speckit-analyze

Spec, plan, and task consistency is checked by performing cross-artifact analysis across spec.md, plan.md, and tasks.md to detect drift, duplication, ambiguity, and coverage gaps before building. The process produces a structured Markdown report highlighting mismatches and underspecified items.

Cross-artifact quality analysis compares the same concepts across spec.md, plan.md, and tasks.md to find inconsistencies and missing measurable criteria. It serves as a quality gate for build readiness by identifying ambiguities and coverage gaps in the project specification.

Constitution compliance is validated by checking MUST and SHOULD principles against the project constitution and flagging any conflicts as critical. This ensures the specification and plan align with the governance rules defined in the .specify directory.

Spec-plan-task analysis is strictly non-destructive and reads files only without modifying any project artifacts. It runs optional before and after hooks defined in .specify/extensions.yml without interpreting hook conditions, ensuring your files remain unchanged.

Cross-artifact consistency checking is needed immediately after generating tasks.md to catch mismatches early. Running it before implementation ensures you do not build the wrong requirements or miss critical constraints defined in the specification.

Consistency checking for spec-plan-task gaps is limited to read-only analysis and requires a .specify project structure with constitution-based governance. It does not interpret extension hook conditions or automatically fix the detected duplication, ambiguity, or coverage issues.