Front page / By role / Requirements from a meeting
Requirements from a meeting
From a meeting transcript to traced requirements: every requirement with the line it came from, decisions and actions, gaps and conflicts, and a follow up email.
For Business analyst, Product owner
What was the meeting about?
One line is enough. Step 1 asks the rest in your AI app, and nothing is done until you approve the brief it writes.
In the case folder's materials/: The meeting transcript or notes in materials/.
The 6 steps
- 01
Set the scope
Then you approve, before the next step starts.
- 02
Pull out the requirements
- 03
Log decisions and actions
- 04
Find gaps and conflicts
Steps 2 to 4 run at the same time, one agent each.
- 05
Trace every requirement
Then you approve, before the next step starts.
- 06
Write the requirements
The agents
decision-logger- Logs the decisions, action items and open questions in a meeting and writes outputs/03-decisions-actions.md.
gap-finder- Finds contradictions, vague words, missing acceptance criteria and unstated assumptions in a meeting, and writes outputs/04-gaps.md.
requirement-extractor- Pulls every requirement out of a meeting transcript or notes, with the line it came from, and writes outputs/02-requirements.md.
trace-checker- Checks that every extracted requirement traces to a line in the meeting and grades it, writing outputs/05-trace.md.
Where things stay
- On your computer
- Your files in materials/, every result in outputs/, the work itself. It runs in your AI app, on the plan you already pay for.
- With Cheatcode
- The steps, the gates and how far each case has come, so a case survives closing the app. See your cases.