Best for
- Founders who think out loud and need it captured properly
- Teams whose 'requirements' live in chat scrollback
- Handing work to builders (human or AI) without re-explaining
What you give it
- The idea or change in your own words — voice-note rough is fine
- Answers when it finds a gap or a contradiction
What you get back
- A one-paragraph vision statement for the change
- Numbered requirements, each testable, each traced to your words
- A list of decisions you implied — confirmed back to you before they become rules
How it works
- Reads what you wrote and what the product already does in the touched area.
- Separates facts you stated, decisions you implied, and gaps nobody has decided.
- Writes numbered, testable requirements that quote your words where it matters.
- Presents the implied decisions as questions — nothing becomes a rule silently.
- Files the result where your project keeps requirements, linked to its milestone.
Example
You: People keep asking for invoices. Companies need them, individuals don't care. Make it work somehow with our existing receipts.
Result: A vision line, six requirements (who gets invoices, what is on them, when they are issued, numbering, the receipts relationship, the edge case of a company buying as an individual) and three decisions flagged for confirmation.
Limits — please read
- It documents and questions; it does not build.
- A requirement is only as good as your answers — it flags gaps, you close them.
- It reads your project for context; an empty project gives it only your words.