1# Task Plan: [Brief Description]
2<!-- 
3  WHAT: This is your roadmap for the entire task. Think of it as your "working memory on disk."
4  WHY: After 50+ tool calls, your original goals can get forgotten. This file keeps them fresh.
5  WHEN: Create this FIRST, before starting any work. Update after each phase completes.
6-->
7 
8## Goal
9<!-- 
10  WHAT: One clear sentence describing what you're trying to achieve.
11  WHY: This is your north star. Re-reading this keeps you focused on the end state.
12  EXAMPLE: "Create a Python CLI todo app with add, list, and delete functionality."
13-->
14[One sentence describing the end state]
15 
16## Current Phase
17<!-- 
18  WHAT: Which phase you're currently working on (e.g., "Phase 1", "Phase 3").
19  WHY: Quick reference for where you are in the task. Update this as you progress.
20-->
21Phase 1
22 
23## Phases
24<!-- 
25  WHAT: Break your task into 3-7 logical phases. Each phase should be completable.
26  WHY: Breaking work into phases prevents overwhelm and makes progress visible.
27  WHEN: Update status after completing each phase: pending → in_progress → complete
28-->
29 
30### Phase 1: Requirements & Discovery
31<!-- 
32  WHAT: Understand what needs to be done and gather initial information.
33  WHY: Starting without understanding leads to wasted effort. This phase prevents that.
34-->
35- [ ] Understand user intent
36- [ ] Identify constraints and requirements
37- [ ] Document findings in findings.md
38- **Status:** in_progress
39<!-- 
40  STATUS VALUES:
41  - pending: Not started yet
42  - in_progress: Currently working on this
43  - complete: Finished this phase
44-->
45 
46### Phase 2: Planning & Structure
47<!-- 
48  WHAT: Decide how you'll approach the problem and what structure you'll use.
49  WHY: Good planning prevents rework. Document decisions so you remember why you chose them.
50-->
51- [ ] Define technical approach
52- [ ] Create project structure if needed
53- [ ] Document decisions with rationale
54- **Status:** pending
55 
56### Phase 3: Implementation
57<!-- 
58  WHAT: Actually build/create/write the solution.
59  WHY: This is where the work happens. Break into smaller sub-tasks if needed.
60-->
61- [ ] Execute the plan step by step
62- [ ] Write code to files before executing
63- [ ] Test incrementally
64- **Status:** pending
65 
66### Phase 4: Testing & Verification
67<!-- 
68  WHAT: Verify everything works and meets requirements.
69  WHY: Catching issues early saves time. Document test results in progress.md.
70-->
71- [ ] Verify all requirements met
72- [ ] Document test results in progress.md
73- [ ] Fix any issues found
74- **Status:** pending
75 
76### Phase 5: Delivery
77<!-- 
78  WHAT: Final review and handoff to user.
79  WHY: Ensures nothing is forgotten and deliverables are complete.
80-->
81- [ ] Review all output files
82- [ ] Ensure deliverables are complete
83- [ ] Deliver to user
84- **Status:** pending
85 
86## Key Questions
87<!-- 
88  WHAT: Important questions you need to answer during the task.
89  WHY: These guide your research and decision-making. Answer them as you go.
90  EXAMPLE: 
91    1. Should tasks persist between sessions? (Yes - need file storage)
92    2. What format for storing tasks? (JSON file)
93-->
941. [Question to answer]
952. [Question to answer]
96 
97## Decisions Made
98<!-- 
99  WHAT: Technical and design decisions you've made, with the reasoning behind them.
100  WHY: You'll forget why you made choices. This table helps you remember and justify decisions.
101  WHEN: Update whenever you make a significant choice (technology, approach, structure).
102  EXAMPLE:
103    | Use JSON for storage | Simple, human-readable, built-in Python support |
104-->
105| Decision | Rationale |
106|----------|-----------|
107|          |           |
108 
109## Errors Encountered
110<!-- 
111  WHAT: Every error you encounter, what attempt number it was, and how you resolved it.
112  WHY: Logging errors prevents repeating the same mistakes. This is critical for learning.
113  WHEN: Add immediately when an error occurs, even if you fix it quickly.
114  EXAMPLE:
115    | FileNotFoundError | 1 | Check if file exists, create empty list if not |
116    | JSONDecodeError | 2 | Handle empty file case explicitly |
117-->
118| Error | Attempt | Resolution |
119|-------|---------|------------|
120|       | 1       |            |
121 
122## Notes
123<!-- 
124  REMINDERS:
125  - Update phase status as you progress: pending → in_progress → complete
126  - Re-read this plan before major decisions (attention manipulation)
127  - Log ALL errors - they help avoid repetition
128  - Never repeat a failed action - mutate your approach instead
129-->
130- Update phase status as you progress: pending → in_progress → complete
131- Re-read this plan before major decisions (attention manipulation)
132- Log ALL errors - they help avoid repetition
133