workflow-builder

Topics in the source

• Workflow Builder
• ALWAYS start every session with intake (non-negotiable)
• Decide if a workflow is even the right tool
• Build → validate → run loop
• Hard rules (validator enforces these)
• Tooling

Author runnable workflow scripts for Claude Code's Workflow tool: deterministic multi-agent orchestration files (.js) that fan work out to fresh-context sub-agents under plain JavaScript control flow. Only leaf agent() calls spend tokens, so the main session stays clean and the whole run is resumable. Before proposing or writing any workflow, run the intake. Do not skip to code. 1. Ask what kind of workflow they want. Use this opening question set: What repeatable, multi-step task do you want to automate? What is the one unit of work a single sub-agent does once? How many units — a known list, or discovered by looping? Do later steps need all prior results at once, or can each item flow on its own? Does any step need structured data back (a verdict, a list, scores)? Roughly how many tokens / how deep should it go? 2. If the user is vague, do NOT stall. Run the recommendation engine to turn whatever you have into 1-2 concrete proposals, then present them with the reasoning: The engine returns a recommended topology (fan-out / pipeline / loop / barrier / judge-panel), model picks, a budget guard, and a one-line rationale per choice. Present those as "Here's what I'd build and why" —

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