Best for
- Projects where requirements live in chat history
- Keeping an AI team building what was actually asked
- Audits and handovers that ask 'why does this exist?'
What you give it
- The requirement in your words, and where it came from
- Answers to the gaps it finds
What you get back
- Numbered requirement entries with pass/fail acceptance criteria
- Each entry traced to its source and mapped to a milestone
- Conflicts with existing requirements surfaced, not overwritten
How it works
- Reads the existing requirements document and finds the right section.
- Writes each requirement so a tester can mark it pass or fail.
- Records the source — who asked, when, in what words.
- Maps the entry to a milestone, or flags that none fits.
- Checks for contradictions with what is already written and raises them.
Example
You: Add: corporate customers can pay by invoice with 30-day terms, retail customers cannot.
Result: Two numbered entries with criteria, a trace to your message, a link to the payments milestone, and one surfaced conflict with an older 'all payments are card' requirement — resolved your way, on the record.
Limits — please read
- Garbage in, numbered garbage out — it structures, you decide.
- It maintains the document; it does not prioritise the roadmap.
- Contradictions are surfaced for you to resolve, never auto-resolved.