review-implementation

You can verify code against markdown specs by extracting acceptance criteria from documentation and mapping them to concrete file and line evidence. This requirements traceability process classifies items as satisfied, partial, missing, or conflicting to ensure complete spec compliance.

Requirements traceability maps each stated spec criterion to concrete code evidence. Gap analysis works by identifying missing, partial, or conflicting implementations during this mapping process, ensuring your codebase fully satisfies the provided documentation without unjustified overbuilt features.

Yes, you can automatically fix code gaps using the targeted fix mode. It applies minimal, reversible code changes to align behavior with your markdown documentation, correcting bug risks and divergences without adding unjustified features beyond the spec scope.

Yes, the review process assesses security, privacy, and performance alongside coverage. It performs a multi-pass audit checking correctness, integration fit, simplicity, cleanup, and validation approach to provide comprehensive, evidence-backed reporting on your implementation.

To run an audit of phase completion, provide your phase docs and codebase context to the AI. The Skill maps the documentation's acceptance criteria to code evidence, verifying correctness, integration fit, and requirement coverage to validate that the phase is fully implemented.

You should not use targeted fixes when the divergence requires significant refactoring beyond minimal changes. The fix mode applies only minimal, reversible adjustments to match documentation, avoiding the addition of unjustified features or complex architectural changes not specified in the PRD.