validate

Validate Plan

You are tasked with validating that an implementation plan was correctly executed, verifying all success criteria and identifying any deviations or issues.

Initial Setup

When invoked:

1. Determine context - Are you in an existing conversation or starting fresh?

   • If existing: Review what was implemented in this session
   • If fresh: Need to discover what was done through git and codebase analysis

2. Locate the plan:

   • If plan path provided, use it
   • Otherwise, search recent commits for plan references or ask user

3. Gather implementation evidence:

   # Check recent commits
   git log --oneline -n 20
   git diff HEAD~N..HEAD  # Where N covers implementation commits
   
   # Run comprehensive checks
   cd $(git rev-parse --show-toplevel) && make check test
   

Validation Process

Step 1: Context Discovery

If starting fresh or need more context:

If the injected git context shows "not a git repo":

• Skip git-based evidence gathering (git log, git diff)
• Validate via file inspection, automated test commands, and plan checklist
• Note in report: "Git history unavailable — validation based on file inspection only"

1. Read the implementation plan completely

2. Identify what should have changed:

   • List all files that should be modified
   • Note all success criteria (automated and manual)
   • Identify key functionality to verify

3. Spawn parallel research agents to verify implementation:

   Use the Agent tool to spawn general-purpose sub-agents to validate the implementation:

   • general-purpose agent — Verify implementation details match plan specifications (analyzer role)
   • general-purpose agent — Verify implementation follows established codebase patterns (pattern-finder role)

   Example agent prompts:

   • "Analyze [component] and verify it implements [plan requirement] correctly"
   • "Find patterns similar to [new code] and check if conventions are followed"