create-plan

Topics in the source

• Create Plan
• Goal
• Minimal workflow
• Plan template (follow exactly)
• Checklist item guidance

Turn a user prompt into a single, actionable plan delivered in the final assistant message. Throughout the entire workflow, operate in read-only mode. Do not write or update files. 1. 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). 2. Ask follow-ups only if blocking Ask at most 1–2 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. 3. 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 unkn

This is an excerpt. Refer to the complete source and its current requirements.