breakdownlisted

# Step 3: Plan (หั่นงานเป็นชิ้นเล็ก) **Habit**: H3 — Put First Things First | **Anti-pattern**: One giant prompt that tries to do everything at once ## Process 1. **Read the requirements/design**: Load PRD or design decisions from previous steps. 2. **Decompose into atomic tasks** (1 task = 1 focused unit of work): ``` ## Task List 1. [ ] [Task name] — [1-sentence description] | Files: [list] | Depends on: [none or #N] 2. [ ] [Task name] — [1-sentence description] | Files: [list] | Depends on: [#1] ... ``` For backlog-bound work, prefer vertical slices: each task should deliver a thin but complete path that can be verified or demonstrated on its own. Avoid horizontal layer tasks (`schema only`, `API only`, `UI only`) unless that layer is independently useful and has its own acceptance criteria. A good issue describes end-to-end behavior, not a list of implementation layers. 3. **Prioritize** by importance, not interest: - Q1 (Urgent + Important): Blocking dependencies, security fixes - Q2 (Important, Not Urgent): Core features, tests, docs - Q3 (Urgent, Not Important): Nice-to-have polish - Q4 (Neither): Skip entirely 4. **Identify parallel work, delegation readiness, and classify orchestration**: Tasks with no dependencies can run simultaneously. Also classify whether a task is ready for agent pickup or still needs human input. | Type | When | Isolation