<div align="center"> <h1>Compozy</h1> <p><strong>Orchestrate AI coding agents from idea to shipped code — in a single pipeline.</strong></p> <p> <a href="https://github.com/compozy/compozy/actions/workflows/ci.yml"> <img src="https://github.com/compozy/compozy/actions/workflows/ci.yml/badge.svg" alt="CI"> </a> <a href="https://pkg.go.dev/github.com/compozy/compozy"> <img src="https://pkg.go.dev/badge/github.com/compozy/compozy.svg" alt="Go Reference"> </a> <a href="https://goreportcard.com/report/github.com/compozy/compozy"> <img src="https://goreportcard.com/badge/github.com/compozy/compozy" alt="Go Report Card"> </a> <a href="LICENSE"> <img src="https://img.shields.io/badge/License-MIT-blue.svg" alt="License: MIT"> </a> <a href="https://github.com/compozy/compozy/releases"> <img src="https://img.shields.io/github/v/release/compozy/compozy?include_prereleases" alt="Release"> </a> </p> </div>

One CLI to replace scattered prompts, manual task tracking, and copy-paste review cycles. Compozy drives the full lifecycle of AI-assisted development: product ideation, technical specification, task breakdown with codebase-informed enrichment, concurrent execution across agents, and automated PR review remediation.

✨ Highlights

One command, 40+ agents. Install bundled skills into Claude Code, Codex, Cursor, Droid, OpenCode, Pi, and 40+ other agents and editors with compozy setup — no npm, pipx, or external tools required.
Idea to code in 5 steps. Structured pipeline: PRD → TechSpec → Tasks → Execution → Review. Each phase produces plain markdown artifacts that feed into the next.
Codebase-aware enrichment. Tasks aren't generic prompts. Compozy spawns parallel agents to explore your codebase, discover patterns, and ground every task in real project context.
Multi-agent execution. Run tasks through Claude Code, Codex, Cursor, Droid, OpenCode, or Pi — just change --ide. Concurrent batch processing with configurable timeouts, retries, and exponential backoff, all with a live terminal UI.
Workflow memory between runs. Agents inherit context from every previous task — decisions, learnings, errors, and handoffs. Two-tier markdown memory with automatic compaction keeps context fresh without manual bookkeeping.
Provider-agnostic reviews. Fetch review comments from CodeRabbit, GitHub, or run AI-powered reviews internally. All normalize to the same format. Provider threads resolve automatically after fixes.
Markdown everywhere. PRDs, specs, tasks, reviews, and ADRs are human-readable markdown files. Version-controlled, diffable, editable between steps. No vendor lock-in.
Frontmatter for machine-readable metadata. Tasks and review issues keep parseable metadata in standard YAML frontmatter instead of custom XML tags.
Single binary, local-first. Compiles to one Go binary with zero runtime dependencies. Your code and data stay on your machine.
Embeddable. Use as a standalone CLI or import as a Go package into your own tools.

📦 Installation

Homebrew

brew tap compozy/compozy
brew install --cask compozy

NPM

npm install -g @compozy/cli

Go

go install github.com/compozy/compozy/cmd/compozy@latest

From Source

git clone git@github.com:compozy/compozy.git
cd compozy && make verify && go build ./cmd/compozy

Then install bundled skills into your AI agents:

compozy setup          # interactive — pick agents and skills
compozy setup --all    # install everything to every detected agent

🔄 How It Works

compozy setup                           Install skills (once per project)
   │
   ▼
/cy-create-prd user-auth               .compozy/tasks/user-auth/_prd.md
   │                                    + Architecture Decision Records
   ▼
/cy-create-techspec user-auth          .compozy/tasks/user-auth/_techspec.md
   │
   ▼
/cy-create-tasks user-auth             .compozy/tasks/user-auth/task_01.md … task_N.md
   │
   ▼
compozy sync --name user-auth          Refresh task workflow _meta.md
   │
   ▼
compozy start --name user-auth         AI agents execute each task
   │                                    ↕ .compozy/tasks/user-auth/memory/
   │
   ▼
compozy fetch-reviews / /cy-review-round  .compozy/tasks/user-auth/reviews-001/
   │
   ▼
compozy fix-reviews --name user-auth   Issues triaged, fixed, resolved
   │
   ▼
compozy archive --name user-auth       Move fully completed workflow to _archived/
   │
   ▼
Repeat until clean → Ship

