Skip to content

CONCEPT Cited by 1 source

Agent orchestration skill

Definition

A skill (in the Rovo-Dev / Claude-Code sense of an addressable bundle of agent-facing instructions) that encodes a multi-step workflow, not a single narrow tool binding. The skill tells the agent how to work on a particular codebase end-to-end — the golden-path loops, the sequencing of tools, the verification checkpoints.

Atlassian's Rovo Dev / Fireworks post is the canonical articulation:

"We've built a meta-workflow / orchestration skill for Fireworks development. It doesn't do one narrow technical thing, instead it gives the agent a set of 'golden path' loops for how to work on Fireworks changes end-to-end." (Source: sources/2026-04-24-atlassian-rovo-dev-driven-development)

Two kinds of skills

Narrow / tool-binding skill Orchestration / meta-workflow skill
One domain or one action End-to-end workflow across domains
E.g. "how to use our CLI", "how to write a Raft test", "how to make a PR" E.g. "how to work on Fireworks changes end-to-end"
Answers what does this tool do Answers which tools in which order for this change shape
Single invocation Multi-step loop with checkpoints

The Fireworks post names the first kind ("Skills for PRs, using CLI, specific domains like Raft, gRPC") as the conventional skill and introduces the orchestration variant as the higher- leverage form for sustained work on a codebase.

Why orchestration skills matter

A coding agent's context budget is finite. For a complex codebase with many tools, many conventions, and a non-obvious golden-path sequence, the agent either:

  • Re-discovers the sequence every task — expensive, error- prone, and dependent on the agent's ability to piece together scattered README files.
  • Loads a pre-compiled orchestration skill — the sequence, conventions, and common traps are encoded once, loaded as context when the agent needs them, and maintained as the codebase evolves.

This is the procedural-knowledge analogue of a README — but structured for agent consumption rather than human onboarding. The Fireworks team reports the form factor works: "we've built lots of skills" and specifically "a skill that automates deploying, operating, and tearing down isolated Fireworks dev shards on the shared AWS scms Kubernetes cluster" — a second orchestration skill, for the dev-shard management sub-workflow.

What goes in an orchestration skill

Inferable from the Fireworks description:

  • Entry points — the workflows this skill covers ("raise a PR", "fix a failing test", "deploy to a dev shard").
  • Tool sequences — which tools to invoke in which order for each entry point.
  • Verification checkpoints — when to pause and check (run tests, check CI, read pipeline output).
  • Common traps / exclusions — things the agent should not do on this codebase ("don't skip the Helm validation step", "don't merge without running e2e").
  • Escape hatches — when to hand back to the human.

This is the same shape as a human team runbook, re-targeted at an LLM agent consumer.

Not the same as

  • A system prompt. The system prompt is always on. Skills are addressable — the agent loads them on demand. Maintaining a skill does not inflate every conversation.
  • A tool schema. A tool schema describes how to call a tool. An orchestration skill describes which tools to call in which order for a workflow.
  • A spec. A spec describes what the system does. A skill describes how the agent works on the system.

Seen in

Last updated · 510 distilled / 1,221 read