speckit.analyze

Cross-artifact quality analysis identifies inconsistencies, duplications, ambiguities, and underspecified items across spec.md, plan.md, and tasks.md. It runs after tasks.md is complete and outputs a structured report detailing findings.

Cross-artifact analysis is a read-only process that outputs a structured report and optional remediation guidance. It requires explicit approval before performing any edits, ensuring your project specifications remain non-destructive during validation.

Validating requirements coverage before implementation is best done by mapping tasks to requirements and highlighting coverage gaps. This analysis validates against constitution constraints to ensure no conflicting or missing edge cases exist across artifacts.

You need read-only quality analysis after speckit.tasks has produced a complete tasks.md. Running it at this stage targets the three core artifacts within your repository to identify duplications and underspecified items before implementation begins.

Yes, this analysis highlights conflicting or missing requirements and edge cases across your technical plan. It performs cross-artifact validation to detect ambiguities and coverage gaps, providing a structured report of the findings.

Underspecified items occur when tasks.md lacks sufficient detail relative to spec.md. Cross-artifact analysis identifies these inconsistencies by comparing the three core artifacts, outputting a structured report with optional remediation guidance to resolve them.