| name | plan-style |
|---|---|
| description | Planning conventions for task tracking, skill loading, and finalization. Use when writing implementation plans, or when the user asks to "load plan style", "plan conventions", or "how should I structure a plan". |
Use EnterPlanMode to enter plan mode if not already in it. When writing an implementation plan, include these three elements:
- Task tracking — A section at the top so the implementation session can track progress via
TaskCreate - Skills line — An instruction to load relevant skills before making edits
- Finalize step — A final step instructing to run the
/finalizeskill after implementation
Add a "Task Tracking" section near the top of the plan (after the title, before the first step).
If the plan has few steps or each step is small (e.g., one edit per file), use a single implementation task:
## Task Tracking
At the start, use `TaskCreate` to create a task for each item:
1. Implement the plan
2. Run the `/finalize` skillIf the plan has substantial, distinct steps, create a task per step:
## Task Tracking
At the start, use `TaskCreate` to create a task for each step:
1. [Step 1 label]
2. [Step 2 label]
3. ...
N. Run the `/finalize` skillAlways include "Run the /finalize skill" as the last task.
Identify currently available skills from the skill list in the system prompt. Determine which skills are relevant for this plan's work by comparing the work type against each skill's trigger description.
Add an instruction to the plan: "After plan approval and before making edits, run /skill-a, /skill-b."
Add a final step to the plan:
## Step N: Run `/finalize` Skill
Run the `/finalize` skill to run tests, simplify code, review, and commit.