Requirements Lead · Pro
An AI requirements lead who runs the whole session
A notetaker waits for people to volunteer needs. The Requirements Lead runs the session: it drives a structured agenda, proposes likely requirements and risks the group has not named, asks them to accept or rewrite, and records what they confirm. Use it in a Teams or Zoom workshop, or as a typed elicitation session in the app, and walk out with a BRD-lite, use-case catalog, NFR register, and recommendations.
What she does in the room
Your one job is to run a complete requirements elicitation session: drive a structured agenda, propose likely requirements and risks the group has not named, give recommendations, and record what they confirm. That is the whole role.
Drive the session. Work the agenda phase by phase and do not wait for the group to volunteer the next topic. After each answer, propose one or two likely requirements, NFRs, use cases, or risks they have not mentioned, then ask them to accept, rewrite, or reject. Give recommendations when a trade-off or gap is clear. Capture confirmed items with the matching tool; log proposals you made with capture_recommendation until they confirm.
The questions she actually asks
She opens by working out what the session is for, then presses on whatever is vague or unowned. These are her real prompts, not paraphrases:
- “What problem or opportunity should this session pin down first?”
- “Who is affected, and who decides what is in scope?”
- “What would a successful outcome of this session look like?”
- “What does done look like for that?”
- “A common requirement here is an audit trail of who changed what — is that in or out?”
- “Who is the actor, and what outcome do they need?”
- “I'd flag a dependency on the source system being available — is that a real risk for you?”
What she listens for
Across the meeting she is collecting the business problem, goals and success criteria, stakeholders, pain points, use cases, functional requirements (with MoSCoW and acceptance criteria when stated), non-functional requirements, constraints, out-of-scope items, decisions, action items, risks / dependencies / assumptions, and your own recommendations (logged separately from confirmed requirements). She records only what participants actually said — when something is missing she asks rather than fills it in.
Captured as structured items
- Problem statement
- Goal
- Requirement
- Non-functional requirement
- Stakeholder
- Out of scope
- Pain point
- Use case
- Constraint
- Recommendation
You walk out with
- BRD-lite
- Use-case catalog
- NFR register
- User stories
- Recommendations
Session presets
- Kickoff
- Requirements workshop
- Discovery
Meetings people use this for
- Requirements workshops
- Discovery interviews
- Kickoffs that need a first-cut BRD
- Async elicitation in chat
Getting her in the call
Paste a Teams or Zoom join link, pick Requirements Lead, and she dials in as a named participant — no tenant install and no admin consent. She introduces herself as Ava by default; you can rename her and change her voice per persona in settings.
Included in the free 60-minute trial, then part of Pro at $39/month. General Notetaker and Business Analyst stay free.
Adjacent personas
Different meeting, different seat. These are the personas closest to this one: