Nv Implement
novuhq/novu
Implement planned work by fanning out parallel subagents on isolated worktrees — TDD at pre-agreed seams, per-slice nv-park-and-review, merge back, full suite once at the end.
A skill your agent uses when feature work needs the Superpowers stages before or during implementation: brainstorming, design confirmation, implementation planning, worktree setup, test-driven…
Install Superpowers Feature Workflow
$ npx skills add SYZ-Coder/superpowers-openspec-team-skills --skill superpowers-feature-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install SYZ-Coder/superpowers-openspec-team-skills superpowers-feature-workflow --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/SYZ-Coder/superpowers-openspec-team-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/team-skills/superpowers-feature-workflow .claude/skills/superpowers-feature-workflow && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "superpowers-feature-workflow" agent skill from https://github.com/SYZ-Coder/superpowers-openspec-team-skills/tree/main/team-skills/superpowers-feature-workflow into .claude/skills/superpowers-feature-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "superpowers-feature-workflow", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/SYZ-Coder/superpowers-openspec-team-skills/tree/main/team-skills/superpowers-feature-workflowType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add SYZ-Coder/superpowers-openspec-team-skills --skill superpowers-feature-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install SYZ-Coder/superpowers-openspec-team-skills superpowers-feature-workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SYZ-Coder/superpowers-openspec-team-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/team-skills/superpowers-feature-workflow .agents/skills/superpowers-feature-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "superpowers-feature-workflow" agent skill from https://github.com/SYZ-Coder/superpowers-openspec-team-skills/tree/main/team-skills/superpowers-feature-workflow into .agents/skills/superpowers-feature-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "superpowers-feature-workflow", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add SYZ-Coder/superpowers-openspec-team-skills --skill superpowers-feature-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install SYZ-Coder/superpowers-openspec-team-skills superpowers-feature-workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SYZ-Coder/superpowers-openspec-team-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/team-skills/superpowers-feature-workflow .cursor/skills/superpowers-feature-workflow && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "superpowers-feature-workflow" agent skill from https://github.com/SYZ-Coder/superpowers-openspec-team-skills/tree/main/team-skills/superpowers-feature-workflow into .cursor/skills/superpowers-feature-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "superpowers-feature-workflow", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/SYZ-Coder/superpowers-openspec-team-skills.git --path team-skills/superpowers-feature-workflow--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add SYZ-Coder/superpowers-openspec-team-skills --skill superpowers-feature-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install SYZ-Coder/superpowers-openspec-team-skills superpowers-feature-workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SYZ-Coder/superpowers-openspec-team-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/team-skills/superpowers-feature-workflow .gemini/skills/superpowers-feature-workflow && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "superpowers-feature-workflow" agent skill from https://github.com/SYZ-Coder/superpowers-openspec-team-skills/tree/main/team-skills/superpowers-feature-workflow into .gemini/skills/superpowers-feature-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "superpowers-feature-workflow", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install SYZ-Coder/superpowers-openspec-team-skills superpowers-feature-workflowInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add SYZ-Coder/superpowers-openspec-team-skills --skill superpowers-feature-workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/SYZ-Coder/superpowers-openspec-team-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/team-skills/superpowers-feature-workflow .github/skills/superpowers-feature-workflow && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "superpowers-feature-workflow" agent skill from https://github.com/SYZ-Coder/superpowers-openspec-team-skills/tree/main/team-skills/superpowers-feature-workflow into .github/skills/superpowers-feature-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "superpowers-feature-workflow", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add SYZ-Coder/superpowers-openspec-team-skills --skill superpowers-feature-workflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install SYZ-Coder/superpowers-openspec-team-skills superpowers-feature-workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SYZ-Coder/superpowers-openspec-team-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/team-skills/superpowers-feature-workflow .opencode/skills/superpowers-feature-workflow && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "superpowers-feature-workflow" agent skill from https://github.com/SYZ-Coder/superpowers-openspec-team-skills/tree/main/team-skills/superpowers-feature-workflow into .opencode/skills/superpowers-feature-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "superpowers-feature-workflow", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
superpowers-feature-workflow- GitHub stars
- 196
- Token cost
- ~891 tokens
- SKILL.md length
- 399 words
- Files
- 5
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when feature work needs the Superpowers stages before or during implementation: brainstorming, design confirmation, implementation planning, worktree setup, test-driven…
- Works in 12 steps: Explore project context before proposing… → Clarify requirements one question at a… → Present 2-3 approaches with a… → …
- Feature work needs the Superpowers stages before
- SKILL.md covers Overview, Workflow, When to Use and Outputs, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Superpowers Feature Workflow is an agent skill from SYZ-Coder/superpowers-openspec-team-skills. Use when feature work needs the Superpowers stages before or during implementation: brainstorming, design confirmation, implementation planning, worktree setup, test-driven development, and verification. Trigger when the user asks to brainstorm first, wants a plan before coding, or wants disciplined execution with TDD and verification.
Its SKILL.md is about 890 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files (for example `README.md`, `agents/openai.yaml` and `readme_cn.md`).
It sits in Testing & QA, covering Test-driven development, Brainstorming and Git worktrees. The repository describes itself as: 一套带有记忆和自学习的harness-team-skills企业级编程技能组合库 针对superpowers+openspec 进行按需组合使用,适用于个人与团队协作进行AI编程. The licence is MIT.
When your agent uses it
- Feature work needs the Superpowers stages before
- During implementation: brainstorming
- Design confirmation
- Implementation planning
Example prompts
- “/superpowers-feature-workflow”
Workflow steps
12 steps, taken from the first numbered list in SKILL.md.
- Explore project context before proposing solutions. If .superpowers-memory/ exists, read PROJECT_CONTEXT.md, CURRENT_STATE.md…
- Clarify requirements one question at a time.
- Present 2-3 approaches with a recommendation.
- Write the approved design to docs/superpowers/specs/YYYY-MM-DD--design.md.
- Ask for user confirmation on the written design before moving on.
- Write the implementation plan to docs/superpowers/plans/YYYY-MM-DD-.md.
- Prefer a repo-local worktree for implementation.
- Implement with TDD: failing test first, then minimal code, then green.
- Run fresh verification commands before any completion claim.
- Before finishing the session, run a short memory closeout check: durable facts changed, current state changed, important decisions added…
- Prefer scripts/run-superpowers-memory-closeout.ps1 when you want one command to review the checklist, get update suggestions, and…
- Use scripts/suggest-superpowers-memory-updates.ps1 when the right memory surface is still unclear after implementation or verification.
What it can do on your machine
Read from SKILL.md and the folder at commit 1426ddc. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Superpowers Feature Workflow loads about 891 tokens when it runs. Until then it costs about 92 tokens; SKILL.md has 399 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from SYZ-Coder/superpowers-openspec-team-skills at commit 1426ddc, republished under its MIT licence (© SYZ-Coder). 399 words, ~891 tokens.
Download SKILL.mdSave it as
.claude/skills/superpowers-feature-workflow/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- superpowers-feature-workflow
- description
- Use when feature work needs the Superpowers stages before or during implementation: brainstorming, design confirmation, implementation planning, worktree setup, test-driven development, and verification. Trigger when the user asks to brainstorm first, wants a plan before coding, or wants disciplined execution with TDD and verification.
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
- Explore project context before proposing solutions. If
.superpowers-memory/exists, readPROJECT_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. - Clarify requirements one question at a time.
- Present 2-3 approaches with a recommendation.
- Write the approved design to
docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md. - Ask for user confirmation on the written design before moving on.
- Write the implementation plan to
docs/superpowers/plans/YYYY-MM-DD-<topic>.md. - Prefer a repo-local worktree for implementation.
- Implement with TDD: failing test first, then minimal code, then green.
- Run fresh verification commands before any completion claim.
- 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.
- Prefer
scripts/run-superpowers-memory-closeout.ps1when you want one command to review the checklist, get update suggestions, and optionally run validation. - Use
scripts/suggest-superpowers-memory-updates.ps1when the right memory surface is still unclear after implementation or verification. - When the repo uses Superpowers memory, update the relevant memory files, including
.superpowers-memory/CURRENT_STATE.mdand a short session note under.superpowers-memory/session-journal/. - When memory quality matters for the task, run
scripts/validate-superpowers-memory.ps1before the final completion claim.
Show full SKILL.md (138 more words)Show less
When to Use
- The user explicitly asks to brainstorm first
- The user explicitly names
$superpowers-feature-workflow - The user explicitly asks for a written plan, TDD, or verification workflow
- A repository policy explicitly requires this workflow
Outputs
- Confirmed design doc
- Implementation plan
- Verified implementation evidence
- Updated Superpowers memory when
.superpowers-memory/is present - Optional closeout helper output when the closeout helper was used
- Memory validation evidence when memory updates were part of the workflow
Guardrails
- Do not write production code before design approval
- Do not skip the failing-test step for new behavior
- Do not report success without fresh command output
- Do not overwrite stable project memory with temporary notes; keep long-term facts in
PROJECT_CONTEXT.mdand session-specific updates in the journal - Do not leave new durable decisions, known failures, or verification rules only in chat history when the repo uses Superpowers memory
© SYZ-Coder, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files in team-skills/superpowers-feature-workflow of SYZ-Coder/superpowers-openspec-team-skills.
- SKILL.md
- README.md
- agents/openai.yaml
- readme_cn.md
- workflow.yaml
Open the folder on GitHubat commit 1426ddc
Compare with similar skills
Superpowers Feature Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Superpowers Feature Workflow this skillSYZ-Coder/superpowers-openspec-team-skills | 196 | — | ~891 | Automated safety check: Pass | MIT | |
| Nv Implementnovuhq/novu | 40k | — | ~1.7k | Automated safety check: Pass | Custom licence | |
| Ca FeaturearbiterForge/codeArbiter | 147 | — | ~2.2k | Automated safety check: Pass | AGPL-3.0 | |
| Evanflow Goevanklem/evanflow | 418 | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| Component Design With TdadHabitat-Thinking/ai-literacy-superpowers | 114 | — | ~3.3k | Automated safety check: Pass | Custom licence | |
| Work Issuejoesaby/astro-mermaid | 123 | — | ~891 | Automated safety check: Pass | MIT |
Similar skills
Ca Feature
arbiterForge/codeArbiter
Start a feature: brainstorm a spec, get it approved, then drive it test-first through the pipeline.
Evanflow Go
evanklem/evanflow
Single entry-point orchestrator for the entire EvanFlow loop.
Component Design With Tdad
Habitat-Thinking/ai-literacy-superpowers
A skill your agent uses when designing a new plugin component (skill, agent, command, or backing script) for the ai-literacy-superpowers plugin or a sister plugin in this marketplace.
Work Issue
joesaby/astro-mermaid
End-to-end workflow for resolving a GitHub issue in astro-mermaid — triages complexity, then runs brainstorm → TDD → implement → docs/spec → code review at the right depth.
Issue Resolve
ffroliva/gflow-cli
A skill your agent uses when an assessed gflow-cli issue (verdict CONFIRMED-BUG or LIKELY-BUG) has localized, verifiable scope and should be driven to a fix.
More from SYZ-Coder/superpowers-openspec-team-skills
Superpowers Openspec Superpowers Workflow
SYZ-Coder/superpowers-openspec-team-skills
A skill your agent uses when the user explicitly wants this workflow, wants Superpowers exploration before OpenSpec artifacts, or is confirming or continuing tasks that this workflow already…
Openspec Feature Workflow
SYZ-Coder/superpowers-openspec-team-skills
A skill your agent uses when a feature needs an OpenSpec change with proposal, design, specs, and tasks completed before coding.
Openspec Superpowers Workflow
SYZ-Coder/superpowers-openspec-team-skills
A skill your agent uses when the user explicitly wants an OpenSpec-first path that creates proposal, design, specs, and tasks before handing off to Superpowers execution, verification, and optional…
Superpowers Learning Workflow
SYZ-Coder/superpowers-openspec-team-skills
A skill your agent uses when the user explicitly wants to capture lessons from completed work, persist durable project knowledge, or turn repeated patterns into reusable learning notes for future…
Related
Categories
Questions about Superpowers Feature Workflow
What does Superpowers Feature Workflow do?
A skill your agent uses when feature work needs the Superpowers stages before or during implementation: brainstorming, design confirmation, implementation planning, worktree setup, test-driven…. Superpowers Feature Workflow is an agent skill from SYZ-Coder/superpowers-openspec-team-skills. Use when feature work needs the Superpowers stages before or during implementation: brainstorming, design confirmation, implementation planning, worktree setup, test-driven development, and verification.
When should I use Superpowers Feature Workflow?
Superpowers Feature Workflow fits situations like: feature work needs the Superpowers stages before; during implementation: brainstorming; design confirmation; implementation planning.
How do I install Superpowers Feature Workflow in Claude Code?
Run `npx skills add SYZ-Coder/superpowers-openspec-team-skills --skill superpowers-feature-workflow -a claude-code`. Or copy the skill folder (team-skills/superpowers-feature-workflow in SYZ-Coder/superpowers-openspec-team-skills) into .claude/skills/superpowers-feature-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Superpowers Feature Workflow in Codex?
Run `npx skills add SYZ-Coder/superpowers-openspec-team-skills --skill superpowers-feature-workflow -a codex`. Or copy the skill folder (team-skills/superpowers-feature-workflow in SYZ-Coder/superpowers-openspec-team-skills) into .agents/skills/superpowers-feature-workflow in your project. Codex loads it when a task matches its description.
Can I use Superpowers Feature Workflow in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add SYZ-Coder/superpowers-openspec-team-skills --skill superpowers-feature-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/superpowers-feature-workflow, .gemini/skills/superpowers-feature-workflow, .github/skills/superpowers-feature-workflow and .opencode/skills/superpowers-feature-workflow in your project.
What does Superpowers Feature Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Superpowers Feature Workflow is instructions for the agent only.
Does Superpowers Feature Workflow access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Superpowers Feature Workflow safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Superpowers Feature Workflow use?
Superpowers Feature Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Superpowers Feature Workflow use?
About 891 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Superpowers Feature Workflow?
Skills that share tags, products or a category with Superpowers Feature Workflow: Nv Implement (novuhq/novu, 40k stars), Ca Feature (arbiterForge/codeArbiter, 147 stars), Evanflow Go (evanklem/evanflow, 418 stars) and Component Design With Tdad (Habitat-Thinking/ai-literacy-superpowers, 114 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Superpowers Feature Workflow?
SYZ-Coder (a GitHub user) maintains it in SYZ-Coder/superpowers-openspec-team-skills, which has 196 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on June 12, 2026.
Source: SYZ-Coder/superpowers-openspec-team-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.