agentleFS
Sign inStart free
darkweb19darkweb19/skills/agent-workflow-designer/SKILL.md

agent-workflow-designer

Skill0 starsChanged 28 days agoApache-2.0View on GitHub

Design production-grade multi-agent workflows with clear pattern choice (sequential, parallel, hierarchical), handoff contracts, failure handling, and cost/context controls. Use when architecting a multi-step agent pipeline, choosing between single-agent vs multi-agent approaches, or refactoring an LLM workflow that suffers from context bloat or unreliable handoffs.

7 other projects use a version of this, 3 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 3 are common, 0 are distinctive, and 0 are very specific to this project.

  • 3

    Common

    Most of the 5 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Add retry/timeouts and output validation gates.

    line 66
  2. Common:

    Start with the smallest pattern that can satisfy requirements.

    line 80
  3. Common:

    Keep handoff payloads explicit and bounded.

    line 81

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

# 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free