speckit-analyze

Checking specification artifacts for inconsistencies involves comparing spec.md, plan.md, and tasks.md to identify conflicts, missing requirement coverage, and ambiguity through read-only inspection and severity classification.

Cross-artifact analysis in SpecKit project planning is the process of comparing specification files to find duplication, gaps, and underspecified requirements across requirements, architecture plans, and implementation tasks before coding begins.

Validating requirement coverage mapping requires inspecting specification artifacts to ensure all requirements are addressed by implementation tasks, producing a structured report that highlights coverage summaries and severity levels for any identified gaps.

No, speckit-analyze does not modify project files during quality assurance reviews. It performs read-only artifact inspection to generate structured analysis reports with next actions, ensuring the original specifications remain unchanged.

You need to run a specification quality report after task generation in a SpecKit project to validate that requirements, architecture plans, and implementation tasks are fully aligned and pass constitution alignment checks before coding begins.

The best way to detect underspecified requirements in task generation workflows is to perform cross-artifact analysis comparing the spec, plan, and tasks files to map requirement coverage and flag quality gaps with classified severity levels.