Implementation Review

Comprehensive review of feature implementations against specifications and organizational standards.

When to Use

• Implementing or completing new features
• Validating spec compliance before merge
• Checking API implementation correctness
• Preparing release readiness assessments

Instructions

Step 1: Gather Context

1. Identify the implementation scope:

   git diff --name-only HEAD~5
   git status
   

2. Locate relevant specification: UPP-1.3.spec.md or related spec files
3. Identify affected providers/modules

Step 2: Spawn Review Sub-Agents

Delegate parallel reviews to sub-agents for:

Step 3: Synthesize Reports

Collect sub-agent findings and compile:

1. Compliance gaps - Missing or incorrect spec implementations
2. Quality issues - Code smells, inconsistencies, design concerns
3. API correctness - Validated against official documentation
4. Regression risks - Potential breaking changes identified

Output Format

# Implementation Review Report

## Summary
[One paragraph overview]

## Spec Compliance: [PASS/PARTIAL/FAIL]
- [ ] Requirement 1
- [ ] Requirement 2

## Code Quality Issues
| Severity | File | Issue | Recommendation |
|----------|------|-------|----------------|

## API Validation
[Findings from web search validation]

## Regression Risks
[Identified risks and mitigation]

## Release Readiness: [READY/BLOCKED/NEEDS WORK]
[Estimation with blockers listed]

Notes

• Always validate external API usage against current documentation
• Cross-reference with existing provider implementations for consistency
• Flag any deviations from established patterns