Transcripts, documents, and scenarios go in. Evidence-scored, architect-approved specifications come out — with every claim traced to a source in your actual codebase.
Meeting transcripts, requirement docs, or a scenario canvas — Spec Forge turns them all into the same rigorous artifact.
Detection and Evidence scores quantify how well-understood and how well-grounded a spec is — before anyone commits a sprint to it.
An architect signs off on a scored, sourced document — not a hunch. The approval is sealed into the receipt.
“Sprint planning stopped being an argument about what the ticket means. The spec settles it, with sources.”
The Detection score captures how completely the requirement was understood at intake — and it never silently changes. A 55 stays a 55, on the record.
The Evidence score climbs as claims get grounded against the indexed codebase — you watch a spec earn its confidence.
Statements in the spec cite the chunks that support them — services, screens, ADRs — so review means checking sources, not trusting prose.
Business view reads like a brief; engineering view exposes the technical mapping. Same spec, no forked truth.
Paths and topics the spec deliberately leaves out are recorded with the reason — scope cuts stop being silent.
Architect approval locks the spec version into the delivery receipt — the same hash that follows the feature to the merged PR.
Thirty minutes. Your stack. Bring one real feature request.