speckit-analyze

To check for inconsistencies across spec, plan, and tasks files, you can analyze the artifacts to detect duplicate requirements, conflicting details, and coverage gaps. This auditing process ensures artifact coherence before you begin implementation.

Spec artifact coverage analysis is the process of mapping generated tasks to original requirements to highlight coverage gaps. It ensures every requirement in spec.md is accounted for in plan.md and tasks.md, maintaining a healthy specification process.

To validate constitution alignment and task coverage, run an analysis pipeline command after task generation. This verifies that your spec.md, plan.md, and tasks.md artifacts satisfy project rules and identify any missing or ambiguous items.

Yes, you can flag ambiguous or underspecified requirements in spec documentation by running an artifact analysis command. This process identifies unclear items across your spec, plan, and tasks files and proposes clarifications.

You need to audit spec, plan, and tasks artifacts for duplications immediately after task generation and before implementation starts. This prevents conflicting requirements from propagating into your codebase during the development phase.