菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
Create new bigpowers skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill for the bigpowers lifecycle.
Refine a rough idea into a clear, detailed specification through dialogue. Does not produce code. Use when user has a vague idea, wants to think through a feature before planning, or needs to turn "I want X" into a concrete spec.
Benchmark-gated skill evolution — consume bigpowers-benchmark report, propose plan-work change, edit skill via craft-skill, re-run benchmark, record ADR. Use when a skill underperforms on benchmark or stocktake finds systemic gap.
Interactive assumption-surfacing Q&A that stress-tests a plan through relentless questioning until every decision is resolved. Use when user wants to challenge a plan, validate decisions from conversation/context, or mentions "grill me". For doc-grounded variant, use grill-with-docs.
Block dangerous git commands (push, force push, reset --hard, clean, branch -D, checkout/restore .) and enforce Conventional Commits & Branch Protection before an AI agent runs them. Installs hook scripts for Claude Code, Cursor, Cursor CLI, and Gemini CLI; documents Google Antigravity Terminal deny lists. Use when the user wants git safety hooks, to block git push or destructive git in agents, or to mirror the same policy across AI coding tools.
| name | compose-workflow |
| model | sonnet |
| description | 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. |
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.
specs/workflows/<name>.yaml:
name, command, description, skills[], verifyargs for skill-specific argumentsorchestrate-project Ad-Hoc mode.Prefer the YAML recipe format over the legacy
specs/WORKFLOW-<name>.mdmarkdown format. YAML recipes are command-mappable, machine-readable, and listed in the Standard Recipe Library.
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.
Pre-built recipes in specs/workflows/ map agentic stack commands to skill chains.
Reference them in AGENTS.md so /command directly invokes the matching recipe.
| Command | Workflow | Skill chain |
|---|---|---|
/check-stack | check-stack | survey-context → assess-impact → setup-environment |
/ship | ship | audit-code → commit-message → release-branch |
/tdd | tdd | develop-tdd → enforce-first |
/code-review | code-review | audit-code → request-review → respond-review |
/security | security | audit-code → request-review |
/plan | plan | survey-context → research-first → plan-work |
/build-fix | build-fix | investigate-bug → diagnose-root → develop-tdd → validate-fix |
/e2e | e2e | smoke-test → verify-work |
Add to AGENTS.md:
/check-stack = compose-workflow check-stack
/ship = compose-workflow ship
→ verify: ls specs/workflows/*.yaml 2>/dev/null | wc -l | awk '{if($1>=8) print "OK: " $1 " recipes"; else print "FAIL"}'
See REFERENCE.md for template.
# WORKFLOW: <name>
**Trigger:** Use when ...
| Step | Skill | Output | verify |
|------|-------|--------|--------|
| 1 | survey-context | state.yaml handoff | ... |
| 2 | research-first | Prior Art in SCOPE_LATEST.yaml | ... |
| 3 | plan-work | epics/eNN-*.yaml tasks | ... |