Cursor rule

1---
2description: "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."
3alwaysApply: false
4---
5 
6# story: e09s01
7# story: e45s27
8# story: e21s04
9 
10# Compose Workflow
11> **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.
12 
13 
14## Process
15 
161. Interview: goal, phases, which skills, gates between steps.
172. Write `specs/workflows/<name>.yaml`:
18   - `name`, `command`, `description`, `skills[]`, `verify`
19   - Optional: `args` for skill-specific arguments
203. Register in state.yaml Active Decisions.
214. Optional: reference from `orchestrate-project` Ad-Hoc mode.
22 
23> **Prefer the YAML recipe format** over the legacy `specs/WORKFLOW-<name>.md` markdown format.
24> YAML recipes are command-mappable, machine-readable, and listed in the Standard Recipe Library.
25 
26## Terminal-state taxonomy (e45s27)
27 
28Every workflow step and `/loop` tick MUST exit with exactly one terminal state:
29 
30| State | Meaning | Next action |
31|-------|---------|-------------|
32| `success` | Step verify passed; artifacts written | Advance to next skill in recipe |
33| `no-op` | Nothing to do (already green / already applied) | Skip step; advance |
34| `blocked` | External gate (approval, red CI, missing dep) | `diagnose-stall` or escalate to user |
35| `exhausted` | Max iterations/cycles reached (review cap, dispatch cycles) | Stop; human decision required |
36 
37Record 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`.
38 
39## Standard Recipe Library
40 
41Pre-built recipes in `specs/workflows/` map agentic stack commands to skill chains.
42Reference them in AGENTS.md so `/command` directly invokes the matching recipe.
43 
44| Command | Workflow | Skill chain |
45|---------|----------|-------------|
46| `/check-stack` | check-stack | survey-context → assess-impact → setup-environment |
47| `/ship` | ship | audit-code → commit-message → release-branch |
48| `/tdd` | tdd | develop-tdd → enforce-first |
49| `/code-review` | code-review | audit-code → request-review → respond-review |
50| `/security` | security | audit-code → request-review |
51| `/plan` | plan | survey-context → research-first → plan-work |
52| `/build-fix` | build-fix | investigate-bug → diagnose-root → develop-tdd → validate-fix |
53| `/e2e` | e2e | smoke-test → verify-work |
54 
55Add to `AGENTS.md`:
56```
57/check-stack = compose-workflow check-stack
58/ship        = compose-workflow ship
59```
60 
61## Verify
62 
63→ verify: `[ "$(ls specs/workflows/*.yaml 2>/dev/null | wc -l | tr -d ' ')" -ge 8 ]`
64 
65See [REFERENCE.md](REFERENCE.md) for template.
66 
67---
68 
69# Workflow template
70 
71```markdown
72# WORKFLOW: <name>
73 
74**Trigger:** Use when ...
75 
76| Step | Skill | Output | verify |
77|------|-------|--------|--------|
78| 1 | survey-context | state.yaml handoff | ... |
79| 2 | research-first | Prior Art in SCOPE_LATEST.yaml | ... |
80| 3 | plan-work | epics/eNN-*.yaml tasks | ... |
81```
82