Compose Workflow

Chain multiple bigpowers skills into a custom workflow recipe saved in specs/. Use when a project repeats a non-standard skill sequence, or user wants a documented playbook beyond orchestrate-project modes.

292 stars 23 forksProductivity & Notes

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add danielvm-git/bigpowers --skill compose-workflow
Manual install
git clone --depth 1 https://github.com/danielvm-git/bigpowers.git /tmp/bigpowers
mkdir -p ~/.claude/skills
cp -r /tmp/bigpowers/.cline/skills/compose-workflow ~/.claude/skills/compose-workflow

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Compose Workflow
> **HARD GATE** — **HARD GATE** — Workflows are orchestration, not automation. Do NOT create workflows for tasks that should be single skills. Workflow complexity must be justified.

## Process

1. Interview: goal, phases, which skills, gates between steps.
2. Write `specs/workflows/<name>.yaml`:
   - `name`, `command`, `description`, `skills[]`, `verify`
   - Optional: `args` for skill-specific arguments
3. Register in state.yaml Active Decisions.
4. Optional: reference from `orchestrate-project` Ad-Hoc mode.

> **Prefer the YAML recipe format** over the legacy `specs/WORKFLOW-<name>.md` markdown format.
> YAML recipes are command-mappable, machine-readable, and listed in the Standard Recipe Library.

## Terminal-state taxonomy (e45s27)

Every workflow step and `/loop` tick MUST exit with exactly one terminal state:

| State | Meaning | Next action |
|-------|---------|-------------|
| `success` | Step verify passed; artifacts written | Advance to next skill in recipe |
| `no-op` | Nothing to do (already green / already applied) | Skip step; advance |
| `blocked` | External gate (approval, red CI, missing dep) | `diagnose-stall` or escalate to user |
| `exhausted` | Max iterations/cycles reached (review cap, dispatch cycles) | Stop; human decision required |

Record terminal state in `specs/state.yaml` `handoff.last_terminal_state` when a recipe step completes. `/loop` ticks that produce no progress for two consecutive wakes → invoke `diagnose-stall`.
Read the full skill on GitHub

Details

Skill name
compose-workflow
Path
.cline/skills/compose-workflow/SKILL.md
License
MIT
Repo updated
9 November 2026

FAQ

What does the Compose Workflow skill do?

Chain multiple bigpowers skills into a custom workflow recipe saved in specs/. Use when a project repeats a non-standard skill sequence, or user wants a documented playbook beyond orchestrate-project modes.

How do I install the Compose Workflow skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add danielvm-git/bigpowers --skill compose-workflow. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Compose Workflow popular?

It lives in danielvm-git/bigpowers, which has 292 GitHub stars and 23 forks.

Related skills

Align Grid

292

danielvm-git/bigpowers

Build editorial/magazine/report webpages on a GENUINE Müller-Brockmann modular grid (International Typographic Style) — not a decorative one. Encodes the discipline (columns + modules + baseline, grotesque type, flush-left, restrained black/white/red palette) AND the hard-won front-end engineering to make the grid real, visible, and verified: one CSS-variable source of truth, an interactive grid-toggle overlay that lives in the SAME content box as the content, subgrid "bands" so every element snaps to a column line, an 8px baseline lock, and runtime OPTICAL ALIGNMENT that puts display type's i

Writing & Content23

Assess Impact

292

danielvm-git/bigpowers

Analyze the blast radius of a proposed change before any code is written. Maps dependents, affected stories, and test coverage. Produces specs/IMPACT_LATEST.md. Use before plan-work on any non-trivial change, when touching a shared module, or when the user asks "what does this break?".

Testing & QA23

Audit Code

292

danielvm-git/bigpowers

Self-review checklist for the coding agent to run before dispatching a reviewer. Checks CONVENTIONS.md compliance, Boy Scout Rule, test coverage, types, and SOLID. Produces a pass/fail checklist. Use before request-review, before committing, or when user asks for a code quality check.

Software Development23

Context Window Design

207

Owl-Listener/ai-design-skills

Designing around token limits, memory, and conversation persistence.

Productivity & Notes37

Bias Detection Design

207

Owl-Listener/ai-design-skills

Designing review workflows to surface and mitigate bias in AI outputs.

Productivity & Notes37

Delegate Task

292

danielvm-git/bigpowers

Delegate one complex task to a single subagent, review its work in two stages before merging back. Sequential — one agent at a time, with oversight. Use when a task is complex and requires careful review before the result is accepted. Distinct from dispatch-agents (no parallelism here; reviewer sees full diff before proceeding).

Productivity & Notes23

Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.