cy-orchestrate-tasks

Orchestrates spec tasks by spawning bounded worker sessions and verifying on-disk completion.

2.7k|171|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/compozy/compozy --skill cy-orchestrate-tasks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cy-orchestrate-tasks
Source: https://github.com/compozy/compozy/tree/main/extensions/spec-cycle/skills/cy-orchestrate-tasks
Command: npx skills add https://github.com/compozy/compozy --skill cy-orchestrate-tasks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating multi-task implementation work across AI agent sessions is error-prone: tasks get skipped, workers are duplicated after lost responses, and completion claims are accepted without proof. This Skill turns a spec's task graph into a disciplined delegation loop where every task runs in its own bounded worker session and only the task file's on-disk status counts as done.

Core Features & Use Cases

  • Graph-ordered task queue: Reads .compozy/tasks/<slug>/_tasks.md and each task_NN.md frontmatter to queue pending or in-progress tasks in dependency order.
  • Bounded worker spawning: Creates one TTL-limited, parent-bound CompozyOS session per task with idempotency keys, runtime selection by task type, and reconciliation logic that prevents duplicate workers after ambiguous spawn responses.
  • Proof-based completion: Dispatches a structured briefing, waits on the blocking prompt, and accepts only status: completed in the task file frontmatter, with one corrective prompt before marking the task blocked.
  • Use Case: Given a spec slug with eight pending tasks, run this Skill to sequentially spawn eight worker sessions, collect per-task JSONL event logs, and produce a structured report mapping each task id to its worker session id.

Quick Start

Orchestrate the tasks for the spec slug 'auth-refactor' under .compozy/tasks/ using the code_implementer agent across worker sessions.

Frequently Asked Questions about cy-orchestrate-tasks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate spec tasks across multiple agent sessions?

Provide the spec slug under .compozy/tasks/ and the implementer agent identifier. The conductor reads _tasks.md for graph order, spawns one bounded worker session per pending task, dispatches a briefing, and verifies completion from the task file frontmatter.

How does the conductor prevent duplicate worker sessions?

Each spawn uses an idempotency key named orchestrate-<slug>-<task_id>. If the spawn response is lost, the conductor lists active spawned sessions by parent and name, reusing the id only when exactly one session matches both the name and the implementer agent.

What counts as proof that a task is completed?

Only status: completed in the task file's frontmatter on disk is accepted. The worker's closing message never completes a task; if the status is anything else, the conductor sends one corrective prompt in the same session before marking the task blocked.

When should I not use task orchestration?

Do not use it to implement a task directly, perform review remediation, or handle QA and pull-request work. The conductor only spawns, dispatches, waits, checks, and stops; all code edits belong to the worker sessions.

How are worker runtimes selected per task?

The task frontmatter type picks the runtime object: backend uses backend_runtime, frontend uses frontend_runtime, and other types use default_runtime. The task's own runtime field merges over that object, and empty fields are omitted so the agent resolves them.