superpowers

Name: superpowers
Availability: InStock
Author: tiankong0101-byte

Enforce a spec-first workflow with brainstorming, TDD, debugging, and branch completion.

Updated May 17, 2026

Search Tags:#planning #tdd #code review #debugging #software development #subagents

Ready to run

npx skills add https://github.com/tiankong0101-byte/skills-registry --skill superpowers-tiankong0101-byte

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: superpowers
Source: https://github.com/tiankong0101-byte/skills-registry/tree/main/skills/superpowers
Command: npx skills add https://github.com/tiankong0101-byte/skills-registry --skill superpowers-tiankong0101-byte

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers avoid ad hoc coding by enforcing a structured workflow for planning, building, debugging, and finishing software work with clear guardrails.

Core Features & Use Cases

Spec-first development: Start with brainstorming and design before writing any code.
TDD-driven implementation: Create detailed execution plans and implement tasks by writing failing tests first.
Subagent-based delivery: Coordinate implementation and review through dedicated subagents for more reliable outcomes.
Systematic debugging: Diagnose failures through root-cause analysis instead of quick patches.
Branch completion workflow: Verify tests, then merge, PR, keep, or discard work with a defined closing process.

Quick Start

Use the superpowers skill to help me design, plan, and implement this feature using the required workflow.

Frequently Asked Questions about superpowers

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

FAQPage Schema

How do I enforce a spec-first software development workflow?▼

To enforce spec-first software development, start with brainstorming and design approval before writing code, then proceed through TDD implementation, systematic debugging, and branch finishing. This structured workflow prevents ad hoc coding by requiring design validation upfront.

What is the best way to implement TDD and coordinate subagents for feature delivery?▼

The best way to implement TDD with subagents is to create detailed execution plans and write failing tests first, then spawn dedicated subagents via sessions_spawn to handle implementation and code review. This subagent-based delivery ensures reliable outcomes through coordinated task execution.

How do I debug test failures using root-cause analysis instead of quick patches?▼

Debug test failures through systematic root-cause analysis by diagnosing the underlying failure points rather than applying quick patches. This requires identifying the exact origin of the failure within the spec-first workflow before attempting any code modifications.

Can I use this structured workflow for both bug fixing and feature development?▼

Yes, you can use this structured workflow for both bug fixing and feature development in agent-driven coding sessions. It applies spec-first rigor, TDD implementation, and branch completion processes to any software delivery task, ensuring consistent quality.

How do I complete a branch after verifying tests pass?▼

To complete a branch after tests pass, follow the defined closing process to merge, create a PR, keep, or discard your work. This branch finishing step verifies all tests and ensures the completed code meets the required guardrails before finalizing.