How the application exposes incomplete specifications before review.
Readiness and traceability
The readiness score
A feature's readiness is the percentage of six signals that are present: description, owner, at least one requirement, expected behavior, verification strategy, and at least one verification scenario. It is a completeness prompt, not proof that the content is correct.
Validation findings
| Finding | Severity |
|---|---|
| Feature intent is missing | Error |
| No owner assigned | Warning |
| No requirements defined | Error |
| Expected behavior is missing | Error |
| Verification strategy is missing | Warning |
| A requirement has no linked scenario | Error |
Traceability direction
Verification scenarios store linked requirement IDs. The application can therefore reveal uncovered requirements without duplicating scenario content on every requirement. Stable requirement IDs are the join between intent and verification planning.