planning-with-files 3.18.3 → 3.19.0

package/templates/task_plan.md

@@ -1,89 +1,89 @@
-# Task Plan: [Brief Description]
-
-Use this file as the durable roadmap for the task. Create it before complex work and keep it current as phases change.
-
-## Goal
-
-State the intended end result in one clear sentence.
-
-[One sentence describing the end state]
-
-## Next Step
-
-Record the single action that should happen next. Update it whenever the active phase or immediate action changes.
-
-[The single next action. Update whenever phase status changes.]
-
-## Current Phase
-
-Name the phase currently being worked on.
-
-Phase 1
-
-## Phases
-
-Break the task into three to seven verifiable phases. Use only `pending`, `in_progress`, or `complete` for each status and update the value when work advances.
-
-### Phase 1: Requirements & Discovery
-
-- [ ] Understand user intent
-- [ ] Identify constraints and requirements
-- [ ] Document findings in findings.md
-- **Status:** in_progress
-
-### Phase 2: Planning & Structure
-
-- [ ] Define technical approach
-- [ ] Create project structure if needed
-- [ ] Document decisions with rationale
-- **Status:** pending
-
-### Phase 3: Implementation
-
-- [ ] Execute the plan step by step
-- [ ] Write code to files before executing
-- [ ] Test incrementally
-- **Status:** pending
-
-### Phase 4: Testing & Verification
-
-- [ ] Verify all requirements met
-- [ ] Document test results in progress.md
-- [ ] Fix any issues found
-- **Status:** pending
-
-### Phase 5: Delivery
-
-- [ ] Review all output files
-- [ ] Ensure deliverables are complete
-- [ ] Deliver to user
-- **Status:** pending
-
-## Key Questions
-
-Record important questions and replace them with answers as they are resolved.
-
-1. [Question to answer]
-2. [Question to answer]
-
-## Decisions Made
-
-Record significant choices and the reason for each one.
-
-| Decision | Rationale |
-|----------|-----------|
-|          |           |
-
-## Errors Encountered
-
-Record each distinct error, the attempt number, and the resolution. Change the approach before retrying a failed action.
-
-| Error | Attempt | Resolution |
-|-------|---------|------------|
-|       | 1       |            |
-
-## Notes
-
-- Update phase status as work progresses: `pending` to `in_progress` to `complete`.
-- Re-read the goal and next step before major decisions.
-- Log errors promptly so failed approaches are not repeated.
+# Task Plan: [Brief Description]
+
+Use this file as the durable roadmap for the task. Create it before complex work and keep it current as phases change.
+
+## Goal
+
+State the intended end result in one clear sentence.
+
+[One sentence describing the end state]
+
+## Next Step
+
+Record the single action that should happen next. Update it whenever the active phase or immediate action changes.
+
+[The single next action. Update whenever phase status changes.]
+
+## Current Phase
+
+Name the phase currently being worked on.
+
+Phase 1
+
+## Phases
+
+Break the task into three to seven verifiable phases. Use only `pending`, `in_progress`, or `complete` for each status and update the value when work advances.
+
+### Phase 1: Requirements & Discovery
+
+- [ ] Understand user intent
+- [ ] Identify constraints and requirements
+- [ ] Document findings in findings.md
+- **Status:** in_progress
+
+### Phase 2: Planning & Structure
+
+- [ ] Define technical approach
+- [ ] Create project structure if needed
+- [ ] Document decisions with rationale
+- **Status:** pending
+
+### Phase 3: Implementation
+
+- [ ] Execute the plan step by step
+- [ ] Write code to files before executing
+- [ ] Test incrementally
+- **Status:** pending
+
+### Phase 4: Testing & Verification
+
+- [ ] Verify all requirements met
+- [ ] Document test results in progress.md
+- [ ] Fix any issues found
+- **Status:** pending
+
+### Phase 5: Delivery
+
+- [ ] Review all output files
+- [ ] Ensure deliverables are complete
+- [ ] Deliver to user
+- **Status:** pending
+
+## Key Questions
+
+Record important questions and replace them with answers as they are resolved.
+
+1. [Question to answer]
+2. [Question to answer]
+
+## Decisions Made
+
+Record significant choices and the reason for each one.
+
+| Decision | Rationale |
+|----------|-----------|
+|          |           |
+
+## Errors Encountered
+
+Record each distinct error, the attempt number, and the resolution. Change the approach before retrying a failed action.
+
+| Error | Attempt | Resolution |
+|-------|---------|------------|
+|       | 1       |            |
+
+## Notes
+
+- Update phase status as work progresses: `pending` to `in_progress` to `complete`.
+- Re-read the goal and next step before major decisions.
+- Log errors promptly so failed approaches are not repeated.