Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

$pwd:

superpowers-workflow

Name: Superpowers Workflow
Author: anthonylee991

// 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.

Executar no Manus

$ git log --oneline --stat

stars:770

forks:98

updated:18 de janeiro de 2026 às 22:19

Explorador de arquivos

4 arquivos

SKILL.md

readonly

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)

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

related-skills.json

mesmo repositório

superpowers-brainstorm.md

from "anthonylee991/gemini-superpowers-antigravity"

Produces a structured brainstorm: goals, constraints, risks, options, recommendation, and acceptance criteria. Use before non-trivial implementation or design changes.

2026-01-18770

superpowers-debug.md

from "anthonylee991/gemini-superpowers-antigravity"

Systematic debugging: reproduce, isolate, form hypotheses, instrument, fix, and add regression tests. Use when troubleshooting errors, failing tests, or unexpected behavior.

2026-01-18770

superpowers-finish.md

from "anthonylee991/gemini-superpowers-antigravity"

Finalizes work: runs verification, summarizes changes, notes follow-ups, and ensures repo hygiene. Use at the end of an implementation or debugging session.

2026-01-18770

superpowers-plan.md

from "anthonylee991/gemini-superpowers-antigravity"

Writes an implementation plan with small steps, exact files to touch, and verification commands. Use before making non-trivial changes.

2026-01-18770

superpowers-python-automation.md

from "anthonylee991/gemini-superpowers-antigravity"

Implements reliable automations in Python for REST APIs: httpx/requests patterns, retries, timeouts, pagination, typing, config, logging, and tests. Use when writing Python scripts/services that call external APIs.

2026-01-18770

superpowers-rest-automation.md

from "anthonylee991/gemini-superpowers-antigravity"

Builds reliable automations that integrate with REST APIs: auth, pagination, retries, rate limits, idempotency, webhooks, data mapping, and safe error handling. Use when calling external APIs, syncing systems, or building ETL-style workflows.

2026-01-18770

package.json

"author": "anthonylee991"

"repository": "anthonylee991/gemini-superpowers-antigravity"

Abrir repositório GitHub Ver repositórios do creator

$ install --global

$ download --local

Executar no Manus

$ useful --forSOC

Desenvolvedores de softwareInformática e Matemática15-1252L4

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)

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

superpowers-workflow

Superpowers Workflow

When to use this skill

Activation marker (required)

Default workflow (mandatory unless explicitly unnecessary)

Decision tree: how much process is needed?

Output rules (how you communicate)

Stop conditions

Mais deste repositório

Mais deste repositório

Superpowers Workflow

When to use this skill

Activation marker (required)

Default workflow (mandatory unless explicitly unnecessary)

Decision tree: how much process is needed?

Output rules (how you communicate)

Stop conditions