菜单
Use when an OpenSpec proposal, tasks.md handoff, or archive checkpoint must stay aligned with a Superpowers implementation workflow.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | opsx-handoff-review |
| description | Use when an OpenSpec proposal, tasks.md handoff, or archive checkpoint must stay aligned with a Superpowers implementation workflow. |
Use this skill to keep the OpenSpec side of a GetSuperpower explicit while Superpowers owns design, build, and verification.
| Checkpoint | Confirm |
|---|---|
/opsx:propose | proposal.md, specs/, and tasks.md exist |
| Human review | proposal.md scope and design direction are approved |
| Handoff | tasks.md preserves acceptance criteria and relevant specs/ paths |
| Delivery | Superpowers returns changed files, checks, and verification evidence |
/opsx:archive | Final behavior is merged back into specs and project knowledge |
proposal.md.tasks.md as a loose note instead of the scope handoff contract.Use when writing or reviewing GetSuperpower workflow skill files, entry skills, local role skills, step instructions, approval gates, handoffs, or Superpowers/Matt Pocock dependency choices.
Startup-team CEO role for company direction, tradeoffs, and strategic decisions.
Startup-team CTO role for architecture, technical risk, and engineering strategy.
Startup-team engineering manager role for delivery sequencing and quality gates.
Startup-team founding engineer role for implementation, tests, debugging, review, and verification.
Startup-team product manager role for discovery, PRDs, and issue slicing.