Agent skill

Orchestration Patterns

by bybren-llc in bybren-llc/safe-agentic-workflow

Agentic orchestration patterns for long-running tasks. An agent skill from bybren-llc/safe-agentic-workflow.

MITAuto-check passedAgent Workflows

Install Orchestration Patterns

skills CLI
$ npx skills add bybren-llc/safe-agentic-workflow --skill orchestration-patterns -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install bybren-llc/safe-agentic-workflow orchestration-patterns --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/bybren-llc/safe-agentic-workflow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.gemini/skills/orchestration-patterns .claude/skills/orchestration-patterns && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
orchestration-patterns
GitHub stars
423
Token cost
~2k tokens
SKILL.md length
358 words
Files
2
Skills in repo
42
Repo updated
First seen
Licence
MIT

At a glance

Agentic orchestration patterns for long-running tasks. An agent skill from bybren-llc/safe-agentic-workflow.

  • Works in 4 steps: Separation of Concerns: QA validates but… → Independent Verification: Catches what… → Bias Prevention: Fresh eyes on commit… → …
  • Managing multi-step work
  • SKILL.md covers Purpose, When This Skill Applies, The Agent Loop and Evidence-Based Delivery, plus 6 more sections
  • Calls yarn

What it does

Orchestration Patterns is an agent skill from bybren-llc/safe-agentic-workflow. Agentic orchestration patterns for long-running tasks. Implements evidence-based delivery and iterative agent loops. Use when managing multi-step work, coordinating workflows, or orchestrating PR workflows.

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `README.md`).

It sits in Agent Workflows, covering Autonomous loops and Multi-agent orchestration. The repository describes itself as: SAW — SAFe Agentic Workflow AI Agent Harness for Multi-Agent Team Workflows Built on SAFe methodology (Scaled Agile Framework), adapted for AI agent teams (Now With AI-DLC!)… The licence is MIT.

When your agent uses it

  • Managing multi-step work
  • Coordinating workflows
  • Orchestrating PR workflows

Example prompts

  • “/orchestration-patterns”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Separation of Concerns: QA validates but doesn't write product code
  2. Independent Verification: Catches what implementer missed
  3. Bias Prevention: Fresh eyes on commit messages, patterns
  4. Evidence in Linear: QA posts final evidence + verdict to Linear (system of record)

What it can do on your machine

Read from SKILL.md and the folder at commit 26ca58b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • yarn

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use yarn, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Orchestration Patterns loads about 2k tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 358 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~57
When it runs · the whole SKILL.md, loaded when a task matches
~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from bybren-llc/safe-agentic-workflow at commit 26ca58b, republished under its MIT licence (© bybren-llc). 358 words, ~1,960 tokens.

Download SKILL.mdSave it as .claude/skills/orchestration-patterns/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
orchestration-patterns
description
Agentic orchestration patterns for long-running tasks. Implements evidence-based delivery and iterative agent loops. Use when managing multi-step work, coordinating workflows, or orchestrating PR workflows.

Orchestration Patterns Skill

Purpose

Codify evidence-based delivery and iterative agent loop for orchestrating complex, long-running tasks. These patterns ensure verifiable progress and intelligent escalation.

When This Skill Applies

  • Orchestrating multi-step implementation tasks
  • Managing work across multiple steps
  • Running long-running sessions that need checkpoints
  • Preparing PRs for merge (mandatory QA gate)
  • Coordinating team handoffs

The Agent Loop

Core Philosophy: "Iterate until success or blocked, then escalate."

