ap-workflows

ap-workflows

When to use

• Work needs ordered phases where each phase fans out agents that run in parallel.
• A later stage must act on an earlier stage's output (produce → review → fix).
• You have a ready AIP-15 WORKFLOW.md (+ optional entry.mjs) to run as-is.

Start a pipeline

workflow_start({
  "workflowId": "review-then-fix",
  "stages": [
    { "label": "produce", "steps": [
        { "label": "plan", "adapter": "claude-code", "prompt": "Draft the migration plan for src/auth." }
    ]},
    { "label": "review", "steps": [
        { "label": "review-a", "adapter": "claude-code", "prompt": "Review the plan for data-loss risks." },
        { "label": "review-b", "adapter": "claude-code", "prompt": "Review the plan for test coverage." }
    ]},
    { "label": "fix", "steps": [
        { "label": "fixer", "sessionRef": "review-a", "prompt": "Address the review comments." }
    ]}
  ]
})
// → { "runId": "wf_..." } — execution is background; returns immediately.

Steps within a stage run CONCURRENTLY. Stages are barriers: stage N+1 does not start until every step of stage N has finished (or failed). adapter spawns a NEW session for the step; sessionRef (a prior step's label, any earlier stage) reuses that session instead — ignoring adapter.

Poll and steer

workflow_status({ "runId": "wf_..." })
// → per-stage: each step's status + sessionId — read earlier output via ap-read-output on that id
workflow_cancel({ "runId": "wf_..." })   // in-flight steps finish; no new stage starts
workflow_list({})                        // running / done / failed / cancelled runs

Run a WORKFLOW.md file

workflow_run_file({
  "path": "workflows/morning-sweep/WORKFLOW.md",
  "input": { "date": "2026-09-01" },
  "cacheKey": "morning-sweep-2026-09-01"
})

Loads the AIP-15 file via the workflow-loader and runs it through the same runner as workflow_start, in the background. With a cacheKey, cacheable steps replay unchanged output on re-invocation instead of re-spawning.