All agents · Project, product, and strategy
Requirements and Specification Draft
BetaA requirements spec (goals, prioritized requirements, out of scope, open questions) where every requirement traces to the stakeholder notes.
How it works
Paste the client brief, discovery-call notes, or stakeholder emails. Requirements are only written when the notes support them; priority is "not stated" unless someone said must/should/could.
What you give it
- Pasted text
- .txt
- .md
- PDF with a text layer
Limitations
- Does not estimate effort or cost.
- Conflicting stakeholder statements are listed as open questions, not resolved.