interview

Topics in the source

• Phase 1 — Interview → Plan
• The six intake slots (ask one at a time; use AskUserQuestion for choices)
• Workflow
• Hard rules
• Forcing-question library (recommend + cite)
• Tools

Open warmly with one or two examples from ../../references/examples-bank.md, then interview the founder into a build sheet. No API key needed in this phase — the output is a plan. | Slot | Question | Maps to | |---|---|---| | Job | "What one job should this agent do end-to-end?" | agent.system + outcome description | | Trigger | "What kicks it off — you ask it, an event, or a schedule?" | on-demand / event / cron | | Inputs | "What does it read?" (files, repo, memory, gmail/slack/github, web) | resources / MCP servers / memory | | Actions | "What does it do?" (draft, write, call APIs, run code) | agent toolset / custom tools / MCP | | Done | "How would you grade a good run?" | outcome rubric (required) | | Recurrence | "Once, on request, or on a cadence?" | single-pass / grade-loop / cron-loop | See ../../references/interview-to-config.md for the full mapping. 1. Interview. Walk the six slots. Capture the founder's own words — never invent specifics they didn't claim. 2. Map to primitives. MCP inputs become schema-true mock custom tools in v0 and a v1 deferral to wire the real server. Irreversible actions (send/publish) become v2 deferrals behind alwaysask. 3. Assemble the sheet. 4

This is an excerpt. Refer to the complete source and its current requirements.