superpowers-suite

Applies structured workflow guidance for brainstorming, planning, debugging, TDD, and verification.

Updated May 29, 2026
One-click install
npx skills add https://github.com/RatnaAtika/Indonesian-ASR-11-Class-Dataset --skill superpowers-suite-ratnaatika
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: superpowers-suite
Source: https://github.com/RatnaAtika/Indonesian-ASR-11-Class-Dataset/tree/main/.agents/skills/superpowers-suite
Command: npx skills add https://github.com/RatnaAtika/Indonesian-ASR-11-Class-Dataset --skill superpowers-suite-ratnaatika

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Ad-hoc prompting often leads to unstructured, unverified work on software tasks. This Skill provides a decision framework that routes each repository task to the right disciplined process, from brainstorming through verification. ## Core Features & Use Cases - Task Classification: Reads the current repository and classifies the task to select the smallest useful process skill, such as brainstorming, writing-plans, or systematic-debugging. - Process Routing: Directs work to test-driven-development for risky behavior, verification-before-completion before commits, and subagent or parallel-agent dispatch for decomposable work. - Guardrails: Keeps local project conventions ahead of generic guidance and avoids process overhead on tiny, self-evident fixes. - Use Case: When a bug appears in a repository, the Skill routes the work to systematic-debugging, then requires verification-before-completion before any commit or handoff. ## Quick Start Ask the assistant to apply the Superpowers workflow to classify the current repository task and pick the right process skill before making changes.

Frequently Asked Questions about superpowers-suite

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose the right process for a coding task?

Classify the task first: use brainstorming for feature changes, writing-plans for multi-step implementation, systematic-debugging for bugs, and test-driven-development for risky new behavior. Pick the smallest useful process rather than applying everything.

When should I use test-driven development on a task?

Use test-driven-development for risky new behavior where regressions are likely. The Skill routes such tasks to TDD and requires verification-before-completion before any commit, push, or handoff.

Can this workflow be used with git worktrees and parallel agents?

Yes. The Skill routes work to dispatching-parallel-agents when tasks split cleanly, and to using-git-worktrees when isolation reduces collision risk between concurrent changes.

When should I skip structured process guidance?

Skip process overhead for tiny, self-evident fixes. The guardrails explicitly say not to force workflow discipline onto trivial changes, but never skip verification when behavior, data flow, or publish steps are affected.

Does this workflow override my project's existing conventions?

No. Local project rules take priority over generic workflow guidance. The Skill applies its process discipline only where it adds structure beyond the repository's own conventions.