orchestrate
Squad Orchestrate Skill
The chained wrapper. Plan, checkpoint, implement.
Flags (parsed from $ARGUMENTS)
--yes— skip the checkpoint.--dry-run— stop after/squad:decompose.--auto-resolve— forwarded to/squad:spawn.--keep-worktrees— forwarded to/squad:spawn.
Everything else in $ARGUMENTS is the goal.
Workflow
- Plan: invoke
/squad:decompose <goal>. It writes the manifest to.claude/squad/runs/<run-id>/manifest.jsonand prints a summary table. Read back therun_id. - Stop if
--dry-run. Print the run id and the manifest path. - Checkpoint. Unless
--yes: print the summary table and askproceed? [y / edit / abort].y— continue with the manifest on disk as written.edit— the user opens.claude/squad/runs/<run-id>/manifest.jsonthemselves (in their editor; orchestrate does not shell out to$EDITOR— it only reads and writes files). Tell them the path and wait for them to confirm they've saved. When they signal ready, reread the file from disk and re-run these checks:- JSON parses.
run_idis unchanged (if the user renamed it, refuse — the run dir on disk is already keyed to the original id).- Task ids are unique.
dependencieshas no cycles (Kahn sort).- Every task has a non-empty
validation_command. - No two parallelizable tasks share a writable
target_filespath. If any check fails, show the specific error and offereditagain orabort. Only continue once validation passes.
abort— stop. No worktrees exist yet, so nothing to clean up. The manifest on disk is the single source of truth for step 4. Orchestrate does not hold an in-memory copy to diff against.
- Implement: invoke
/squad:spawn run:<run-id>, forwarding--auto-resolveand--keep-worktreesif set. - Final message is spawn's own:
Integration branch ready: squad/<run-id>/integration. Run /ship:commit to ship.
Guardrails
- Never skip
/squad:decompose— spawn requires a valid manifest. --yesbypasses the checkpoint, not the inner skills' guardrails. A malformed manifest still aborts/squad:spawn.- Never invoke
/ship:commitautomatically. The user ships explicitly. - Never retry a failed phase automatically more than once.
Task
Handle this request: $ARGUMENTS
More from skrrt-sh/skills
commit
Creates focused conventional commits with mandatory gitmojis. Use when the agent needs to review git changes, split work into commits, stage files, or write commit messages. Always use this skill when the user asks to commit, make a commit, write a commit message, split changes into commits, stage and commit files, or anything involving git commit workflows. Trigger for phrases like "commit this", "write a commit", "split into commits", "conventional commit", "gitmoji commit", "stage and commit", "commit the changes", or "help me commit".
13pr
Creates or updates GitHub pull requests and GitLab merge requests with the matching CLI. Use when the agent needs to push a branch, open a review request, or write PR or MR text. Always use this skill when the user asks to open a PR, create a pull request, push and open a PR, create a merge request, update PR text, write a PR description, or anything involving pull requests or merge requests. Trigger for phrases like "open a PR", "create a pull request", "push and open a PR", "merge request", "MR on gitlab", "update the PR", or "write PR description".
12md-writer
Write well-structured markdown documents with YAML frontmatter, Mermaid diagrams, and markdownlint compliance. Use when creating or editing .md files, writing documentation, guides, specs, or any markdown content.
12release
Drafts and publishes GitHub or GitLab releases with curated release notes. Use when the agent needs to prepare release text, compare tags, summarize release changes, or create a release. Always use this skill when the user asks to create a release, draft release notes, publish a release, summarize changes for a version, update a changelog for a release, or anything involving GitHub or GitLab releases. Trigger for phrases like "release notes", "draft a release", "publish release", "create a release", "v1.x.x release", "what changed since last tag", or "prepare release text".
11setup
Adds skrrt skills instructions to the current project's CLAUDE.md or AGENTS.md so that commits, PRs, and releases use the ship plugin skills. Use this skill whenever the user wants to set up, configure, install, or wire skrrt skills into a project, add ship plugin instructions to agent config files, or ensure the team uses /commit /pr /release instead of raw git commands. Trigger even when the user says "set up this repo", "add skills to CLAUDE.md", or "configure the ship plugin".
10spawn
Run N subagents in parallel for one big task. Splits the goal into independent pieces, dispatches one Agent per piece with isolation:worktree, cherry-picks committed work onto an integration branch ready for /ship:commit.
3