agent workflow designer
- Repo stars 15,974
- Author repo claude-skills
- Domain
- Design
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @alirezarezvani · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# Agent Workflow Designer
**Tier:** POWERFUL
**Category:** Engineering
**Domain:** Multi-Agent Systems / AI Orchestration
---
## Overview
Design production-grade multi-agent workflows with clear pattern choice, handoff contracts, failure handling, and cost/context controls.
## Core Capabilities
- Workflow pattern selection for multi-step agent systems
- Skeleton config generation for fast workflow bootstrapping
- Context and cost discipline across long-running flows
- Error recovery and retry strategy scaffolding
- Documentation pointers for operational pattern tradeoffs
---
## When to Use
- A single prompt is insufficient for task complexity
- You need specialist agents with explicit boundaries
- You want deterministic workflow structure before implementation
- You need validation loops for quality or safety gates
---
## Quick Start
```bash
# Generate a sequential workflow skeleton
python3 scripts/workflow_scaffolder.py sequential --name content-pipeline
# Generate an orchestrator workflow and save it
python3 scripts/workflow_scaffolder.py orchestrator --name incident-triage --output workflows/incident-triage.json
```
---
## Pattern Map
- `sequential`: strict step-by-step dependency chain
- `parallel`: fan-out/fan-in for independent subtasks
- `router`: dispatch by intent/type with fallback
- `orchestrator`: planner coordinates specialists with dependencies
- `evaluator`: generator + quality gate loop
Detailed templates: `references/workflow-patterns.md`
---
## Recommended Workflow
1. Select pattern based on dependency shape and risk profile.
2. Scaffold config via `scripts/workflow_scaffolder.py`.
3. Define handoff contract fields for every edge.
4. Add retry/timeouts and output validation gates.
5. Dry-run with small context budgets before scaling.
---
## Common Pitfalls
- Over-orchestrating tasks solvable by one well-structured prompt
- Missing timeout/retry policies for external-model calls
- Passing full upstream context instead of targeted artifacts
- Ignoring per-step cost accumulation
## Best Practices
1. Start with the smallest pattern that can satisfy requirements.
2. Keep handoff payloads explicit and bounded.
3. Validate intermediate outputs before fan-in synthesis.
4. Enforce budget and timeout limits in every step.
Sections and files
Listed in source order.
sections -> Overview → Core Capabilities → When to Use → Quick Start → Pattern Map → Recommended Workflow
terms -> Tier · Category · Domain · Design production-grade multi-agent workflows with clear pattern choice, handoff contracts, failure handling, and cost/context controls. · 1. Select pattern based on dependency shape and risk profile. · 1. Start with the smallest pattern that can satisfy requirements.
files/cmd -> sequential · parallel · router · orchestrator · evaluator · references/workflow-patterns.md · scripts/workflow_scaffolder.py
body sha256 -> e85adb0994b8
Overview
Design production-grade multi-agent workflows with clear pattern choice, handoff contracts, failure handling, and cost/context controls.
Core Capabilities
Workflow pattern selection for multi-step agent systems Skeleton config generation for fast workflow bootstrapping Context and cost discipline across long-running flows Error recovery and retry strategy scaffolding Documentation pointers for operational pattern tradeoffs
When to Use
A single prompt is insufficient for task complexity You need specialist agents with explicit boundaries You want deterministic workflow structure before implementation You need validation loops for quality or safety gates
Pattern Map
sequential: strict step-by-step dependency chainparallel: fan-out/fan-in for independent subtasksrouter: dispatch by intent/type with fallbackorchestrator: planner coordinates specialists with dependenciesevaluator: generator + quality gate loopRecommended Workflow
Select pattern based on dependency shape and risk profile. Scaffold config via
scripts/workflow_scaffolder.py. Define handoff contract fields for every edge. Add retry/timeouts and output validation gates. Dry-run with small context budgets before scaling.