superpowers-workflow
- Repo stars 774
- Author updated Live
- Author repo gemini-superpowers-antigravity
- Domain
- AI
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @anthonylee991 · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- Python
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: superpowers-workflow
description: Enforces a disciplined workflow for coding, debugging, refactoring, and automation: brainstorm -…
category: ai
runtime: Python
---
# superpowers-workflow output preview
## PART A: Task fit
- Use case: Enforces a disciplined workflow for coding, debugging, refactoring, and automation: brainstorm -> plan -> implement with verification (prefer TDD) -> review -> finish. Use for almost any non-trivial change..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “When to use this skill / Activation marker (required) / Default workflow (mandatory unless explicitly unnecessary)” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Enforces a disciplined workflow for coding, debugging, refactoring, and automation: brainstorm -> plan -> implement with verification (prefer TDD) -> review -> finish. Use for almost any non-trivial change.”.
- **02** When the source has headings, the agent prioritizes “When to use this skill / Activation marker (required) / Default workflow (mandatory unless explicitly unnecessary)” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “When to use this skill / Activation marker (required) / Default workflow (mandatory unless explicitly unnecessary)”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: superpowers-workflow
description: Enforces a disciplined workflow for coding, debugging, refactoring, and automation: brainstorm -…
category: ai
source: anthonylee991/gemini-superpowers-antigravity
---
# superpowers-workflow
## When to use
- Enforces a disciplined workflow for coding, debugging, refactoring, and automation: brainstorm -> plan -> implement wi…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “When to use this skill / Activation marker (required) / Default workflow (mandatory unless explicitly unnecessary)” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "superpowers-workflow" {
input -> user goal + target files + boundaries + acceptance criteria
context -> When to use this skill / Activation marker (required) / Default workflow (mandatory unless explicitly unnecessary)
rules -> SKILL.md triggers / order / output contract
runtime -> Python | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Superpowers Workflow
This skill defines the default operating procedure for software and automation tasks.
When to use this skill
Use whenever the user asks to:
- build or modify code
- debug an error or failing tests
- refactor or improve quality
- design an automation workflow (e.g., API integrations, ETL, pipelines)
- add tests, reliability, or safety checks
Activation marker (required)
Immediately after reading this skill (before any other output), run:
python .agent/skills/superpowers-workflow/scripts/record_activation.py --skill superpowers-workflow
Default workflow (mandatory unless explicitly unnecessary)
- Brainstorm (short): clarify goal, constraints, risks, and acceptance criteria.
- Write a plan: small steps (2–10 minutes each) with files + verification.
- Implement: make the smallest correct change; prefer tests-first when feasible.
- Review pass: correctness, edge cases, security, style, maintainability.
- Finish: run verification commands, summarize changes + next steps.
Decision tree: how much process is needed?
- Tiny change (1 file, obvious):
- Do a mini-brainstorm (3 bullets), then mini-plan (3–5 steps), then implement + verify.
- Non-trivial change:
- Full brainstorm + plan before editing.
- High-risk change (auth, money, prod data, security, migrations):
- Add explicit risk controls: rollback plan, dry-run, extra tests, logging, safe defaults.
Output rules (how you communicate)
- Always state assumptions if anything is ambiguous.
- Always include verification (commands, tests, or observable checks).
- If you must ask questions, ask at most 3; then proceed with best assumptions.
Stop conditions
Pause implementation and switch to planning if:
- requirements conflict
- critical unknowns block correctness
- the change could cause data loss or security issues without safeguards
Decide Fit First
Design Intent
How To Use It
Boundaries And Review