agentleFS
anurag-rivoraanurag-rivora/product-brain-starter/.claude/skills/plan-in-nine-steps/SKILL.md

plan-in-nine-steps

Skill1 starsChanged 4 days agoMITView on GitHub

Plan a feature in nine steps using the checklists in steps/, starting with a five-line executive summary and ending with the delivery backlog. Loads only the brief and approved in-scope brain entries, drafts one step at a time, and stops for a person to approve each. Use when someone says "plan this feature", "plan in nine steps" or "draft the next step".

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Ask which feature (features/<slug>/).

    line 12
  2. Very specific:

    Read AGENTS.md, features/<slug>/brief.md and brain/INDEX.md.

    line 13
  3. Distinctive:

    Check that every earlier step this one reads has been approved in the brief's steps table.

    line 16
  4. Very specific:

    Write the step to features/<slug>/<step>.md.

    line 18
  5. Very specific:

    When answers arrive, run the capture skill so the answers worth keeping are saved with a scope.

    line 25
  6. Distinctive:

    Start the next step before the person approves this one.

    line 29
  7. Distinctive:

    Treat a draft step or proposed entry as fact.

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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 in nine steps

One step at a time. Each step reads only approved earlier steps. Start with a five-line summary, and rewrite it at the end.

How to run it

  1. Ask which feature (features/<slug>/). If it does not exist, copy features/_template/ and ask the person to fill in brief.md.
  2. Read AGENTS.md, features/<slug>/brief.md and brain/INDEX.md. Work out the scope from the brief.
  3. Open only entries that are status: approved and whose scope matches. Read rules with severity must first. Ignore proposed entries.
  4. Pick the next step in this order: 01 executive summary (first pass), 02 intent, 03 impact, 04 UX, 05 backend, 06 system impact, 07 data, 08 plan, 09 backlog, then 01 executive summary again (final pass). Skip a step marked not needed.
  5. Check that every earlier step this one reads has been approved in the brief's steps table. If not, stop and say which one is missing.
  6. Open steps/<step>.md and work through its checklist. Read the approved earlier steps it names. Do not read drafts.
  7. Write the step to features/<slug>/<step>.md. In it:
    • Cite entry IDs for everything you rely on.
    • Label each assumption with a confidence and what would disprove it.
    • List sources.
    • Say "to be confirmed" instead of guessing.
  8. List questions in features/<slug>/questions.md with an owner role and a blocking level. If a blocking question is open, stop here and ask.
  9. Set the step to draft in the brief and ask the person to review and approve it. Only a person changes it to approved and fills in approver and date.
  10. When answers arrive, run the capture skill so the answers worth keeping are saved with a scope.

Do not

  • Start the next step before the person approves this one.
  • Treat a draft step or proposed entry as fact.
  • Invent file paths, module names or endpoints.

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.