text
┌─────────────────────────────────────────────────────────┐
│  THE AGENT LOOP (for every task)                        │
├─────────────────────────────────────────────────────────┤
│                                                         │
│  1. GOAL DEFINITION                                     │
│     └─ Clear acceptance criteria (from spec/ticket)     │
│                                                         │
│  2. PATTERN DISCOVERY                                   │
│     └─ Search codebase, docs, previous sessions         │
│     └─ Use: pattern-discovery skill (auto-invoked)      │
│     └─ Or: /search-pattern for explicit code search     │
│                                                         │
│  3. ITERATIVE EXECUTION LOOP:                           │
│     ┌─────────────────────────────────────────────┐     │
│     │  Implement approach                         │     │
│     │       ↓                                     │     │
│     │  Run validation (yarn ci:validate)          │     │
│     │       ↓                                     │     │
│     │  If PASS → proceed to evidence              │     │
│     │  If FAIL → analyze error, adjust, repeat    │     │
│     │  If BLOCKED → escalate with context         │     │
│     └─────────────────────────────────────────────┘     │
│                                                         │
│  4. EVIDENCE ATTACHMENT                                 │
│     └─ Attach proof to Linear (see templates below)     │
│                                                         │
│  5. QA GATE (MANDATORY before merge)                    │
│     └─ Independent review of PR                         │
│                                                         │
└─────────────────────────────────────────────────────────┘

Evidence-Based Delivery

Core Principle: "All work requires verifiable evidence - no 'trust me, it works'"

Evidence Types
TypeWhat It ProvesExample
Test ResultsCode works as expectedyarn ci:validate output
ScreenshotsUI changes are correctBefore/after comparison
Command OutputOperations completedBuild logs, migration logs
QA ReportIndependent verificationQA validation markdown
Session IDFull audit trail availableSession reference
Phase Evidence Requirements
PhaseEvidence RequiredLinear Template
DevTest results, command outputDev Evidence Template
StagingUAT validation or N/A + reasonStaging Template
DoneQA report, merge confirmationDone Evidence Template

QA Pre-Merge Gate

MANDATORY: Before merging any PR, perform independent review.

Why QA Gate Matters
  1. Separation of Concerns: QA validates but doesn't write product code
  2. Independent Verification: Catches what implementer missed
  3. Bias Prevention: Fresh eyes on commit messages, patterns
  4. Evidence in Linear: QA posts final evidence + verdict to Linear (system of record)
QA Review Checklist
markdown
## QA Review - PR #XXX for {{TICKET_PREFIX}}-YYY

### Commit Message Validation
- [ ] Ticket reference in subject line
- [ ] Proper format: `type(scope): description [{{TICKET_PREFIX}}-XXX]`

### Code Pattern Validation
- [ ] RLS context helpers used (no direct Prisma)
- [ ] Naming conventions followed
- [ ] File structure matches patterns

### CI Status
- [ ] All checks passing
- [ ] No new lint warnings

### Evidence Verification
- [ ] Dev evidence attached to Linear
- [ ] Acceptance criteria addressed

### Verdict
- [ ] APPROVED for merge
- [ ] CHANGES REQUESTED (list below)
Show full SKILL.md (142 more words)Show less
QA Output Location

All QA reports go to: docs/agent-outputs/qa-validations/{{TICKET_PREFIX}}-{number}-qa-validation.md

Escalation Patterns

When to Escalate
ConditionEscalate ToInclude
Blocked > 4 hoursTDMFull context, attempts made
Architecture ambiguityARCHitectOptions, trade-offs
Cross-team dependencyTDMWhich teams, what's blocked
Security concernSecEngSpecific risk, evidence
Escalation Template
markdown
**Escalation Required**

**Blocked On**: [specific blocker]
**Attempts Made**:

1. [what you tried]
2. [what you tried]

**Context**:

- Ticket: {{TICKET_PREFIX}}-XXX
- Session ID: [if available]
- Time blocked: X hours

**Request**: [specific ask - what do you need?]

Long-Running Task Checkpoints

For tasks spanning multiple steps or sessions:

Checkpoint Pattern
text
Every 10-15 steps:
1. Update progress with current state
2. If nearing limits, summarize state
3. If handoff needed, provide continuation context

At session boundaries:
1. Summarize completed work
2. List remaining items
3. Document any blockers
4. Attach evidence to Linear
State Preservation
markdown
**Session Checkpoint**

**Completed**:

- [x] Task 1
- [x] Task 2

**In Progress**:

- [ ] Task 3 (at step X)

**Remaining**:

- [ ] Task 4
- [ ] Task 5

**Blockers**: [if any]

**Next Action**: [specific next step]

Orchestration Workflow Example

text
# Complete workflow for feature implementation:

1. /start-work {{TICKET_PREFIX}}-XXX
   └─ Syncs to main, creates branch, sets context

