orchestration-workflow-builder

Compose multi-step agent workflow DAGs with routing, approvals, RAG, and audit steps.

Updated Jul 28, 2026
One-click install
npx skills add https://github.com/human-centric-engineering/resparkable --skill orchestration-workflow-builder-human-centric-engineering
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: orchestration-workflow-builder
Source: https://github.com/human-centric-engineering/resparkable/tree/main/.claude/skills/orchestration-workflow-builder
Command: npx skills add https://github.com/human-centric-engineering/resparkable --skill orchestration-workflow-builder-human-centric-engineering

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Building multi-step agent pipelines by hand is error-prone: invalid DAG edges, missing required config, mismatched route conditions, and silent runtime failures. This Skill guides the composition of valid, production-ready workflow definitions for the Resparkable orchestration engine, covering all 19 step types, error strategies, versioning, and validation rules. ## Core Features & Use Cases - DAG Composition: Wire steps across 19 step types — llm_call, route, guard, evaluate, judge_call, human_approval, rag_retrieve, external_call, parallel, supervisor, report, and more — with correct config and conditional edges. - Quality & Audit Patterns: Add post-hoc supervisor audits with evidence-cited verdicts and deterministic Markdown reports, with run-time opt-out toggles for operators. - Validation & Gotcha Avoidance: Apply backend validator rules (required config, reachability, cycle detection), semantic validation of agent/capability/model references, and documented failure modes like LLM-mode guards hallucinating on closed-set checks. - Use Case: Build a customer-support workflow that classifies intent with a route step, retrieves knowledge-base context via rag_retrieve, drafts a reply, gates it through a schema-mode guard, pauses for human approval, then sends a notification with a supervisor verdict attached. ## Quick Start Ask the agent to build a workflow that routes incoming support requests to the right agent, adds a human approval gate before sending, and ends with a supervisor audit and report.

Frequently Asked Questions about orchestration-workflow-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a multi-step agent workflow with approval gates?▼

Define a WorkflowDefinition with an entryStepId, errorStrategy, and steps array. Chain llm_call or agent_call steps, insert a human_approval step with a required prompt, and wire edges via nextSteps. Validate with validateWorkflow before publishing.

What is the difference between evaluate, judge_call, guard, and supervisor steps?▼

Evaluate scores one step's output against a rubric, judge_call drives a named judge agent on a QA pair, guard applies binary pass/fail rules via LLM, regex, or Zod schema, and supervisor audits the entire execution trace with an independent judge model.

Why does my LLM-mode guard reject valid enum values?▼

LLM-mode guards hallucinate on closed-set membership checks even with the spec in the prompt. Use mode 'schema' with a registered Zod schema instead — it is deterministic, zero-cost, and validates against the same constants as the apply layer.

Does editing a workflow via PATCH change running executions?▼

No. PATCH writes to draftDefinition only; running executions, schedules, and triggers stay pinned to the published version. Changes go live only after POST /publish snapshots the draft as a new immutable version.

Why did my external_call step fail with a 401 or 422 error?▼

The authType likely mismatches the vendor's header contract — for example Brave Search requires api-key with X-Subscription-Token, not bearer. Also check that interpolated query parameters stay under vendor length limits such as Brave's 400-character cap.

Can I re-run a failed workflow execution from a specific step?▼

No, the rerun granule is the whole execution. POST /executions/:id/rerun creates a new execution against a chosen workflow version with parentExecutionId lineage; per-step partial reruns are not supported.