Every artifact is a plain markdown file in .compozy/tasks/<name>/. You can read, edit, or version-control any of them between steps.

Task and review issue files use YAML frontmatter for parseable metadata such as status, domain, severity, and provider_ref. Task workflow _meta.md files can be refreshed explicitly with compozy sync. Fully completed workflows can be moved out of the active task root with compozy archive. If you have an older project with XML-tagged artifacts, run compozy migrate once before using start or fix-reviews.

🚀 Quick Start

This walkthrough builds a feature called user-auth from idea to shipped code.

1. Install skills

compozy setup --all --yes

Auto-detects installed agents and copies (or symlinks) skills into their configuration directories.

2. Create a PRD

Inside your AI agent (Claude Code, Codex, Cursor, OpenCode, Pi, etc.):

/cy-create-prd user-auth

Interactive brainstorming session — asks clarifying questions, spawns parallel agents to research your codebase and the web, produces a business-focused PRD with ADRs.

3. Create a TechSpec

/cy-create-techspec user-auth

Reads your PRD, explores the codebase architecture, asks technical clarification questions. Produces architecture specs, API designs, and data models.

4. Break down into tasks

/cy-create-tasks user-auth

Analyzes both documents, explores your codebase for relevant files and patterns, produces individually executable task files with status tracking, context, and acceptance criteria.

5. Execute tasks

compozy start --name user-auth --ide claude

Each pending task is processed sequentially — the agent reads the spec, implements the code, validates it, and updates the task status. Use --dry-run to preview prompts without executing.

6. Review

Option A — AI-powered review inside your agent:

/cy-review-round user-auth

Option B — Fetch from an external provider:

compozy fetch-reviews --provider coderabbit --pr 42 --name user-auth

Both produce the same output: .compozy/tasks/user-auth/reviews-001/issue_*.md

7. Fix review issues

compozy fix-reviews --name user-auth --ide claude --concurrent 2 --batch-size 3

Agents triage each issue as valid or invalid, implement fixes for valid issues, and update statuses. Provider threads are resolved automatically.

8. Iterate and ship

Repeat steps 6–7. Each cycle creates a new review round (reviews-002/, reviews-003/), preserving full history. When clean — merge and ship.

🧩 Skills

Compozy bundles 8 skills that its workflows depend on. They run inside your AI agent — no context switching to external tools.

| Skill | Purpose | | --- | --- | | cy-create-prd | Interactive brainstorming → Product Requirements Document with ADRs | | cy-create-techspec | PRD → Technical Specification with architecture exploration | | cy-create-tasks | PRD + TechSpec → Independently implementable task files | | cy-execute-task | Executes one task end-to-end: implement, validate, track, commit | | cy-workflow-memory | Maintains cross-task context so agents pick up where the last one left off | | cy-review-round | Comprehensive code review → structured issue files | | cy-fix-reviews | Triage, fix, verify, and resolve review issues | | cy-final-verify | Enforces verification evidence before any completion claim |

🧠 Workflow Memory

When agents execute tasks, context gets lost between runs — decisions made, errors hit, patterns discovered. Compozy solves this with a two-tier memory system that gives each agent a running history of the workflow.

Every task execution automatically bootstraps two markdown files inside .compozy/tasks/<name>/memory/:

| File | Scope | What goes here | | --- | --- | --- | | MEMORY.md | Cross-task, shared | Architecture decisions, discovered patterns, open risks, handoffs between tasks | | task_01.md | Single task | Objective snapshot, files touched, errors hit, what's ready for the next run |

How it works:

Before a task runs, Compozy creates the memory directory and scaffolds both files with section templates if they don't exist yet.
The agent reads both memory files before writing any code — treating them as mandatory context, not optional notes.
During execution, the agent keeps task memory current: decisions, learnings, errors, and corrections.
Only durable, cross-task context gets promoted to shared memory. Task-local details stay in the task file.
Before completion, the agent updates memory with anything that helps the next run start faster.

Automatic compaction. Memory files have soft limits (150 lines / 12 KB for shared, 200 lines / 16 KB per task). When a file exceeds its threshold, Compozy flags it for compaction — the agent trims noise and repetition while preserving active risks, decisions, and handoffs.

No duplication. Memory files don't copy what's already in the repo, git history, PRD, or task specs. They capture only what would otherwise be lost between runs: the why behind decisions, surprising findings, and context that makes the next agent immediately productive.

The cy-workflow-memory skill handles

Compozy

Install / Use

README