Spec-Driven Verification
YAML specs define exactly what 'done' means. No ambiguity. No AI judgment.
The Problem It Solves
Incomplete Implementations: AI delivers 95% garbage on first attempt. Tests missing, error handling stubbed, edge cases ignored. The skeleton looks complete but the hard parts are TODOs.
How It Works
CleanAim defines 'done' explicitly. Our YAML specification files declare exactly what a complete implementation requires: which files must exist, which patterns must be present, which tests must pass. No ambiguity. No AI judgment.
The verify-wp.py system checks every specification before completion can be claimed. 42 spec files define 137 must_exist rules and 140 must_contain patterns. If the spec says a test file must exist, it must exist—or the task isn't done.
Placeholders trigger failures. Our pattern matching detects TODO comments, stub implementations, and incomplete error handling. The AI can't declare victory while leaving the hard parts for you.
Key Components
YAML Specification Files
42 spec files define exact requirements for each work package. Files, patterns, tests—all explicit.
must_exist Rules
137 rules verify required files are present. Missing test file? Missing migration? Caught automatically.
must_contain Patterns
140 patterns verify required code is present. Error handling, logging, validation—all verified.
Placeholder Detection
TODO comments, stub implementations, and incomplete patterns trigger failures. No shortcuts allowed.
The Evidence
Stop accepting half-finished work
See how spec-driven verification works in your workflow.
Get Your Diagnostic