Review implementation fidelity against specifications by comparing actual code to spec requirements. Identifies deviations, assesses impact, and generates compliance reports for tasks, phases, or entire specs.
Inherits all available tools
Additional assets for this skill
This skill inherits all available tools. When active, it can use any tool Claude has access to.
reference.mdThe sdd-fidelity-review skill compares actual implementation against SDD specification requirements to ensure fidelity between plan and code. It identifies deviations, assesses their impact, and generates detailed compliance reports.
This skill is part of the Spec-Driven Development quality assurance family:
sdd-plan → sdd-next → Implementation → sdd-update → sdd-fidelity-review (this skill) → run-tests
Use this skill when you need to:
Do NOT use for:
sdd-plan)sdd-next)sdd-update)run-tests)This skill relies entirely on the Foundry MCP server (foundry-mcp). Tools use the router+action pattern: mcp__plugin_foundry_foundry-mcp__<router> with action="<action>".
Critical Rules:
Read() on spec JSON filescat, grep, jq) on specs| Type | Scope | When to Use |
|---|---|---|
| Phase Review | 3-10 tasks | Phase completion checkpoints |
| Task Review | 1 file | Critical task validation, high-risk implementations |
For detailed workflow steps per review type, see
reference.md#review-types
For complex reviews or unfamiliar code, use Claude Code's built-in subagents to gather context before and after running the MCP fidelity review:
| Scenario | Subagent | Thoroughness |
|---|---|---|
| Pre-review: understand implementation scope | Explore | medium |
| Pre-review: find all files in a phase | Explore | quick |
| Post-review: investigate deviation causes | Explore | very thorough |
| Post-review: complex multi-file deviations | general-purpose | N/A |
Example: Pre-review context (phase review)
Use the Explore agent (medium thoroughness) to find:
- All implementation files referenced in phase-1 tasks
- Related test files for the phase
- Configuration files that may affect behavior
Example: Post-review investigation
Use the Explore agent (very thorough) to investigate:
- Why task-2-3 has a major deviation
- What other files depend on the deviated implementation
- Whether the deviation is documented in comments or commit messages
For detailed patterns, see
reference.md#subagent-investigation-patterns
Phase review:
mcp__plugin_foundry_foundry-mcp__review action="fidelity" spec_id="{spec-id}" phase_id="{phase-id}"
Task review:
mcp__plugin_foundry_foundry-mcp__review action="fidelity" spec_id="{spec-id}" task_id="{task-id}"
Query tasks before review:
mcp__plugin_foundry_foundry-mcp__task action="query" spec_id="{spec-id}" parent="{phase-id}"
For query patterns and anti-patterns, see
reference.md#querying-spec-and-task-data-efficiently
| Category | Meaning |
|---|---|
| Exact Match | Implementation precisely matches specification |
| Minor Deviation | Small differences with no functional impact |
| Major Deviation | Significant differences affecting functionality |
| Missing | Specified features not implemented |
Generate reports in this format:
# Implementation Fidelity Review
**Spec:** {spec-title} ({spec-id})
**Scope:** {review-scope}
**Date:** {review-date}
## Summary
- **Tasks Reviewed:** {count}
- **Files Analyzed:** {count}
- **Overall Fidelity:** {percentage}%
- **Deviations Found:** {count}
## Fidelity Score
- Exact Matches: {count} tasks
- Minor Deviations: {count} tasks
- Major Deviations: {count} tasks
- Missing Functionality: {count} items
## Detailed Findings
### Task: {task-id} - {task-title}
**Assessment:** {exact-match|minor-deviation|major-deviation}
**Deviations:**
1. {deviation-description}
- **Impact:** {low|medium|high}
- **Recommendation:** {action}
## Recommendations
1. {recommendation-1}
2. {recommendation-2}
For complete template with all sections, see
reference.md#report-structure
This skill may take up to 5 minutes. The MCP tool handles timeout internally.
Never use run_in_background=True with frequent polling.
Skill(foundry:sdd-fidelity-review) "Review phase phase-1 in spec user-auth-001"
For comprehensive documentation including:
See reference.md