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:
- •Determine context - Are you in an existing conversation or starting fresh?
- •Locate the plan - Use provided path or search
thoughts/plans/ - •Gather implementation evidence via git history
Validation Process
Step 1: Context Discovery
- •Read the implementation plan completely
- •Identify what should have changed
- •Delegate to research agents (e.g.,
codebase_investigator,codebase_locator) to verify implementation details and find modified files.
Step 2: Systematic Validation
For each phase:
- •Check completion status - Look for checkmarks
- •Run automated verification - Execute success criteria commands
- •Assess manual criteria - List what needs manual testing
- •Think about edge cases
Step 3: Generate Validation Report
markdown
## Validation Report: [Plan Name] ### Implementation Status - Phase 1: [Name] - Fully implemented - Phase 2: [Name] - Partially implemented (see issues) ### Automated Verification Results - Build passes: `npm run build` - Tests pass: `npm test` - Linting issues: `npm run lint` (X warnings) ### Code Review Findings #### Matches Plan: - [What was implemented correctly] #### Deviations from Plan: - [What differs from plan] #### Potential Issues: - [Concerns discovered] ### Manual Testing Required: 1. [ ] Verify [feature] works 2. [ ] Test error states ### Recommendations: - [Actionable next steps]
Relationship to Other Commands
Recommended workflow:
- •
/create_plan- Create implementation plan - •
/implement_plan- Execute the implementation - •
/commit- Create atomic commits - •
/validate_plan- Verify implementation correctness - •Create PR
Key Principles
- •Understand Before Validating - Read the entire plan first
- •Be Objective and Critical - Validate functionality, not just presence
- •Verify Comprehensively - Run all automated checks
- •Communicate Clearly - Provide specific file references
- •Think Long-term - Consider maintainability