spec-kit-analyze

To check for inconsistencies between spec, plan, and tasks files, run a cross-artifact analysis to detect duplications, ambiguities, and underspecified items. This process surfaces actionable remediation opportunities without modifying your original markdown files.

Cross-artifact analysis in software spec planning identifies mismatches, duplications, and underspecified items across spec, plan, and tasks documents. It highlights findings with risk severities to ensure traceability and alignment without altering your files.

Audit tasks.md against spec.md and plan.md by running a non-destructive analysis after task generation. This flags underspecified items and ambiguities, producing a compact, structured report with risk severities and optional remediation guidance.

Yes, you can analyze spec and plan documents without modifying the files by using a non-destructive audit process. It reads your markdown artifacts and outputs a separate structured report detailing findings and remediation opportunities.

Run a spec kit audit on your tasks immediately after a complete tasks.md file is generated. Applying the analysis at this stage ensures all cross-artifact inconsistencies and underspecified items are caught early before implementation begins.

Spec plans often have underspecified items and ambiguities due to misalignment across separate planning documents. A structured cross-artifact analysis identifies these exact gaps, maps them to tasks, and provides remediation guidance to resolve them.