agentleFS
SamuelBostic29SamuelBostic29/claude-skills/skills/plan-save/SKILL.md

plan-save

Skill1 starsChanged 4 months agoMITView on GitHub

Save and structure a plan for iterative execution across sessions. Use right after plan mode (or a planning conversation) produces a plan worth executing over multiple sessions — "save this plan", "write the plan to a file", "make this plan trackable/persistent". Restructures the plan into a persistent markdown file with a Context section and phase headings that plan-next executes one at a time; asks where to save, preserves every technical detail.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the original plan already has numbered sections, steps, or phases, use those as the phases.

    line 84
  2. Distinctive:

    If the original plan doesn't have clear steps, organize it into logical phases yourself based on dependency order.

    line 85
  3. Distinctive:

    Keep phase descriptions detailed — include file paths, code snippets, architecture notes, expected behavior.

    line 86
  4. Distinctive:

    Do NOT add phases that weren't in the original plan.

    line 87
  5. Distinctive:

    Do NOT remove or reword technical content to make it "cleaner" — accuracy matters more than aesthetics.

    line 88

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Plan Save: Structure and persist a plan for iterative execution

You have just helped create a plan (either through plan mode or conversation). Your job is to restructure it into a persistent, trackable format and save it to a file.

When to use this skill

  • Plan mode (or a planning conversation) just produced a plan, and the work will span multiple sessions.
  • "Save this plan" / "write the plan to a file" / "make this plan trackable".

When NOT to use this skill

  • No plan exists in the conversation yet — there is nothing to restructure; plan first.
  • The plan is already saved — edit the file directly, or use plan-next (execute) / plan-review (critique).
  • A small, single-session change — just do the work; a plan file adds ceremony, not value.

Steps

  1. Identify the plan in the current conversation. Look for the plan that was just discussed or created in plan mode.
  2. Ask the user for the save location using AskUserQuestion. Suggest a descriptive filename in the current project directory (e.g., ./dev-mode-plan.md, ./auth-refactor-plan.md). Do NOT save to ~/.claude/.
  3. Restructure the plan into the format described below.
  4. Write the file to the location the user specified.

Output format

# [Plan Title]

## Context

[Extract the background, goals, constraints, architecture decisions, and any other
relevant context from the plan. This section should give a future session enough
information to understand WHY this plan exists and WHAT is being built. Include
file paths, architecture diagrams, design principles — anything a fresh session
needs to pick up the work without re-exploring the codebase.]

## Implementation phases

Phases are executed one at a time across conversation sessions. When a phase is finished,
add an `#### Implemented` subsection summarizing what was done, then prefix the phase title
with **COMPLETED** (e.g., `### COMPLETED 1. Setup database schema`).
On a new session, read this file first — skip any COMPLETED phases and pick up the next open one.
Do not automatically move to the next phase when done — mark the phase completed and stop.

### 1. [Phase title]

[What needs to be done — files to create/modify, specific implementation details,
code snippets, acceptance criteria. Be detailed enough that a fresh session can
execute this without guessing.]

### 2. [Phase title]

[...]

### N. [Phase title]

[...]

Rules

  • Preserve ALL technical detail from the original plan — do not summarize away specifics like file paths, code snippets, architecture notes, or design rationale.
  • The Context section should be comprehensive enough for a completely fresh session (no prior conversation history) to understand the project and make good decisions.
  • Each phase should be a coherent, self-contained unit of work that can be completed in one session.
  • If the original plan already has numbered sections, steps, or phases, use those as the phases. Preserve the original numbering/naming style where it makes sense.
  • If the original plan doesn't have clear steps, organize it into logical phases yourself based on dependency order.
  • Keep phase descriptions detailed — include file paths, code snippets, architecture notes, expected behavior.
  • Do NOT add phases that weren't in the original plan.
  • Do NOT remove or reword technical content to make it "cleaner" — accuracy matters more than aesthetics.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.