Individual skill

superpowers-feature-workflow

0upvotes

Standalone Codex workflow for clarification, design, planning, TDD, and verification.

dist/codex/bundles/superpowers-feature/skills/superpowers-feature-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.

design Derived category
operations Derived category
testing 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 · 1,540 bytes

Read excerpt


# Superpowers Feature Workflow

Use this standalone skill when you want disciplined feature delivery without OpenSpec artifact generation.

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-feature-workflow`, or a repository policy explicitly requires it.

## Workflow

1. Explore project context first. If `.superpowers-memory/` exists, read `PROJECT_CONTEXT.md`, `CURRENT_STATE.md`, and the latest session journal entries before asking questions.
2. Clarify requirements one question at a time.
3. Present 2-3 approaches and recommend one.
4. Write the approved design to `docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md`.
5. Ask the user to confirm the written design.
6. Write the implementation plan to `docs/superpowers/plans/YYYY-MM-DD-<topic>.md`.