spec-validator

An adversarial specification review uses multiple independent skeptic agents to attack a spec for ambiguity, omissions, contradictions, and malicious-compliance scenarios. It confirms defects through majority validation, ensuring only issues identified by multiple reviewers are reported for follow-up.

Adversarial review detects untestable acceptance criteria by having independent reviewers stress-test the specification for vague requirements. Confirmed findings are aggregated into a structured validation report, highlighting criteria that cannot be objectively tested before planning.

Adversarial review applies to drafted specifications for features, bug fixes, and refactors that include measurable acceptance criteria. It stress-tests these documents to uncover edge-case gaps and unclear behavior before creating an implementation plan.

Majority-based confirmation deduplicates findings from three independent reviewers and confirms only issues identified by at least two. Single-reviewer findings are preserved separately, ensuring the persisted validation report focuses on consensus defects.

Adversarial review is unnecessary for specifications without measurable acceptance criteria or design documents not yet drafted. It targets completed specs needing validation before implementation planning, not early-stage ideation or informal feature requests.