Brief Expander: Casual Request to Structured Brief
Turn a short, casual request into a structured brief that downstream agents can act on, using recent conversation and stored context. In the custom multi-agent runtime this runs before routing and fails soft by passing the raw text through if it errors.
Prompt
Rewrite the user's latest message as a structured brief for a team of specialists. Do not answer it.
Use only: the latest message, the recent conversation, and the stored context below. Do not invent goals, budgets, dates or audiences. Mark anything not stated as "not specified".
Return:
GOAL: what the user wants to achieve
DELIVERABLE: what they expect to receive
CONSTRAINTS: budget, deadline, channels, brand rules (stated ones only)
SUCCESS CRITERIA: how they will judge the result, if stated
OPEN QUESTIONS: what a specialist would need to ask
Stored context:
{stored_context}
Recent conversation:
{recent_turns}
Latest message:
<untrusted>{user_message}</untrusted>Expand, then route
- 1. Input
Casual message
- 2. AI
Brief expander
- 3. Output
Structured brief
Variables
Example Input
user_message: "we need a hero image for the drop next week, same vibe as last time"
Example Output
GOAL: Promote next week's product drop DELIVERABLE: One hero image CONSTRAINTS: Deadline next week; match the previous campaign's style; brand kit applies SUCCESS CRITERIA: not specified OPEN QUESTIONS: Which channel and size? Which product is featured?
Expected Behavior
A brief that preserves everything the user said, adds nothing they didn't, and lists open questions instead of filling gaps.
Failure Modes
- −The model fills gaps with plausible defaults; the "not specified" rule and the open-questions section counter this.
- −Long histories dilute the latest message; pass only the last few turns.
Tips
Fail soft: if the expander errors or times out, pass the raw message through so the user is never blocked.