speckit-analyze

To check consistency between spec.md, plan.md, and tasks.md, run a cross-artifact analysis to detect missing entries, conflicting requirements, and coverage gaps across your documents before implementation begins.

When tasks.md has missing or conflicting requirements, cross-artifact analysis identifies requirements without tasks and tasks without requirements, flagging these coverage gaps and unresolved placeholders for focused remediation.

To validate project artifacts against constitution rules, compliance checks enforce MUST-level principles from .specify/memory/constitution.md, scanning artifacts and flagging any violations as critical issues in the report.

Spec-kit analysis requires a .specify directory because it reads constitution rules from .specify/memory/constitution.md for normative validation and accesses FEATURE_DIR artifacts to perform non-destructive cross-artifact checks.

To detect vague acceptance criteria in your spec and plan, a quality analysis scans for unresolved placeholders and ambiguities across spec.md, plan.md, and tasks.md, producing a prioritized report for remediation.

Running consistency checks on an incomplete tasks.md file will surface coverage gaps by identifying requirements without tasks, but a completed tasks.md produced by speckit.tasks is required for accurate analysis.