2. Pattern discovery (skill auto-invokes or use /search-pattern)
   └─ Finds relevant patterns before implementation

3. [Implementation with agent loop]
   ├─ Implement
   ├─ Validate (yarn ci:validate)
   ├─ Adjust if needed
   └─ Repeat until passing

4. /pre-pr
   └─ Full validation checklist

5. Create PR with evidence

6. [QA GATE - MANDATORY]
   └─ Perform QA review
   └─ Fix any blocking issues
   └─ Commit QA report

7. Merge (only after QA approval)

8. /end-work
   └─ Updates Linear, cleans up

Reference

  • AGENT_WORKFLOW_SOP.md: Full agent workflow documentation
  • CONTRIBUTING.md: Workflow requirements
  • linear-sop skill: Evidence templates for Linear

Anti-Patterns to Avoid

Anti-PatternWhy It's BadDo This Instead
Skip QA reviewMiss commit message issuesAlways perform QA pre-merge
No evidence in LinearNo audit trailAttach evidence every phase
Ignore CI failuresBroken code reaches mainFix in agent loop, don't skip
Force-push without checkMay lose teammate's changesUse --force-with-lease
Continue when blockedWaste time, no progressEscalate with context

© bybren-llc, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .gemini/skills/orchestration-patterns of bybren-llc/safe-agentic-workflow.

  • SKILL.md
  • README.md

Open the folder on GitHubat commit 26ca58b

Compare with similar skills

Orchestration Patterns next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Orchestration Patterns compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Orchestration Patterns this skillbybren-llc/safe-agentic-workflow423—~2kAutomated safety check: PassMIT
Zeroshotthe-open-engine/zeroshot1.9k—~2kAutomated safety check: PassMIT
OMG Mode Cancellerzereight/gitlab-mcp2k1 repos~690Automated safety check: PassMIT
agtx One-Shot Project Runnerfynnfluegge/agtx1.7k—~3.8kAutomated safety check: PassApache-2.0
Self-Improve Evolutionary LoopYeachan-Heo/oh-my-claudecode40k—~5.3kAutomated safety check: WarnMIT
AutopilotYeachan-Heo/oh-my-claudecode40k—~4.4kAutomated safety check: PassMIT

Similar skills

  • Zeroshot

    the-open-engine/zeroshot

    Use Zeroshot to prepare, run, observe, or troubleshoot explicit multi-agent software work locally or on Zeroshot Cloud.

    1.9k GitHub stars~2k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • OMG Mode Canceller

    zereight/gitlab-mcp

    Detects which autonomous OMG mode is currently active - Autopilot, Ralph, Ultrawork, UltraQA, Team or Self-Improve - and shuts it down cleanly.

    2k GitHub starsUsed in 1 repo~690 tokens
    Agent WorkflowsAuto-check passed
  • Runs a whole project unattended on an agtx kanban board, decomposing the goal, starting tasks, unblocking workers and merging each result.

    1.7k GitHub stars~3.8k tokensUpdated 7 days ago
    Agent WorkflowsAuto-check passed
  • Self-Improve Evolutionary Loop

    Yeachan-Heo/oh-my-claudecode

    Runs an autonomous improvement loop on a repository: agents propose and execute plans, a tournament picks the winner by benchmark, and each round is recorded and plotted.

    40k GitHub stars~5.3k tokensUpdated yesterday
    Agent WorkflowsAuto-check: warnings
  • Autopilot

    Yeachan-Heo/oh-my-claudecode

    Takes a short product idea through requirements, design, planning, parallel implementation, QA cycles and multi-reviewer validation to produce working code.

    40k GitHub stars~4.4k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Harness Engineering

    10xChengTu/harness-engineering

    Set up and improve harness engineering (AGENTS.md, docs/, lint rules, eval systems, project-level prompt engineering) for AI-agent-friendly codebases.

    102 GitHub starsUsed in 1 repo~1k tokens
    Agent WorkflowsAuto-check passed

More from bybren-llc/safe-agentic-workflow

