Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Conducts one spec's tasks by delegation — spawns a dedicated bounded worker session per task, dispatches the briefing, and uses the task file on disk for completion state and checks its verification…
$ npx skills add compozy/compozy --skill cy-orchestrate-tasks -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install compozy/compozy cy-orchestrate-tasks --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/compozy/compozy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/extensions/spec-cycle/skills/cy-orchestrate-tasks .claude/skills/cy-orchestrate-tasks && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "cy-orchestrate-tasks" agent skill from https://github.com/compozy/compozy/tree/main/extensions/spec-cycle/skills/cy-orchestrate-tasks into .claude/skills/cy-orchestrate-tasks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cy-orchestrate-tasks", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/compozy/compozy/tree/main/extensions/spec-cycle/skills/cy-orchestrate-tasksType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add compozy/compozy --skill cy-orchestrate-tasks -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install compozy/compozy cy-orchestrate-tasks --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/compozy/compozy.git skills-src && mkdir -p .agents/skills && cp -r skills-src/extensions/spec-cycle/skills/cy-orchestrate-tasks .agents/skills/cy-orchestrate-tasks && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cy-orchestrate-tasks" agent skill from https://github.com/compozy/compozy/tree/main/extensions/spec-cycle/skills/cy-orchestrate-tasks into .agents/skills/cy-orchestrate-tasks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cy-orchestrate-tasks", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add compozy/compozy --skill cy-orchestrate-tasks -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install compozy/compozy cy-orchestrate-tasks --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/compozy/compozy.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/extensions/spec-cycle/skills/cy-orchestrate-tasks .cursor/skills/cy-orchestrate-tasks && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "cy-orchestrate-tasks" agent skill from https://github.com/compozy/compozy/tree/main/extensions/spec-cycle/skills/cy-orchestrate-tasks into .cursor/skills/cy-orchestrate-tasks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cy-orchestrate-tasks", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/compozy/compozy.git --path extensions/spec-cycle/skills/cy-orchestrate-tasks--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add compozy/compozy --skill cy-orchestrate-tasks -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install compozy/compozy cy-orchestrate-tasks --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/compozy/compozy.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/extensions/spec-cycle/skills/cy-orchestrate-tasks .gemini/skills/cy-orchestrate-tasks && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "cy-orchestrate-tasks" agent skill from https://github.com/compozy/compozy/tree/main/extensions/spec-cycle/skills/cy-orchestrate-tasks into .gemini/skills/cy-orchestrate-tasks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cy-orchestrate-tasks", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install compozy/compozy cy-orchestrate-tasksInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add compozy/compozy --skill cy-orchestrate-tasks -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/compozy/compozy.git skills-src && mkdir -p .github/skills && cp -r skills-src/extensions/spec-cycle/skills/cy-orchestrate-tasks .github/skills/cy-orchestrate-tasks && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "cy-orchestrate-tasks" agent skill from https://github.com/compozy/compozy/tree/main/extensions/spec-cycle/skills/cy-orchestrate-tasks into .github/skills/cy-orchestrate-tasks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cy-orchestrate-tasks", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add compozy/compozy --skill cy-orchestrate-tasks -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install compozy/compozy cy-orchestrate-tasks --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/compozy/compozy.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/extensions/spec-cycle/skills/cy-orchestrate-tasks .opencode/skills/cy-orchestrate-tasks && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "cy-orchestrate-tasks" agent skill from https://github.com/compozy/compozy/tree/main/extensions/spec-cycle/skills/cy-orchestrate-tasks into .opencode/skills/cy-orchestrate-tasks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cy-orchestrate-tasks", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
cy-orchestrate-tasksConducts one spec's tasks by delegation — spawns a dedicated bounded worker session per task, dispatches the briefing, and uses the task file on disk for completion state and checks its verification…
Cy Orchestrate Tasks is an agent skill from compozy/compozy. Conducts one spec's tasks by delegation — spawns a dedicated bounded worker session per task, dispatches the briefing, and uses the task file on disk for completion state and checks its verification evidence. Use when a prompt names a spec slug under .compozy/tasks/ and asks for its tasks to be orchestrated across worker sessions. Do not use for implementing a task directly, for review remediation, or for QA and pull-request work.
Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Pull requests. The repository describes itself as: An operating system for AI agents. Plug in the agent CLIs you already use (Claude Code, Codex, Gemini CLI, Cursor) and they become a team: they split the work, hand tasks to each… The licence is MIT.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit eec2ed1. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Cy Orchestrate Tasks loads about 2.3k tokens when it runs. Until then it costs about 114 tokens; SKILL.md has 1,109 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from compozy/compozy at commit eec2ed1, republished under its MIT licence (© compozy). 1,109 words, ~2,278 tokens.
.claude/skills/cy-orchestrate-tasks/SKILL.md (or your agent's skills folder).This session is the conductor of the spec: it conducts, it does not play. Every task under
.compozy/tasks/<slug>/ is implemented by a dedicated CompozyOS worker session.
slug — the directory name under .compozy/tasks/<slug>/, holding _tasks.md (the task graph)
and task_NN.md files whose frontmatter carries status, title, and type.implementer — the exact validated Agent identifier supplied in the Goal objective. The Loop
defaults it to code_implementer; the conductor never substitutes that default.backend_runtime, frontend_runtime, and default_runtime — optional runtime objects supplied
in the Goal objective. Each can carry provider, model, reasoning, and speed.Read .compozy/tasks/<slug>/_tasks.md and derive the execution order from graph.edges. Read the
frontmatter of every task_NN.md. Queue only tasks whose status is pending or in_progress,
in graph order. Treat completed, complete, done, and finished as already completed, ignoring
case and surrounding whitespace. Stop on unknown or missing statuses before spawning workers;
report the task file and invalid value instead of guessing.
Done when: the queue lists the id, title, and status of every queued task, in execution order.
Choose the worker runtime by exact frontmatter type: backend uses backend_runtime, frontend
uses frontend_runtime, and every other value uses default_runtime. Merge the task's own
frontmatter runtime over that category object field by field before building spawn flags. Create
one bounded spawned session bound to this conductor. Bind the exact implementer value from the
Goal once, then pass it as one quoted argument. TTL and parent-stop are the containment contract;
--ttl-seconds is mandatory.
The child starts with no delegated tools when permission atoms are omitted. Before spawning, inspect this conductor's session lineage permission policy and the worker's required operations. Pass an explicit subset of the parent's concrete tool IDs: the bootstrap set below supports native discovery, descriptor reads, skill lookup, and retained-reference reads. Add only task-required tools the parent can delegate. If a required tool is absent from the parent budget, block with that missing ID; do not retry without permissions, grant wildcards, or bypass a denial through files/CLI. Other permission categories remain empty unless the task needs an explicit parent-authorized subset.
For native compozy__session_spawn, put these same IDs in tools; use the live descriptor for
any additional fields. The equivalent CLI recipe is:
IMPLEMENTER="<exact implementer identifier from the Goal>"
compozy spawn --agent "$IMPLEMENTER" \
--name "orchestrate-<slug>-<task_id>" \
--role worker \
--tool compozy__tool_search \
--tool compozy__tool_info \
--tool compozy__tool_artifact_read \
--tool compozy__skill_search \
--tool compozy__skill_view \
--ttl-seconds 3600 \
--auto-stop-on-parent=true \
--idempotency-key "orchestrate-<slug>-<task_id>" \
-o jsonAppend --provider, --model, --reasoning-effort, and --speed only for non-empty fields in the
selected runtime object; reasoning maps to --reasoning-effort. When every field is empty, omit
provider, model, and reasoning flags so the child resolves them through the selected Agent and
workspace. Under current spawn behavior, omitted speed inherits the parent session. Capture
.session.id.
When the spawn response is lost or ambiguous, reconcile before acting — a blind respawn creates a second worker for one task:
compozy session list \
--parent "$COMPOZY_SESSION_ID" \
--type spawned \
--state active \
--query "orchestrate-<slug>-<task_id>" \
-o jsonReuse the id only when exactly one returned session has name equal to
orchestrate-<slug>-<task_id> and agent_name equal to $IMPLEMENTER. Zero results after a
confirmed spawn failure blocks the task. A mismatched agent_name is never adopted or followed by
a blind respawn: stop the session only when its parent and exact name prove conductor ownership,
then block the task. More than one exact match: stop every conductor-owned match and block the task.
Done when: exactly one worker session id is held for this task, or the task is marked blocked.
Send the briefing and wait in the same command. compozy session prompt blocks until the worker's
turn ends in every output mode; -o jsonl is the form that also leaves a durable per-task event log
as evidence:
mkdir -p .compozy/tasks/<slug>/logs
compozy session prompt <session_id> "<briefing>" \
-o jsonl > .compozy/tasks/<slug>/logs/<task_id>.jsonl 2>&1--queue, --interrupt, and --steer return at admission instead of at turn end, so they cannot
carry a briefing this workflow waits on.
Done when: the command has returned and its outcome is recorded, including a failed prompt.
Re-read the task file frontmatter. Workers write status: completed; the importer also accepts
complete, done, and finished (ignoring case and surrounding whitespace). The
worker's closing message alone never completes a task. Check the referenced verification evidence
against the task contract and current inputs; a status label is not proof that checks passed.
Reuse valid worker evidence instead of rerunning the same suite.
If the status is not a recognized completion state, send one corrective prompt in the same session, using the same
blocking form, naming exactly what is missing. A second failure produces a blocked result citing
.compozy/tasks/<slug>/logs/<task_id>.jsonl as evidence.
Done when: the task has a recognized completion state on disk and verified evidence, or the Goal result is blocked with the log path cited. Do not write Goal result statuses into task files.
Run compozy session stop <session_id> -o json before advancing to the next task and before
reporting any result — after success, after a prompt failure, after the corrective attempt, and
after a block. A failed stop is itself a blocked result and must be recorded with its error. TTL
and parent-stop contain abrupt cancellations; they do not replace this stop.
Done when: the worker session is no longer active and the stop outcome is recorded.
Answer with the structured result the loop asks for: status, optional summary (1–3 sentences),
and optional tasks — each task entry names the worker session that executed it. Use complete
or blocked; task-file frontmatter continues to use completed.
Done when: every task in the queue appears in the report with its task id and session id.
Fill the fields and send this as the prompt body:
Implement exactly task
<task_id>—<title>— of the spec.compozy/tasks/<slug>/.Execution guidance:
cy-workflow-memory: use for continuity across workers or interruptions. Memory directory.compozy/tasks/<slug>/memory, shared memory.compozy/tasks/<slug>/memory/MEMORY.md, task memory.compozy/tasks/<slug>/memory/<task_id>.md.cy-execute-task: the end-to-end execution workflow for this task.cy-final-verify: assess task-scope evidence within the existing validation step; run only missing or invalidated checks. Name remaining workflow-owned integration/QA obligations without starting another verification cycle for the same evidence.Read the repository
AGENTS.md/CLAUDE.mdand surface-specific instructions, then the task file,_tasks.mddependencies, and relevant_spec.mdsections; reuse grounding already supplied in the briefing. These contracts remain the source of truth. Keep scope tight to this task and record follow-up work instead of widening it. Preserve unrelated worktree changes. Satisfy the Validation, Test Plan, or Testing items the task body requires; reuse evidence only when the same inputs and project policy allow it. Fix failures. With verification clean, set the task file frontmatter tostatus: completed. Leave the changes uncommitted — commit and pull request belong to other surfaces.
© compozy, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in extensions/spec-cycle/skills/cy-orchestrate-tasks of compozy/compozy.
Open the folder on GitHubat commit eec2ed1
Cy Orchestrate Tasks next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Cy Orchestrate Tasks this skillcompozy/compozy | 2.8k | — | ~2.3k | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Check PRonyx-dot-app/onyx | 32k | 2 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Understand Diff AnalysisEgonex-AI/Understand-Anything | 86k | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| PR Design DocOpenHands/OpenHands | 90k | — | ~2.4k | Automated safety check: Pass | MIT |
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
onyx-dot-app/onyx
Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.
Egonex-AI/Understand-Anything
Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.
OpenHands/OpenHands
For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…
woocommerce/woocommerce
Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.
compozy/compozy
Dogfoods Compozy through an autonomous startup scenario with live providers, cross-surface observation, and strict evidence audit.
compozy/compozy
Go test-shape discipline for Compozy. An agent skill from compozy/compozy.
compozy/compozy
Guide for assistant-ui library - AI chat UI components. An agent skill from compozy/compozy.
compozy/compozy
Guide for assistant-ui UI primitives - ThreadPrimitive, ComposerPrimitive, MessagePrimitive.
compozy/compozy
Guide for assistant-ui runtime system and state management. An agent skill from compozy/compozy.
compozy/compozy
Guide for assistant-stream package and streaming protocols. An agent skill from compozy/compozy.
Categories
Conducts one spec's tasks by delegation — spawns a dedicated bounded worker session per task, dispatches the briefing, and uses the task file on disk for completion state and checks its verification…. Cy Orchestrate Tasks is an agent skill from compozy/compozy. Conducts one spec's tasks by delegation — spawns a dedicated bounded worker session per task, dispatches the briefing, and uses the task file on disk for completion state and checks its verification evidence.
Cy Orchestrate Tasks fits situations like: A prompt names a spec slug under .compozy/tasks/ and asks for its tasks to be orchestrated across worker sessions; implementing a task directly; for review remediation; for QA and pull-request work.
Run `npx skills add compozy/compozy --skill cy-orchestrate-tasks -a claude-code`. Or copy the skill folder (extensions/spec-cycle/skills/cy-orchestrate-tasks in compozy/compozy) into .claude/skills/cy-orchestrate-tasks in your project. Claude Code loads it when a task matches its description.
Run `npx skills add compozy/compozy --skill cy-orchestrate-tasks -a codex`. Or copy the skill folder (extensions/spec-cycle/skills/cy-orchestrate-tasks in compozy/compozy) into .agents/skills/cy-orchestrate-tasks in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add compozy/compozy --skill cy-orchestrate-tasks -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cy-orchestrate-tasks, .gemini/skills/cy-orchestrate-tasks, .github/skills/cy-orchestrate-tasks and .opencode/skills/cy-orchestrate-tasks in your project.
SKILL.md names no scripts, command-line tools or credentials: Cy Orchestrate Tasks is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Cy Orchestrate Tasks is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.3k tokens (SKILL.md is roughly 9.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Cy Orchestrate Tasks: Finishing a Development Branch (obra/superpowers, 296k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and Understand Diff Analysis (Egonex-AI/Understand-Anything, 86k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
compozy (a GitHub organization) maintains it in compozy/compozy, which has 2,792 GitHub stars. The repository holds 47 skills in this directory. The repository was last updated on October 8, 2026.
Source: compozy/compozy on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.