Menu
Use when an OpenSpec proposal, tasks.md handoff, or archive checkpoint must stay aligned with a Superpowers implementation workflow.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when creating or editing an Omniskills workflow bundle, bundle skill, entry skill, orchestrator skill, skill tree, or workflow that composes multiple agent skills into one callable skill.
Use when writing or reviewing Omniskills workflow skill files, entry skills, local role skills, step instructions, approval gates, handoffs, or Superpowers/Matt Pocock dependency choices.
Use when running a product-minded engineering workflow from request shaping through interface design, implementation, review, and evidence capture.
Use when shaping a product-development request that should be grilled before Superpowers design and planning.
Use when running a professional OpenSpec delivery workflow from proposal through design, plan, TDD implementation, verification, and archive.
| 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 an Omniskills workflow 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.