Shoal orchestration for agy - routing, Plan and approval gate, dispatch to named roles, fresh verification, recovery. Load before deciding delegation, review, or approval on large, ambiguous, architectural, risky, cross-surface, or plan-first work.
Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
Are you the author of Shoal Orchestration?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/miyago9267-shoal-orchestration-shoal)
---
name: shoal-orchestration
description: Shoal orchestration for agy - routing, Plan and approval gate, dispatch to named roles, fresh verification, recovery. Load before deciding delegation, review, or approval on large, ambiguous, architectural, risky, cross-surface, or plan-first work.
---
# Shoal orchestration (agy)
This skill is the detailed procedure behind the always-on shoal bootstrap.
The bootstrap stays authoritative for its invariants; this skill supplies the
complete contract.
## First move
1. Classify the interaction shape: `co_discover`, `explore_then_plan`, `fan_out`, or
`execute` (see the policy's routing section).
2. Set `execution_scope`, `review_intent`, and the discovery budget from the
policy extensions.
3. Apply risk triggers before size, then the phase gate and dispatch brake
before every invoke_subagent call.
An `executor` brief names its file/module bound; work larger than that is split into several executors or routed to `applier`.
## References
Read only the part needed for the current decision:
- [orchestration-policy.md](references/orchestration-policy.md): routing,
lifecycle gates, dispatch and ownership, severity, recovery, AUTO/ASK,
parallel and runtime mechanics.
- [workflow-extensions.md](references/workflow-extensions.md): outcome-level
continuation, turn-scoped review intent, discovery budget, decision
checkpoint through `ask_question`, task ledger and blocked-task
isolation, continuation across user input, review-service circuit breaker,
and verifier direction checkpoint.
If a reference is unavailable, keep the bootstrap invariants, work fail-soft,
and do not claim full shoal verification.
