Back to list
anthonylee991

superpowers-workflow

by anthonylee991

Superpowers for Gemini's Antigravity (like Claude Superpowers)

348🍴 39📅 Jan 23, 2026

SKILL.md


name: superpowers-workflow description: 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.

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

Score

Total Score

70/100

Based on repository quality metrics

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

+10
説明文

100文字以上の説明がある

0/10
人気

GitHub Stars 100以上

+5
最近の活動

3ヶ月以内に更新

+5
フォーク

10回以上フォークされている

+5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

0/5

Reviews

💬

Reviews coming soon