All 42 skills in this repo
  • Multi-Agent Coordination Template

    bybren-llc/safe-agentic-workflow

    Agent assignment matrix, blocker escalation, and TDM coordination patterns. Use when assigning work to specialist agents, managing blockers across agents…

    423 GitHub stars~1.2k tokensUpdated 2 mo ago
    Auto-check passed
  • API Route Patterns

    bybren-llc/safe-agentic-workflow

    API route implementation patterns with RLS, validation, and error handling. Use when creating API routes, implementing CRUD endpoints, adding server-side…

    423 GitHub stars~1.6k tokensUpdated 2 mo ago
    Auto-check passed
  • Technical Documentation Templates

    bybren-llc/safe-agentic-workflow

    Documentation templates for ADRs, runbooks, architecture docs, and knowledge transfer documents. Use when creating Architecture Decision Records, writing…

    423 GitHub stars~1.2k tokensUpdated 2 mo ago
    Auto-check passed
  • Deployment SOP Checklist

    bybren-llc/safe-agentic-workflow

    Deployment workflows, pre-deploy validation, smoke testing, and rollback procedures. Use when deploying to staging or production, running smoke tests…

    423 GitHub stars~950 tokensUpdated 2 mo ago
    Auto-check passed
  • Frontend Patterns Template

    bybren-llc/safe-agentic-workflow

    Frontend patterns for modern web frameworks, component libraries, auth flows, and analytics. Use when building UI components, creating pages, implementing…

    423 GitHub stars~2k tokensUpdated 2 mo ago
    Auto-check passed
  • Advanced Git Operations

    bybren-llc/safe-agentic-workflow

    Advanced git operations including rebase, bisect, cherry-pick, and conflict resolution. Use when rebasing feature branches, debugging with bisect…

    423 GitHub stars~1.6k tokensUpdated 2 mo ago
    Auto-check passed

Categories

Questions about Orchestration Patterns

What does Orchestration Patterns do?

Agentic orchestration patterns for long-running tasks. An agent skill from bybren-llc/safe-agentic-workflow. Orchestration Patterns is an agent skill from bybren-llc/safe-agentic-workflow. Agentic orchestration patterns for long-running tasks.

When should I use Orchestration Patterns?

Orchestration Patterns fits situations like: managing multi-step work; coordinating workflows; orchestrating PR workflows.

How do I install Orchestration Patterns in Claude Code?

Run `npx skills add bybren-llc/safe-agentic-workflow --skill orchestration-patterns -a claude-code`. Or copy the skill folder (.gemini/skills/orchestration-patterns in bybren-llc/safe-agentic-workflow) into .claude/skills/orchestration-patterns in your project. Claude Code loads it when a task matches its description.

How do I install Orchestration Patterns in Codex?

Run `npx skills add bybren-llc/safe-agentic-workflow --skill orchestration-patterns -a codex`. Or copy the skill folder (.gemini/skills/orchestration-patterns in bybren-llc/safe-agentic-workflow) into .agents/skills/orchestration-patterns in your project. Codex loads it when a task matches its description.

Can I use Orchestration Patterns in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add bybren-llc/safe-agentic-workflow --skill orchestration-patterns -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/orchestration-patterns, .gemini/skills/orchestration-patterns, .github/skills/orchestration-patterns and .opencode/skills/orchestration-patterns in your project.

What does Orchestration Patterns need to run?

Going by SKILL.md and its folder, Orchestration Patterns needs the command-line tools its instructions call (yarn).

Does Orchestration Patterns access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Orchestration Patterns safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Orchestration Patterns use?

Orchestration Patterns is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Orchestration Patterns use?

About 2k tokens (SKILL.md is roughly 7.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Orchestration Patterns?

Skills that share tags, products or a category with Orchestration Patterns: Zeroshot (the-open-engine/zeroshot, 1.9k stars), OMG Mode Canceller (zereight/gitlab-mcp, 2k stars), agtx One-Shot Project Runner (fynnfluegge/agtx, 1.7k stars) and Self-Improve Evolutionary Loop (Yeachan-Heo/oh-my-claudecode, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Orchestration Patterns?

bybren-llc (a GitHub organization) maintains it in bybren-llc/safe-agentic-workflow, which has 423 GitHub stars. The repository holds 42 skills in this directory. The repository was last updated on July 20, 2026.

Source: bybren-llc/safe-agentic-workflow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.