superpowers workflow

AI Community

Skill notes

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)

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):

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.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
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
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Author source file SKILL.md

# 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)
1. **Brainstorm (short)**: clarify goal, constraints, risks, and acceptance criteria.
2. **Write a plan**: small steps (2–10 minutes each) with files + verification.
3. **Implement**: make the smallest correct change; prefer tests-first when feasible.
4. **Review pass**: correctness, edge cases, security, style, maintainability.
5. **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

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.