cy-loop-tasks

Executes Compozy spec task graphs through a self-healing five-phase loop until SHIP.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Shipping a spec end to end requires coordinating task execution, QA cycles, peer review, and CI delivery across many iterations; this Skill automates that orchestration as a resumable state machine with one atomic checkpoint commit per task.

Core Features & Use Cases

  • Phase-driven execution: A detect-phase script derives the next action (bootstrap, task execution, QA report/execution, peer-review rounds, or delivery) from filesystem truth and state.yaml, so the loop resumes cleanly after any interruption.
  • Self-healing recovery: Failed commands, gates, or worker runs stay inside the current phase action for diagnosis and repair; only proven external blockers stop the loop.
  • Worker delegation lanes: Frontend tasks dispatch to Claude Code or Cursor herdr workers, and QA reports dispatch to a Claude Fable 5 worker, while the orchestrator retains all checkpoint commits.
  • Use Case: Given a spec at .compozy/tasks/<slug> decomposed into task files, run the loop to execute each task with focused validation, produce QA artifacts, remediate deep-review findings until SHIP, and land green exact-head PR CI.

Quick Start

Activate the cy-loop-tasks skill for slug <slug> and continue autonomously until Phase E or a proven external blocker.

Frequently Asked Questions about cy-loop-tasks

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

FAQPage Schema
How do I run a Compozy spec to completion automatically?

Invoke the cy-loop-tasks skill with the spec slug under .compozy/tasks/. It runs a detect-phase script each iteration, executes one phase action (task, QA, review round, or delivery), commits a checkpoint, and continues until Phase E or a proven external blocker.

How do I delegate frontend tasks to Claude Code or Cursor workers?

Pass --frontend claude or --frontend cursor at invocation; bootstrap records it in state.yaml and every frontend-typed task dispatches to a herdr worker TUI. The worker implements and validates but never commits; the orchestrator owns the checkpoint commit.

When should I not use cy-loop-tasks?

Do not use it for one-off tasks, PRD or spec authoring, or a slug that has spec documents but no task graph; use cy-implement-spec for the latter. It also refuses to bootstrap when _spec.md is missing.

What happens when a command or gate fails mid-loop?

The failure stays inside the current phase action: the recovery loop diagnoses the root cause, repairs it, and reruns the narrowest failing command before any state update. Only a proven external blocker, with exhausted alternatives recorded, produces outcome=blocked.

Does cy-loop-tasks support stacked pull requests?

Yes, in tasks mode only: pass --stacked at bootstrap and each Phase B checkpoint publishes its task as one gh stack layer with a draft PR. The loop submits the stack but never merges it.