Plan

Skill graphistry/graphistry-skills/.agents/skills/internal/plan

Create and maintain a concise file-backed plan for multi-session work, handoffs, or complex multi-PR tasks. Use only when the user explicitly requests a plan file or durable task state is needed; otherwise use the platform's native planning.From its SKILL.md

Install

npx -y skills add graphistry/graphistry-skills --skill plan

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.0 KB, as published. Nobody here has run it

File-backed plans

Use a plan file only when its persistence is valuable. For ordinary single-session work, use native planning instead.

Start

Create plans/<task>/plan.md from the template below.
Record the raw request, branch/base, success criteria, and any constraints.
Split the work into independently verifiable steps. Mark only one IN_PROGRESS.

# <Task> plan

**Branch**: `<branch>`
**Base**: `<base>`
**PR**: `<URL or pending>`

## Goal
<Outcome and success criteria>

## Context
<Important constraints, decisions, and links needed to resume>

## Steps

### 1. <Step>
**Status**: IN_PROGRESS
**Verify**: <command or observable outcome>
**Notes**: <results, decisions, or blocker>

### 2. <Step>
**Status**: TODO
**Verify**: <command or observable outcome>

Maintain

Read the plan at natural handoff points: starting a work block, changing steps, returning after interruption, and before a PR/review.
Update it when a step completes, a material decision changes, a command fails, or a blocker appears. Do not turn routine reads or minor edits into plan churn.
Keep durable facts in the plan: exact commands worth rerunning, validation results, PR links, unresolved questions, and decisions with rationale.
Keep only one step IN_PROGRESS; use TODO, DONE, BLOCKED, or SKIPPED for the rest.
For a long plan, replace completed detail with a short verified-results summary. Preserve the commands and decisions needed for a safe resume.

Finish

Before handoff or PR, record the current commit/PR, validation performed, remaining risks, and the next concrete action. Do not commit plans/ unless repository convention or the user asks.