agentmods.dev

superpowers-feature-workflow

superpowers-feature-workflow is a skill for Codex from SYZ-Coder/superpowers-openspec-team-skills. It costs 64 tokens per session (736 once invoked), scanned A, original, MIT.

A staged workflow for feature development, covering idea clarification, design approval, planning, separate workspaces, test-driven development (writing a failing test before the code), and verification.

In plain words
What is it for?
Use it when you want to brainstorm before coding, approve a design, create an implementation plan, work in a separate worktree, build with TDD, and verify the result.
Why use it?
It prevents coding from starting with unclear requirements or an unreviewed design. It also keeps implementation steps and checks recorded in the repository.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: $skill-name invocation.

not rated 192repo +2 2mo ago A scan 64 tokens original MIT

Good fit Use it when you want to brainstorm before coding, approve a design, create an implementation plan, work in a separate worktree, build with TDD, and verify the result.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/syz-coder/superpowers-openspec-team-skills/superpowers-feature-workflow
View source ↗ SYZ-Coder/superpowers-openspec-team-skills
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add SYZ-Coder/superpowers-openspec-team-skills --skill superpowers-feature-workflow
Clone the repo
git clone --depth 1 https://github.com/SYZ-Coder/superpowers-openspec-team-skills

Made for: Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for superpowers-feature-workflow

README.md
[![agentmods](https://agentmods.dev/badge/skills/syz-coder/superpowers-openspec-team-skills/superpowers-feature-workflow/github.svg)](https://agentmods.dev/skills/syz-coder/superpowers-openspec-team-skills/superpowers-feature-workflow)
Your own site
<a href="https://agentmods.dev/skills/syz-coder/superpowers-openspec-team-skills/superpowers-feature-workflow"><img src="https://agentmods.dev/badge/skills/syz-coder/superpowers-openspec-team-skills/superpowers-feature-workflow/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for superpowers-feature-workflow

Your own site · 80×15
<a href="https://agentmods.dev/skills/syz-coder/superpowers-openspec-team-skills/superpowers-feature-workflow"><img src="https://agentmods.dev/badge/skills/syz-coder/superpowers-openspec-team-skills/superpowers-feature-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 64 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 736 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00064 $0.00736
Opus 5 $0.00032 $0.00368
Sonnet 5 $0.00013 $0.00147
Haiku 4.5 $0.00006 $0.00074

Measured 9d ago against content hash 45730ed6ebec, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

superpowers-feature-workflow scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

team-skills/superpowers-feature-workflow/SKILL.md · 54 lines

How it starts

The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Superpowers Feature Workflow

Overview

Use this skill for the Superpowers half of feature delivery. It covers clarification, design, plan, worktree, TDD, verification, and repo-persisted memory, but it does not manage OpenSpec artifacts.

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

Workflow

  1. Explore project context before proposing solutions. If .superpowers-memory/ exists, read PROJECT_CONTEXT.md, CURRENT_STATE.md, DECISIONS.md, KNOWN_FAILURES.md, VERIFICATION_BASELINE.md, TEAM_PREFERENCES.md, USER_PROFILE.md, AGENT_NOTES.md, and the latest session journal entries first.
  2. Clarify requirements one question at a time.
  3. Present 2-3 approaches with a recommendation.
  4. Write the approved design to docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md.
  5. Ask for user confirmation on the written design before moving on.
  6. Write the implementation plan to docs/superpowers/plans/YYYY-MM-DD-<topic>.md.
  7. Prefer a repo-local worktree for implementation.
  8. Implement with TDD: failing test first, then minimal code, then green.
  9. Run fresh verification commands before any completion claim.
  10. Before finishing the session, run a short memory closeout check: durable facts changed, current state changed, important decisions added, failure patterns discovered, verification rules changed, and reusable lessons identified.
  11. Prefer scripts/run-superpowers-memory-closeout.ps1 when you want one command to review the checklist, get update suggestions, and optionally run validation.
  12. Use scripts/suggest-superpowers-memory-updates.ps1 when the right memory surface is still unclear after implementation or verification.
  13. When the repo uses Superpowers memory, update the relevant memory files, including .superpowers-memory/CURRENT_STATE.md and a short session note under .superpowers-memory/session-journal/.
  14. When memory quality matters for the task, run scripts/validate-superpowers-memory.ps1 before the final completion claim.

Read the full file on GitHub · 54 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 54 lines · 0 tokens per session scan A 45730ed6ebec

Subscribe to this mod's changes

superpowers-feature-workflow is a skill published in the GitHub repository SYZ-Coder/superpowers-openspec-team-skills (192 stars, last pushed 2mo ago), licensed MIT. It adds 64 tokens to every session and 736 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

PlanningTDDTesting
Related

Other skills, from other repositories

engram-testing-coverage

TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.

Gentleman-Programming/engram · 25 tokens

nw-fp-clojure

Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.

nWave-ai/nWave · 25 tokens

strict-tdd

Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.

a5c-ai/babysitter · 34 tokens

mobiai-mobile-tdd

You MUST use this before writing any implementation code for a mobile feature, bug fix, refactor, or behavior change. Tests come before implementation — no exceptions.

ArisGuimera/MobiAI-Core · 38 tokens

tdd

This skill should be used when the user wants to implement features or fix bugs using test-driven development. Enforces the RED-GREEN-REFACTOR cycle with vertical slicing, context isolation between test writing and implementation, human checkpoints, and auto-test feedback loops. Uses multi-agent orchestration with the…

glebis/claude-skills · 92 tokens

conductor-implement

Execute tasks from a track's implementation plan following TDD workflow.

rmyndharis/antigravity-skills · 17 tokens