speckit-analyze

Checking project specifications for inconsistencies requires cross-verifying spec, plan, and task documents to detect duplications, ambiguities, and coverage gaps. This ensures project coherence and confirms readiness for implementation through a read-only assessment.

Specification coverage assessment evaluates task lists against documented requirements to highlight missing or orphaned elements. It works by performing a read-only analysis of planning artifacts to detect duplications and verify that all requirements are addressed.

Identifying security risks in project planning documents involves analyzing specifications to detect potential conflicts with project principles. This read-only risk identification highlights potential security concerns before implementation begins.

You can cross-verify spec.md, plan.md, and tasks.md files automatically by running a comprehensive analysis command. This non-destructive process evaluates task coverage against requirements and outputs a detailed report on found inconsistencies.

Project artifact analysis does not modify your existing specification files. The assessment is strictly read-only, performing a non-destructive evaluation of your documents to detect ambiguities and coverage gaps without altering the original artifacts.

You should run a specification consistency check before implementation to ensure all requirements are addressed in the task list. This verifies project coherence, detects oversights in planning documents, and confirms readiness for the development phase.