speckit-analyze

You can validate project specification consistency by analyzing artifacts like spec.md, plan.md, and tasks.md to identify conflicting requirements, duplications, and ambiguities, providing structured feedback for better alignment and quality assurance.

Specification consistency checking evaluates project planning artifacts to find gaps and underspecified items. You need it after task generation to verify requirement coherence and ensure alignment with project principles before starting implementation.

Analyze spec.md and plan.md by evaluating them against project principles to detect underspecified items and gaps in task coverage, generating an immediate report on specification quality and completeness for quality assurance.

Yes, you can validate requirements alignment automatically by checking planning artifacts for compliance with core project principles, ensuring that specifications adhere to the project constitution and identifying deviations.

The best way to check task coverage completeness is to analyze tasks.md alongside specification documents to evaluate whether all requirements are fully covered, identifying gaps and preventing underspecified implementation items.

Specification ambiguities detected in project artifacts include conflicting information across documents, duplicated requirements, underspecified items, and missing information that creates gaps in task coverage and project alignment.