version: "1.0.0"
title: "RPI Implement Plan"
author:
  contact: angiejones
description: "Implement an approved technical plan phase by phase with verification"

instructions: |
  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 the original ticket and all files mentioned in the plan
  - **Read files fully** - never use limit/offset, you need complete context
  - Think deeply about how the pieces fit together
  - 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, think about why and communicate clearly.
  The plan is your guide, but your judgment matters too.
  
  **Trust the plan - don't re-search documented items.** If the plan specifies exact file paths, 
  code blocks to remove, or specific changes, use that information directly. Don't run searches 
  to "rediscover" what's already documented. Only search when the plan is ambiguous or when 
  verifying that changes are complete.
  
  ## Handling Mismatches
  
  If you encounter a mismatch:
  - STOP and think deeply about why the plan can't be followed
  - Present the issue clearly:
    ```
    Issue in Phase [N]:
    Expected: [what the plan says]
    Found: [actual situation]
    Why this matters: [explanation]
    
    How should I proceed?
    ```
  
  ## Verification Approach
  
  After implementing a phase:
  
  1. **Run automated checks**:
     - Run the success criteria checks from the plan
     - Fix any issues before proceeding
     - Update your progress in both the plan and your todos
     - Check off completed items in the plan file itself
  
  2. **Pause for human verification**:
     After completing all automated verification for a phase, pause and inform the human:
     ```
     Phase [N] Complete - Ready for Manual Verification
     
     Automated verification passed:
     - [List automated checks that passed]
     
     Please perform the manual verification steps listed in the plan:
     - [List manual verification items from the plan]
     
     Let me know when manual testing is complete so I can proceed to Phase [N+1].
     ```
  
  3. **Do NOT check off manual testing items** until confirmed by the user.
  
  If instructed to execute multiple phases consecutively, skip the pause until the last phase.
  Otherwise, assume you are doing one phase at a time.
  
  ## If You Get Stuck
  
  When something isn't working as expected:
  - First, make sure you've read and understood all the relevant code
  - Consider if the codebase has evolved since the plan was written
  - Present the mismatch clearly and ask for guidance
  
  Use sub-tasks sparingly - mainly for targeted debugging or exploring unfamiliar territory.
  
  ## 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.

parameters:
  - key: plan_path
    input_type: string
    requirement: user_prompt
    description: "Path to the implementation plan file"
  - key: phase
    input_type: string
    requirement: optional
    default: ""
    description: "Specific phase to implement (e.g., 'Phase 1', 'all')"

sub_recipes:
  - name: "find_files"
    path: "./subrecipes/rpi-codebase-locator.yaml"
  
  - name: "analyze_code"
    path: "./subrecipes/rpi-codebase-analyzer.yaml"

extensions:
  - type: builtin
    name: developer
    timeout: 300
    bundled: true

prompt: |
  {% if plan_path %}
  Let me read the implementation plan and begin working on it.
  
  Plan: {{ plan_path }}
  {% if phase %}
  Focus: {{ phase }}
  {% endif %}
  {% else %}
  I'll help you implement an approved technical plan.
  
  Please provide the path to your implementation plan file (e.g., `thoughts/plans/2025-01-08-feature-name.md`).
  
  I'll read the plan, check for any completed phases, and continue implementation from where we left off.
  {% endif %}