Individual skill

superpowers-openspec-superpowers-workflow

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.

dist/codex/bundles/superpowers-openspec-superpowers/skills/superpowers-openspec-superpowers-workflow/SKILL.md

Read pinned source

Source commit 1426ddcb85f203c7de8a13b5d1ba4cfd188fb265

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: Yes
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 201
Repository last updated: Jun 12, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

operations Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 6,079 bytes

Read excerpt


# Superpowers -> OpenSpec -> Superpowers Workflow

Use this standalone skill when feature delivery should follow a calm but rigorous sequence:

1. Explore and converge with Superpowers
2. Lock the confirmed behavior and artifacts with OpenSpec
3. Return to Superpowers for implementation, testing, and verification
4. Archive the OpenSpec change when everything is aligned

This is an explicit opt-in workflow. Do not use it by default. Only use it when the user explicitly asks for it, names `$superpowers-openspec-superpowers-workflow`, or a repository policy explicitly requires it.

If this workflow already produced `tasks.md` for the current request and the next user turn confirms, revises, or continues those tasks, keep this workflow active even if the skill name is not repeated.

If `.superpowers-memory/` exists in the repository, read it at the start and update it before the session ends.