Concise Planning

1---
2name: concise-planning
3description: Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.
4---
5 
6# Concise Planning
7 
8## Goal
9 
10Turn a user request into a **single, actionable plan** with atomic steps.
11 
12## Workflow
13 
14### 1. Scan Context
15 
16- Read `README.md`, docs, and relevant code files.
17- Identify constraints (language, frameworks, tests).
18 
19### 2. Minimal Interaction
20 
21- Ask **at most 1–2 questions** and only if truly blocking.
22- Make reasonable assumptions for non-blocking unknowns.
23 
24### 3. Generate Plan
25 
26Use the following structure:
27 
28- **Approach**: 1-3 sentences on what and why.
29- **Scope**: Bullet points for "In" and "Out".
30- **Action Items**: A list of 6-10 atomic, ordered tasks (Verb-first).
31- **Validation**: At least one item for testing.
32 
33## Plan Template
34 
35```markdown
36# Plan
37 
38<High-level approach>
39 
40## Scope
41 
42- In:
43- Out:
44 
45## Action Items
46 
47[ ] <Step 1: Discovery>
48[ ] <Step 2: Implementation>
49[ ] <Step 3: Implementation>
50[ ] <Step 4: Validation/Testing>
51[ ] <Step 5: Rollout/Commit>
52 
53## Open Questions
54 
55- <Question 1 (max 3)>
56```
57 
58## Checklist Guidelines
59 
60- **Atomic**: Each step should be a single logical unit of work.
61- **Verb-first**: "Add...", "Refactor...", "Verify...".
62- **Concrete**: Name specific files or modules when possible.
63