speckit-analyze

To check for inconsistencies between spec, plan, and task files, run a read-only analysis that loads minimal context and builds semantic requirement and task coverage mappings to flag duplications, ambiguities, and underspecified requirements.

Mapping task coverage to requirements involves loading spec.md, plan.md, and tasks.md from your FEATURE_DIR to create a semantic inventory. This identifies which requirements are fully covered by tasks and highlights any specification gaps.

Yes, you can enforce constitution rules during artifact analysis by checking spec.md, plan.md, and tasks.md against .specify/memory/constitution.md. Any conflicts found are flagged as CRITICAL severity in the final structured Markdown report.

No, spec, plan, and task analysis is strictly non-destructive. It performs a read-only load of your artifacts to evaluate coverage and assign severity to findings, ensuring your original specification files remain completely unchanged.

The best way to detect underspecified requirements is to generate a structured Markdown analysis report that inventories requirements semantically and maps task coverage. This highlights ambiguities and missing details for product managers to resolve.

Spec and plan inconsistencies are marked as CRITICAL when they directly conflict with the project's established constitution rules defined in .specify/memory/constitution.md. Other findings receive severity assignments based on duplication or ambiguity levels.