Agent skill

Cy Orchestrate Tasks

by compozy in 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…

MITAuto-check passedDevelopment

Install Cy Orchestrate Tasks

skills CLI
$ npx skills add compozy/compozy --skill cy-orchestrate-tasks -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install compozy/compozy cy-orchestrate-tasks --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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-src

Use ~/.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/

Facts

Skill name
cy-orchestrate-tasks
GitHub stars
2.8k
Token cost
~2.3k tokens
SKILL.md length
1,109 words
Files
1
Skills in repo
47
Repo updated
First seen
Licence
MIT

At a glance

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…

  • Works in 6 steps: Load the task graph → Spawn the worker session → Dispatch the briefing and wait → …
  • A prompt names a spec slug under .compozy/tasks/ and asks for its tasks to be orchestrated across worker sessions
  • SKILL.md covers Required Inputs, Workflow, Worker briefing and Rules
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

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.

When your agent uses it

  • 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

Example prompts

  • “Use the cy-orchestrate-tasks skill to conduct one spec's tasks by delegation — spawns a dedicated bounded worker session per task, dispatches the…”
  • “/cy-orchestrate-tasks”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Load the task graph
  2. Spawn the worker session
  3. Dispatch the briefing and wait
  4. Check the proof
  5. Stop the worker session
  6. Report

What it can do on your machine

Read from SKILL.md and the folder at commit eec2ed1. It shows what the files ask for, not the result of running them.

  • Tool permissions

    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.

  • Runs code

    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.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

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.

Always · name and description, kept in context so the agent knows when to use it
~114
When it runs · the whole SKILL.md, loaded when a task matches
~2.3k

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.

Safety

Auto-check passed

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.

SKILL.md

The full file from compozy/compozy at commit eec2ed1, republished under its MIT licence (© compozy). 1,109 words, ~2,278 tokens.

Download SKILL.mdSave it as .claude/skills/cy-orchestrate-tasks/SKILL.md (or your agent's skills folder).
name
cy-orchestrate-tasks
description
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.

Orchestrate Spec Tasks

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.

Required Inputs

  • 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.

Workflow

1. Load the task graph

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.

2. Spawn the worker session

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:

bash
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 json

Append --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:

bash
compozy session list \
  --parent "$COMPOZY_SESSION_ID" \
  --type spawned \
  --state active \
  --query "orchestrate-<slug>-<task_id>" \
  -o json

Reuse 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.

3. Dispatch the briefing and wait

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:

bash
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.

Show full SKILL.md (490 more words)Show less
4. Check the proof

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.

5. Stop the worker session

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.

6. Report

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.

Worker briefing

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.md and surface-specific instructions, then the task file, _tasks.md dependencies, and relevant _spec.md sections; 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 to status: completed. Leave the changes uncommitted — commit and pull request belong to other surfaces.

Rules

  • The conductor conducts: in this session the work is spawn, dispatch, wait, check, stop. Code edits belong to workers.
  • One task at a time, in graph order, with one worker session per task — reused only for that task's corrective prompt.

© compozy, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in extensions/spec-cycle/skills/cy-orchestrate-tasks of compozy/compozy.

Open the folder on GitHubat commit eec2ed1

Compare with similar skills

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.

Cy Orchestrate Tasks compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cy Orchestrate Tasks this skillcompozy/compozy2.8k—~2.3kAutomated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Understand Diff AnalysisEgonex-AI/Understand-Anything86k1 repos~1.4kAutomated safety check: PassMIT
PR Design DocOpenHands/OpenHands90k—~2.4kAutomated safety check: PassMIT

Similar skills

  • 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.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Check PR

    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.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed
  • Understand Diff Analysis

    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.

    86k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed
  • PR Design Doc

    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…

    90k GitHub stars~2.4k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • WooCommerce Code Review

    woocommerce/woocommerce

    Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.

    11k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed

More from compozy/compozy

All 47 skills in this repo
  • Eng Real Scenario QA

    compozy/compozy

    Dogfoods Compozy through an autonomous startup scenario with live providers, cross-surface observation, and strict evidence audit.

    2.8k GitHub stars~3.4k tokensUpdated today
    Auto-check passed
  • Eng Test Conventions

    compozy/compozy

    Go test-shape discipline for Compozy. An agent skill from compozy/compozy.

    2.8k GitHub stars~467 tokensUpdated today
    Auto-check passed
  • Assistant UI

    compozy/compozy

    Guide for assistant-ui library - AI chat UI components. An agent skill from compozy/compozy.

    2.8k GitHub stars~958 tokensUpdated today
    Auto-check passed
  • Guide for assistant-ui UI primitives - ThreadPrimitive, ComposerPrimitive, MessagePrimitive.

    2.8k GitHub stars~999 tokensUpdated today
    Auto-check passed
  • Assistant UI Runtime

    compozy/compozy

    Guide for assistant-ui runtime system and state management. An agent skill from compozy/compozy.

    2.8k GitHub stars~856 tokensUpdated today
    Auto-check passed
  • Assistant UI Streaming

    compozy/compozy

    Guide for assistant-stream package and streaming protocols. An agent skill from compozy/compozy.

    2.8k GitHub stars~813 tokensUpdated today
    Auto-check passed

Categories

Questions about Cy Orchestrate Tasks

What does Cy Orchestrate Tasks do?

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.

When should I use Cy Orchestrate Tasks?

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.

How do I install Cy Orchestrate Tasks in Claude Code?

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.

How do I install Cy Orchestrate Tasks in Codex?

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.

Can I use Cy Orchestrate Tasks in Cursor, Gemini CLI or GitHub Copilot?

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.

What does Cy Orchestrate Tasks need to run?

SKILL.md names no scripts, command-line tools or credentials: Cy Orchestrate Tasks is instructions for the agent only.

Does Cy Orchestrate Tasks access the network?

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.

Is Cy Orchestrate Tasks safe to install?

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.

What licence does Cy Orchestrate Tasks use?

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.

How many tokens does Cy Orchestrate Tasks use?

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.

What are the alternatives to Cy Orchestrate Tasks?

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.

Who maintains Cy Orchestrate Tasks?

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.