Menú
Decision guide for selecting the right orchestration pattern for a process
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Use when creating a local agent for a pas-clief workspace. Walks the user through naming the agent, defining its role, listing its skills, and writing CLAUDE.md and CONTEXT.md from templates. The agent lands in `library/agents/<name>/`.
Use when drafting and publishing a newsletter issue. Walks research → draft → publish phases, using the writer agent. Example library process for pas-clief — copy or extend it for your own use.
Use when applying a workspace's drafting conventions to written output — voice, format, sentence rhythm, the things that make output feel like it belongs to this project. Reads the workspace's style notes if any and adjusts the draft accordingly.
Use when line-editing a draft for clarity and economy. Tightens sentences, removes filler, rewrites awkward constructions, ensures every sentence earns its keep. Apply this skill on the final pass before output.
Use when an agent needs to gather sources or background information from the web for a topic. Produces a concise sources file with URLs, summaries, and the most relevant excerpts.
Use when checking that a pas-clief workspace is current with the latest plugin conventions, or when migrating from an older version. Walks a checklist of structural and template changes and offers to apply each.
| name | orchestration-patterns |
| description | Decision guide for selecting the right orchestration pattern for a process |
Every process declares an orchestration: field in its process.md. This guide helps you choose the right pattern.
cycle-9, 2026-03-08-code-review). The slug is provided by the user or derived from the directive when the orchestrator creates the workspace.| Pattern | File | Orchestrator Role | Best For |
|---|---|---|---|
| hub-and-spoke | hub-and-spoke.md | Central orchestrator, all agents communicate through hub | Multi-agent pipelines with clear phases |
| discussion | discussion.md | Moderator, facilitates multi-agent discussion | Brainstorming, design review, multi-perspective analysis |
| solo | solo.md | Operator, single agent handles everything | Simple processes, single-skill tasks |
| sequential-agents | sequential-agents.md | Coordinator, explicit handoff between agents | Strict ordering, resource constraints, assembly-line work |
Start here:
How many agents does the process need?
Do agents need to discuss or debate?
Can phases run in parallel?
Still unsure?
All patterns share a common lifecycle protocol defined in lifecycle.md:
Read lifecycle.md first, then the pattern-specific file for execution rules.
hub-and-spoke.md — Spawn order, parallelism inference, error chain, gate protocol, intra-phase parallel dispatchdiscussion.md — Moderator behavior, turn-taking, synthesis rulessolo.md — Single-agent operation, when to upgrade to multi-agentsequential-agents.md — Handoff protocol, agent lifecycle (eager shutdown)A process can override pattern defaults in its process.md:
sequential: true forces linear execution even in hub-and-spokemodes/supervised.md, modes/autonomous.md) control gate behavior