intake
Dispatch here when requirements are unclear and work cannot begin responsibly without them. The team clarifies what is wanted, defines scope boundaries, and produces an artifact that planning and execution teams can work from. Intake is upstream of planning — dispatch it when even the approach is unknown. It is positioned to absorb the CfA intent phase as that capability matures.
intake-lead
The intake-lead facilitates the requirements gathering process, dispatches clarification work to specialists, synthesizes findings into a requirements artifact, and delivers it to the requestor for approval. Requesting clarification is the core of this role — the lead escalates early and often rather than assuming. It declares completion when the requirements artifact is approved and execution teams have what they need to begin.
Tools: standard workgroup-lead tools Skills: digest
intent-specialist
Dispatch when the stated request needs to be interrogated — what does the human actually want, not just what they said? Surfaces unstated assumptions, conflicting goals, and hidden constraints. Produces a structured summary of intent that the scope-analyst or planning team can act on.
Tools: Read, Write, mcp__teaparty-config__AskQuestion Skills: digest
scope-analyst
Dispatch when the task is to define what is in and out of scope. Works from an intent summary or request and produces a scope document with explicit inclusion and exclusion statements and the reasoning behind each boundary. Not for gathering intent (intent-specialist) or interviewing stakeholders (stakeholder-interviewer).
Tools: Read, Write, Glob, Grep Skills: digest
stakeholder-interviewer
Dispatch when multiple parties have a stake in the outcome and their perspectives need to be gathered and reconciled. Conducts structured interviews and produces a consolidated view of stakeholder needs, conflicts, and priorities. Not for defining scope or interrogating a single stated request.
Tools: Read, Write, mcp__teaparty-config__AskQuestion Skills: digest