4-implement-plan

name	4_implement_plan
description	Implements an approved technical plan from `thoughts/plans/`. These plans contain phases with specific changes and success criteria.

Implement Plan

You are tasked with implementing an approved technical plan from thoughts/plans/. These plans contain phases with specific changes and success criteria.

Getting Started

When given a plan path:

• Read the plan completely and check for any existing checkmarks (- [x])
• Read all files mentioned in the plan
• Read files fully - never use limit/offset parameters
• Create a todo list to track your progress
• Start implementing if you understand what needs to be done

If no plan path provided, ask for one.

Implementation Philosophy

Plans are carefully designed, but reality can be messy. Your job is to:

• Follow the plan's intent while adapting to what you find
• Implement each phase fully before moving to the next
• Verify your work makes sense in the broader codebase context
• Update checkboxes in the plan as you complete sections

When things don't match the plan exactly:

Issue in Phase [N]:
Expected: [what the plan says]
Found: [actual situation]
Why this matters: [explanation]

How should I proceed?

IMPORTANT Commit after every step

You MUST commit changes after completing any step of a phase. Do not wait for the user to ask — this command authorizes you to commit. After each step: stage, commit (following the commit guidelines below), then move to the next step.

Commit guidelines

When committing changes to git, adhere to the following:

• Stage behavioral changes from structural changes (refactorings like moves, renames, etc) to commit them separately
• Keep commit title short (50 chars max)
• Explain reasoning for these particular changes in commit body
• If you considered alternatives, describe them in the commit body

Verification Approach

After implementing a phase:

• Run the success criteria checks
• Fix any issues before proceeding
• Update your progress in both the plan and your todos
• Check off completed items in the plan file using Edit

Working Process

1. Phase by Phase Implementation:

   • Complete one phase entirely before moving to next
   • Run all automated checks for that phase
   • Update plan checkboxes as you go

2. When You Get Stuck:

   • First, ensure you've read and understood all relevant code
   • Consider if the codebase has evolved since plan was written
   • Present the mismatch clearly and ask for guidance

3. Progress Tracking:

   • Use TodoWrite to track implementation tasks
   • Update plan file with [x] checkmarks as you complete items
   • Keep user informed of progress

Resuming Work

If the plan has existing checkmarks:

• Trust that completed work is done
• Pick up from the first unchecked item
• Verify previous work only if something seems off

Remember: You're implementing a solution, not just checking boxes. Keep the end goal in mind and maintain forward momentum.