analyze

To verify spec-to-code alignment, you run an adversarial eight-check process that resolves misalignments between your spec, plan, tasks, and codebase. It blocks implementation progression until all gating criteria pass.

Preventing codebase drift involves checking plan-vs-codebase reality and DAG integrity before coding. This skill enforces task traceability and architecture coverage to ensure your codebase matches your project plan.

Extracting acceptance criteria and tracing them through architecture tasks is handled by the AC extraction and task traceability checks. This ensures your architectural decisions fully cover the required acceptance criteria.

Yes, the spec-to-code alignment process generates a formal deliverables-and-status artifact suite. It outputs a structured report.md and status.json file directly to your specified workstream directory.

No, you cannot use this alignment checker to modify your codebase. It enforces strict read-only boundaries during the analysis phase to safely verify deliverables without risking unintended code changes.