backend-orchestrator
Installation
SKILL.md
Backend Orchestrator
Pick the right skill for a backend request, or chain several skills into a gated pipeline. The orchestrator itself writes no code or files. The routed skills do the work, own their memory updates, and run their own checkpoints.
Before You Start
- Resolve the shared docs folder (""): first
_shared/inside this skill's folder (bundled installs), then../_shared/next to it; other fallbacks are in<shared>/context-loading.md-> Resolving_shared/Files. A missing shared doc is a warning, not a stop. - Read
<shared>/tool-rules.md(mode=auto contract, Always Ask First, checkpoints) and<shared>/host-tools.mdif the actions below do not map cleanly to your host's tools. - Check project state per
<shared>/context-loading.md: is there a backend project, and does.opencode/everything-backend-memory/exist and look fresh? Missing or stale memory on an existing project means the pipeline starts withbackend-scan. No project at all means Greenfield. - If the detected stack matches a file in
<shared>/stacks/, note it; the routed skills read it.
Skills and What They Own
Each skill has exactly one owner role. Route by the owner, not by keyword overlap.