Compound Workflow

Compound Workflow is a portable, command-first system for shipping software with less ambiguity and stronger verification. It follows a simple cycle: clarify -> plan -> execute -> verify -> capture.

Use it when you want repeatable delivery without ad-hoc process drift.

Inspired by Compound Engineering (Every).

Best fit when you need:

• Clear intent and acceptance criteria before coding
• Structured execution with explicit review gates
• A repeatable process that captures reusable learnings

Workflow

The workflow turns a request into validated output and reusable team knowledge.

flowchart LR
  A["brainstorm"] --> B["plan"] --> C["work (includes triage)"] --> D["review"] --> E["capture"] --> F["metrics"]

Get Started

1. Install the package

npm install compound-workflow

2. Automatic setup

The package’s postinstall script runs and configures your repo: AGENTS.md, standard directories, and OpenCode wiring. No separate npx step is needed.

3. If lifecycle scripts were skipped

If your package manager didn’t run postinstall, run once:

npx compound-workflow install

Restart Cursor after install; enable third-party plugins in Settings if skills/commands don't appear.

4. After updating the package

To get the latest commands and wiring (e.g. after npm update compound-workflow or a new release), run install again so your project’s opencode.json is refreshed:

npx compound-workflow install

What gets configured

• Workflow template in AGENTS.md
• Standard workspace directories (plans, todos, docs)
• opencode.json managed entries pointing at node_modules/compound-workflow/src/.agents/*

Breaking Change (2.0.0)

2.0.0 removes all legacy compatibility pathways (/setup, /sync, runtime mirror copies, and Cursor sync fallbacks). See migration notes in docs/migrations/2026-03-03-v2-native-cutover.md.

Critical Path

After install, use this default sequence:

1. /workflow:brainstorm for requirements clarity
2. /workflow:plan for implementation design
3. /workflow:work to execute against the approved plan (includes automatic triage)
4. /workflow:review to validate quality before completion
5. /workflow:compound to capture reusable learnings

Optional:

• /workflow:triage for manual backlog curation before or during execution
• /metrics and /assess for process improvement

Commands (Quick Map)

Core flow: /workflow:brainstorm -> /workflow:plan -> /workflow:work -> /workflow:review -> /workflow:compound -> /metrics (optional /assess for rollups).

| Command | Purpose | Related skills | Related agents | | ---------------------- | ------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | /install | Configure workflow files and runtime wiring in the repo | install CLI (no workflow skill routing) | none | | /workflow:brainstorm | Clarify what to build through structured discussion | brainstorming (primary), document-review (optional refinement) | repo-research-analyst | | /workflow:plan | Convert intent into an executable plan with fidelity/confidence | state-orchestration skill when needed (for example xstate-actor-orchestration) | repo-research-analyst, learnings-researcher, best-practices-researcher, framework-docs-researcher, git-history-analyzer, spec-flow-analyzer, planning-technical-reviewer | | /workflow:triage | Manual queue curation for complex/multi-item backlogs (optional; /workflow:work runs triage automatically) | file-todos | none | | /workflow:work | Execute plan/todos with quality gates and validation evidence | git-worktree, file-todos, standards, state-orchestration skill when needed | repo-research-analyst, learnings-researcher, best-practices-researcher, framework-docs-researcher, git-history-analyzer | | /workflow:review | Perform independent quality review before completion | git-worktree (for non-current targets), standards | learnings-researcher, lint, bug-reproduction-validator, git-history-analyzer, framework-docs-researcher, agent-native-reviewer | | /workflow:compound | Capture reusable implementation learnings in docs/solutions/ | compound-docs (primary), document-review (optional) | learnings-researcher, best-practices-researcher, framework-docs-researcher | | /metrics | Log session outcomes and improvement actions | process-metrics, file-todos (optional for follow-ups) | none | | /assess | Aggregate metrics trends and propose process improvements | file-todos (for approved follow-up actions) | none | | /test-browser | Validate affected routes with browser-level checks | agent-browser, git-worktree (optional branch isolation) | none |

Canonical command docs: src/.agents/commands/

Learn More

• Workflow principles: docs/principles/workflow-baseline-principles.md
• Project command and policy index: src/AGENTS.md
• Command definitions: src/.agents/commands/

If docs conflict: follow docs/principles/workflow-baseline-principles.md, then src/AGENTS.md, then command docs.

Guardrails:

• Independent review policy: code/config changes require /workflow:review before workflow completion (docs-only changes are exempt).
• Standards baseline policy: code/config changes must pass the standards baseline gate in /workflow:work and /workflow:review.