speckit.analyze

To check consistency and quality across project artifacts, you can automate cross-artifact analysis that detects duplications, ambiguities, and underspecifications. This process ensures your spec.md, plan.md, and tasks.md files align with project requirements without manual review.

Validating generated tasks against a project constitution requires a read-only analysis that checks for alignment. Running a post-task generation analysis ensures your tasks.md output complies with defined project principles and identifies any compliance gaps.

Artifact consistency analysis does not modify your spec.md or tasks.md files. It performs a read-only evaluation and outputs a structured report detailing ambiguities, duplications, and underspecifications, leaving your original project artifacts untouched.

You automate post-task generation validation by running an analysis skill immediately after task generation. This validates the output by checking for duplications, ambiguities, and underspecifications across your spec.md, plan.md, and tasks.md artifacts.

Yes, you need knowledge of project artifacts and the constitution before running specification analysis. Understanding your spec.md, plan.md, and tasks.md content is required to effectively identify ambiguities and ensure constitution alignment.