speckit-analyze

To check for inconsistencies across spec, plan, and task files, you analyze the artifacts to surface duplications, ambiguities, and underspecifications. This process produces a compact report with remediation recommendations and traceable mappings between requirements, stories, and tasks.

Cross-artifact consistency analysis in a spec-kit project structure identifies gaps where tasks lack associated requirements and validates conformance to the constitution. It ensures alignment across spec.md, plan.md, and tasks.md before implementation.

You need to run a consistency check on generated tasks immediately after task generation. Running the analysis at this stage surfaces critical risks, validates constitution conformance, and maintains alignment before implementation.

Yes, spec analysis maps requirements to stories and tasks to provide coverage tracking. This mapping reveals gaps where tasks have no associated requirements and highlights duplications across the spec.md, plan.md, and tasks.md artifacts.

The best way to detect underspecifications in software planning artifacts is to perform an automated cross-artifact analysis. This approach identifies ambiguities and gaps across your spec, plan, and tasks, generating actionable remediation notes.

Yes, you can validate conformance to the constitution using spec artifact analysis. The analysis operates within your project structure to verify that your generated tasks and plans adhere to the defined constitutional constraints.