Menu
Standalone OpenCode workflow for OpenSpec proposal, design, specs, and tasks.
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
| name | openspec-feature-workflow |
| description | Standalone OpenCode workflow for OpenSpec proposal, design, specs, and tasks. |
Use this standalone skill when the feature needs OpenSpec artifacts before implementation.
This is an explicit opt-in workflow. Do not use it by default. Only use it when the user explicitly asks for it, names openspec-feature-workflow or $openspec-feature-workflow, or a repository policy explicitly requires it.
openspec/changes/<change-name>/.openspec status --change "<change-name>" --json.openspec instructions <artifact> --change "<change-name>" --json.proposal.mddesign.mdspecs/.../spec.mdtasks.mdopenspec status --change "<change-name>" --json until all required artifacts are ready.Use when the user explicitly wants this workflow, wants Superpowers exploration before OpenSpec artifacts, or is confirming or continuing tasks that this workflow already generated.
Use when the user explicitly wants this workflow, wants Superpowers exploration before OpenSpec artifacts, or is confirming or continuing tasks that this workflow already generated.
Use when the user explicitly wants this workflow, wants Superpowers exploration before OpenSpec artifacts, or is confirming or continuing tasks that this workflow already generated.
Standalone OpenCode workflow for OpenSpec-first artifacts, then Superpowers implementation planning, TDD, and verification, including follow-up turns that confirm or revise generated tasks.
Standalone OpenCode workflow for clarification, design, planning, TDD, and verification.
Standalone OpenCode workflow for capturing durable project knowledge, current state, session outcomes, and reusable lessons after meaningful work.