Skip to content

docs: make downloadable workflow migration guide a genuine agent task spec#1086

Open
bets-margulies-vapi wants to merge 1 commit into
mainfrom
claude/workflow-migration-agent-spec
Open

docs: make downloadable workflow migration guide a genuine agent task spec#1086
bets-margulies-vapi wants to merge 1 commit into
mainfrom
claude/workflow-migration-agent-spec

Conversation

@bets-margulies-vapi

Copy link
Copy Markdown
Contributor

What

Follow-up to #1081. The downloadable static/workflow-migration-guide.md that shipped in #1081 was really the human guide reflowed into plain markdown — readable by an LLM, but not tailored for one. This rewrites it as an actual agent migration spec.

Why

An agent doing the migration needs the transformation contract, not prose. The previous file described steps in words ("add a handoff tool", "configure variable extraction") but never gave the input/output JSON shapes or a worked transform, so a model couldn't reliably emit valid output.

Changes

  • static/workflow-migration-guide.md rewritten as a task spec:
    • Task framing ("you are migrating a Workflow to a Squad; here's the spec, produce valid output")
    • Input Workflow schema (node types, extractVariables, edges, isGlobal, …)
    • Output Squad / assistant / handoff-tool schemas (grounded in the real shapes in squads/handoff.mdx, squads.mdx, and the clinic-triage example — no invented fields)
    • Deterministic 8-step transform procedure + node→construct quick-reference table
    • A full worked input → output example (the biggest gap before; few-shot transforms are what make a model produce correct structured output)
    • Variable-extraction rules that encode real judgment (only add a variableExtractionPlan when a var crosses an assistant boundary; branch-selector vars need none)
    • "When to stop and ask the human" + a validation checklist
  • workflows/legacy-migration.mdx: updated the download blurb to describe it as a task spec (schemas + worked example), and to point the model at GET /workflow/{id} as the input.

Note

The worked example uses a fictional "Acme Dental" workflow because it exercises a conditional branch + a cross-boundary variable cleanly. Happy to swap it for a real example doc if preferred.

🤖 Generated with Claude Code

https://claude.ai/code/session_01KfSaT4cFb2DggCYTctrzEq


Generated by Claude Code

The merged .md was the human guide reflowed into plain markdown. Rewrite
it as an agent-oriented migration spec: task framing, the input Workflow
schema, output Squad/assistant/handoff-tool schemas, a deterministic
transform procedure, a full worked input->output example grounded in the
real API shapes, variable-extraction rules, when-to-ask guidance, and a
validation checklist. Update the page blurb to match.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KfSaT4cFb2DggCYTctrzEq
@github-actions

Copy link
Copy Markdown
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants