speckit-analyze

To check for inconsistencies between spec, plan, and tasks files, you can analyze these specification artifacts to surface cross-artifact gaps and mismatches. This process identifies ambiguities and overspecifications to align teammates before starting work.

Cross-artifact traceability analysis is a non-destructive review process that validates task generation results by surfacing gaps between functional requirements, acceptance criteria, and implementation tasks across specification documents.

You validate task generation results by running an analysis against your feature folder to surface cross-artifact issues. This identifies mismatches between functional requirements and acceptance criteria to ensure alignment before development.

Yes, analyzing specification artifacts can identify missing functional requirements in task lists. The review specifically targets cross-artifact inconsistencies, revealing task gaps and overspecifications that hinder progress before work begins.

No, cross-artifact analysis satisfies requirements for non-destructive review. It generates traceable findings and structured reports that feed into the workflow without modifying the original spec.md, plan.md, and tasks.md artifacts.

You should run a specification consistency check before starting work to surface functional requirements, acceptance criteria, and task gaps. This validates task generation results and aligns teammates on the feature folder artifacts.