davila7--claude-code-templates
wehub-resource-sync
1 行
2.5 KiB
JSON
1 行
2.5 KiB
JSON
{"content": "---\nname: create-plan\ndescription: Create a concise plan. Use when a user explicitly asks for a plan related to a coding task.\nmetadata:\n short-description: Create a plan\n---\n\n# Create Plan\n\n## Goal\n\nTurn a user prompt into a **single, actionable plan** delivered in the final assistant message.\n\n## Minimal workflow\n\nThroughout the entire workflow, operate in read-only mode. Do not write or update files.\n\n1. **Scan context quickly**\n - Read `README.md` and any obvious docs (`docs/`, `CONTRIBUTING.md`, `ARCHITECTURE.md`).\n - Skim relevant files (the ones most likely touched).\n - Identify constraints (language, frameworks, CI/test commands, deployment shape).\n\n2. **Ask follow-ups only if blocking**\n - Ask **at most 1–2 questions**.\n - Only ask if you cannot responsibly plan without the answer; prefer multiple-choice.\n - If unsure but not blocked, make a reasonable assumption and proceed.\n\n3. **Create a plan using the template below**\n - Start with **1 short paragraph** describing the intent and approach.\n - Clearly call out what is **in scope** and what is **not in scope** in short.\n - Then provide a **small checklist** of action items (default 6–10 items).\n - Each checklist item should be a concrete action and, when helpful, mention files/commands.\n - **Make items atomic and ordered**: discovery → changes → tests → rollout.\n - **Verb-first**: \"Add…\", \"Refactor…\", \"Verify…\", \"Ship…\".\n - Include at least one item for **tests/validation** and one for **edge cases/risk** when applicable.\n - If there are unknowns, include a tiny **Open questions** section (max 3).\n\n4. **Do not preface the plan with meta explanations; output only the plan as per template**\n\n## Plan template (follow exactly)\n\n```markdown\n# Plan\n\n<1–3 sentences: what we're doing, why, and the high-level approach.>\n\n## Scope\n- In:\n- Out:\n\n## Action items\n[ ] <Step 1>\n[ ] <Step 2>\n[ ] <Step 3>\n[ ] <Step 4>\n[ ] <Step 5>\n[ ] <Step 6>\n\n## Open questions\n- <Question 1>\n- <Question 2>\n- <Question 3>\n```\n\n## Checklist item guidance\nGood checklist items:\n- Point to likely files/modules: src/..., app/..., services/...\n- Name concrete validation: \"Run npm test\", \"Add unit tests for X\"\n- Include safe rollout when relevant: feature flag, migration plan, rollback note\n\nAvoid:\n- Vague steps (\"handle backend\", \"do auth\")\n- Too many micro-steps\n- Writing code snippets (keep the plan implementation-agnostic)\n"} |