create-plan

1# Create Plan
2 
3## Goal
4 
5Turn a user prompt into a **single, actionable plan** delivered in the final assistant message.
6 
7## Minimal workflow
8 
9Throughout the entire workflow, operate in read-only mode. Do not write or update files.
10 
111. **Scan context quickly**
12   - Read `README.md` and any obvious docs (`docs/`, `CONTRIBUTING.md`, `ARCHITECTURE.md`).
13   - Skim relevant files (the ones most likely touched).
14   - Identify constraints (language, frameworks, CI/test commands, deployment shape).
15 
162. **Ask follow-ups only if blocking**
17   - Ask **at most 1–2 questions**.
18   - Only ask if you cannot responsibly plan without the answer; prefer multiple-choice.
19   - If unsure but not blocked, make a reasonable assumption and proceed.
20 
213. **Create a plan using the template below**
22   - Start with **1 short paragraph** describing the intent and approach.
23   - Clearly call out what is **in scope** and what is **not in scope** in short.
24   - Then provide a **small checklist** of action items (default 6–10 items).
25      - Each checklist item should be a concrete action and, when helpful, mention files/commands.
26      - **Make items atomic and ordered**: discovery → changes → tests → rollout.
27      - **Verb-first**: "Add…", "Refactor…", "Verify…", "Ship…".
28   - Include at least one item for **tests/validation** and one for **edge cases/risk** when applicable.
29   - If there are unknowns, include a tiny **Open questions** section (max 3).
30…