金色时刻 · 15:48
让好资源,触手可及
AGENT SKILL

superpowers-workflow

superpowers-workflow 是面向测试与安全、效率工具、开发运维的 Agent Skill,来自 anthonylee991/gemini-superpowers-antigravity。查看技能说明、操作步骤与使用约定,并通过原项目了解详细用法。

SKILL.md

下载 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

来源:anthonylee991/gemini-superpowers-antigravity · MIT 许可 · 许可原文 · MD 为来源页保存的历史版本