Create Plan
Goal
Turn a user prompt into a single, actionable plan delivered in the final assistant message.
Minimal workflow
Throughout the entire workflow, operate in read-only mode. Do not write or update files.
Scan context quickly
- Read
README.md and any obvious docs (docs/, CONTRIBUTING.md, ARCHITECTURE.md).
- Skim relevant files (the ones most likely touched).
- Identify constraints (language, frameworks, CI/test commands, deployment shape).
Ask follow-ups only if blocking
- Ask at most 5–6 questions.
- Only ask if you cannot responsibly plan without the answer; prefer multiple-choice.
- If unsure but not blocked, make a reasonable assumption and proceed.
Create a plan using the template below
- Start with 1 short paragraph describing the intent and approach.
- Clearly call out what is in scope and what is not in scope in short.
- Then provide a small checklist of action items (default 6–10 items).
- Each checklist item should be a concrete action and, when helpful, mention files/commands.
- Make items atomic and ordered: discovery → changes → tests → rollout.
- Verb-first: "Add…", "Refactor…", "Verify…", "Ship…".
- Include at least one item for tests/validation and one for edge cases/risk when applicable.
- If there are unknowns, include a tiny Open questions section (max 3).
Do not preface the plan with meta explanations; output only the plan as per template
Plan template (follow exactly)
# Plan
<1–3 sentences: what we're doing, why, and the high-level approach.>
## Scope
- In:
- Out:
## Action items
[ ] <Step 1>
[ ] <Step 2>
[ ] <Step 3>
[ ] <Step 4>
[ ] <Step 5>
[ ] <Step 6>
## Open questions
- <Question 1>
- <Question 2>
- <Question 3>
Checklist item guidance
Good checklist items:
- Point to likely files/modules: src/..., app/..., services/...
- Name concrete validation: "Run npm test", "Add unit tests for X"
- Include safe rollout when relevant: feature flag, migration plan, rollback note
- Before completing, verify the entire plan - battle test and stress-test this plan to check for missing inconsistencies, issues, bugs, consistency, edge cases, tests, conventions, obsevability, friendly ui, intuitive ux, etc.
Avoid:
- Vague steps ("handle backend", "do auth")
- Too many micro-steps
- Writing code snippets (keep the plan implementation-agnostic)
1---2name: create-plan3description: Create a concise plan. Use when a user explicitly asks for a plan related to a coding task.4---56# Create Plan78## Goal910Turn a user prompt into a **single, actionable plan** delivered in the final assistant message.1112## Minimal workflow1314Throughout the entire workflow, operate in read-only mode. Do not write or update files.15161. **Scan context quickly**17 - Read `README.md` and any obvious docs (`docs/`, `CONTRIBUTING.md`, `ARCHITECTURE.md`).18 - Skim relevant files (the ones most likely touched).19 - Identify constraints (language, frameworks, CI/test commands, deployment shape).20212. **Ask follow-ups only if blocking**22 - Ask **at most 5–6 questions**.23 - Only ask if you cannot responsibly plan without the answer; prefer multiple-choice.24 - If unsure but not blocked, make a reasonable assumption and proceed.25263. **Create a plan using the template below**27 - Start with **1 short paragraph** describing the intent and approach.28 - Clearly call out what is **in scope** and what is **not in scope** in short.29 - Then provide a **small checklist** of action items (default 6–10 items).30 - Each checklist item should be a concrete action and, when helpful, mention files/commands.31 - **Make items atomic and ordered**: discovery → changes → tests → rollout.32 - **Verb-first**: "Add…", "Refactor…", "Verify…", "Ship…".33 - Include at least one item for **tests/validation** and one for **edge cases/risk** when applicable.34 - If there are unknowns, include a tiny **Open questions** section (max 3).35364. **Do not preface the plan with meta explanations; output only the plan as per template**3738## Plan template (follow exactly)3940```markdown41# Plan4243<1–3 sentences: what we're doing, why, and the high-level approach.>4445## Scope46- In:47- Out:4849## Action items50[ ] <Step 1>51[ ] <Step 2>52[ ] <Step 3>53[ ] <Step 4>54[ ] <Step 5>55[ ] <Step 6>5657## Open questions58- <Question 1>59- <Question 2>60- <Question 3>61```6263## Checklist item guidance64Good checklist items:65- Point to likely files/modules: src/..., app/..., services/...66- Name concrete validation: "Run npm test", "Add unit tests for X"67- Include safe rollout when relevant: feature flag, migration plan, rollback note68- Before completing, verify the entire plan - battle test and stress-test this plan to check for missing inconsistencies, issues, bugs, consistency, edge cases, tests, conventions, obsevability, friendly ui, intuitive ux, etc.6970Avoid:71- Vague steps ("handle backend", "do auth")72- Too many micro-steps73- Writing code snippets (keep the plan implementation-agnostic)
payals