Iterate Implementation Plan

---

description: Iterate on existing implementation plans with thorough research and updates model: opus

Iterate Implementation Plan

You are tasked with updating existing implementation plans based on user feedback. You should be skeptical, thorough, and ensure changes are grounded in actual codebase reality.

Initial Response

When this command is invoked:

1. **Parse the input to identify**:

   • Plan file path (e.g., thoughts/shared/plans/2025-10-16-feature.md)
   • Requested changes/feedback

2. **Handle different input scenarios**:

   **If NO plan file provided**:

   I'll help you iterate on an existing implementation plan.
   
   Which plan would you like to update? Please provide the path to the plan file (e.g., `thoughts/shared/plans/2025-10-16-feature.md`).
   
   Tip: You can list recent plans with `ls -lt thoughts/shared/plans/ | head`

   Wait for user input, then re-check for feedback.

   **If plan file provided but NO feedback**:

   I've found the plan at [path]. What changes would you like to make?
   
   For example:
   - "Add a phase for migration handling"
   - "Update the success criteria to include performance tests"
   - "Adjust the scope to exclude feature X"
   - "Split Phase 2 into two separate phases"

   Wait for user input.

   **If BOTH plan file AND feedback provided**:

   • Proceed immediately to Step 1
   • No preliminary questions needed

Process Steps

Step 1: Read and Understand Current Plan

1. **Read the existing plan file COMPLETELY**:

   • Use the Read tool WITHOUT limit/offset parameters
   • Understand the current structure, phases, and scope
   • Note the success criteria and implementation approach

2. **Understand the requested changes**:

   • Parse what the user wants to add/modify/remove
   • Identify if changes require codebase research
   • Determine scope of the update

Step 2: Research If Needed

**Only spawn research tasks if the changes require new technical understanding.**

If the user's feedback requires understanding new code patterns or validating assumptions:

1. **Create a research todo list** using TodoWrite

2. **Spawn parallel sub-tasks for research**: Use the right agent for each type of research:

   **For code investigation:**

   • codebase-locator - To find relevant files
   • codebase-analyzer - To understand implementation details
   • codebase-pattern-finder - To find similar patterns

   **For historical context:**

   • thoughts-locator - To find related research or decisions
   • thoughts-analyzer - To extract insights from documents

   **Be EXTREMELY specific about directories**:

   • If the change involves "WUI", specify humanlayer-wui/ directory
   • If it involves "daemon", specify hld/ directory
   • Include full path context in prompts

3. **Read any new files identified by research**:

   • Read them FULLY into the main context
   • Cross-reference with the plan requirements

4. **Wait for ALL sub-task