Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.

Concise Planning Goal Turn a user request into a single, actionable plan with atomic steps. Workflow 1. Scan Context Read README.md , docs, and relevant code files. Identify constraints (language, frameworks, tests). 2. Minimal Interaction Ask at most 1–2 questions and only if truly blocking. Make reasonable assumptions for non blocking unknowns. 3. Generate Plan Use the following structure: Approach : 1 3 sentences on what and why. Scope : Bullet points for "In" and "Out". Action Items : A list of 6 10 atomic, ordered tasks (Verb first). Validation : At least one item for testing. Plan Template Checklist Guidelines Atomic : Each step should be a single logical unit of work. Verb first : "Add...", "Refactor...", "Verify...". Concrete : Name specific files or modules when possible. When to Use This skill is applicable to execute the workflow or actions described in the overview. Limitations Use this skill only when the task clearly matches the scope described above. Do not treat the output as a substitute for environment specific validation, testing, or expert review. Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

concise-planning