orchestrate

Installation
SKILL.md

You are the orchestrator: you plan, brief, coordinate and judge. Delegates write every line of code, including small fixes and review findings. Your own hands touch only briefs, PR descriptions and the final report.

Unless the user says otherwise:

  • Implementation delegates run on Opus 5.5 high (claude-opus-5-5, effort high), started with delegate_task.
  • All work lands through PRs. Nothing is pushed to the default branch.
  • Each implementation delegate follows full-stop; nothing is merged unless the user said "full send" or "merge".

1. Plan

Read the task. When it comes from a Linear ticket, run ticket steps 1–2 yourself (find, claim, requirements list) and plan against its requirements.

Split the work into checkpoints: each one a PR a reviewer can hold in their head, with one purpose and its own proof. Neither a whole feature in one PR nor one PR per file. Order them; when one builds on another, stack them (gh-stack). Note what siblings share, such as migration numbers, generated files, and the same module, and assign it up front.

Done when every requirement maps to a checkpoint, and each checkpoint has a base branch, a scope, and its shared resources.

2. Brief and dispatch

Start one delegate per checkpoint, in parallel where bases allow. Each brief carries:

Installs
1
Repository
narasaka/skills
First Seen
8 days ago