analyze

To check for spec drift against architecture decisions, you can audit a spec.md file alongside its sibling slice files and reference docs to detect cross-artifact inconsistencies. The audit compares the spec against ADRs, architecture, principles, and glossary entries.

Cross-artifact consistency reporting detects drift and conflicts between a spec and its related artifacts, such as ADR decisions, architecture principles, and terminology, without modifying any files. It surfaces issues across six categories including duplication and ambiguity.

You run a non-destructive spec audit by executing the skill on a single spec.md and its slice-NN-*.md files. It reads reference docs like product-vision.md and decisions, then emits a markdown findings report directly to stdout without writing any files.

A six-category spec audit report includes a severity-sorted findings list, a per-category coverage summary, and recommended next steps. The six categories are Duplication, Ambiguity, Underspecification, Principle Violations, Coverage Gaps, and Terminology Drift.

Yes, you can audit spec slices against a glossary and product vision docs. The audit reads read-only reference inputs including docs/memory/glossary.md, docs/product-vision.md, docs/architecture.md, and docs/decisions to evaluate consistency with the target spec.

A key limitation of this cross-artifact audit is that it only evaluates a single jig spec at a time and outputs findings strictly to stdout. It does not write files or automatically resolve the detected drift, coverage gaps, or terminology conflicts.