We split this skill into the rules it gives an agent

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

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈9

  Distinctive · estimate

  This author's own choices. Worth a look.

• 5

  Very specific

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

• Common
• Distinctive
• Very specific

1. Distinctive:

   Create a focused implementation plan that fixes scope, prevents uncontrolled expansion, and gives the project a checkbox-based execution …

   line 10
2. Very specific:

   Read relevant local docs first: README.md, AGENTS.md, CLAUDE.md, docs/*.md, and existing dev-plan/*.md.

   line 14
3. Very specific:

   Create a new file under dev-plan/implement_YYYYMMDD_HHMMSS.md unless the user explicitly asks to update an existing plan.

   line 16
4. Distinctive:

   Keep the plan implementation-oriented, not a PRD or meeting note.

   line 17
5. Distinctive:

   Add self-tests and done criteria for every phase.

   line 19
6. Distinctive:

   Update checkboxes to match real progress while implementing.

   line 20
7. Distinctive:

   Every plan should include:

   line 24
8. Very specific:

   Use references/dev-plan-template.md when a full skeleton is needed.

   line 34
9. Distinctive:

   Do not overwrite old plan files.

   line 38
10. Distinctive:

    Do not add features outside the stated scope.

    line 39
11. Distinctive:

    Put ambiguous or risky work into a separate phase or follow-up section.

    line 40
12. Distinctive:

    If parallel implementation is likely, include ownership boundaries and merge order.

    line 41
13. Very specific:

    If engineering review is requested, add an Engineering Review section or call the plan-eng-review skill separately.

    line 42
14. Very specific:

    Use scripts/new_dev_plan.py to scaffold a timestamped plan:

    line 46

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.