validate-spec

Specification validation checks essential sections like Summary, Problem Statement, Acceptance Scenarios, Agent Context, Out of Scope, and Dependencies to ensure structural completeness and compliance before approval. It provides clear remediation guidance for any identified gaps.

Post-implementation validation verifies specifications against acceptance scenarios and compliance requirements after development. It detects the spec status to apply mode-aware checks, ensuring the implementation matches the approved specification.

Specifications must include Summary, Problem Statement, Acceptance Scenarios, Agent Context, Out of Scope, and Dependencies sections to pass structural completeness validation. Missing any of these essential sections triggers remediation guidance.

Mode-aware validation detects pre- or post-implementation mode based on spec status signals, applying appropriate checks for draft, in_progress, or approved states. This ensures validation logic matches the current lifecycle stage of the specification.

Automating specification quality assurance involves running validation checks across the spec lifecycle to verify completeness and compliance. The process highlights gaps, suggests concrete remediation, and applies lightweight readiness criteria before approval.

Specification validation fails when acceptance scenarios are missing because they are an essential structural component required for completeness. The validator highlights this gap and provides concrete remediation guidance to add the missing section.