superpowers-coding

Enforce TDD, root-cause debugging, Git worktrees, and subagent-driven development workflows.

37|12|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/exiao/skills --skill superpowers-coding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: superpowers-coding
Source: https://github.com/exiao/skills/tree/main/superpowers-coding
Command: npx skills add https://github.com/exiao/skills --skill superpowers-coding

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive framework for writing high-quality code, ensuring reliability through Test-Driven Development (TDD), efficient debugging, and streamlined workflow management with Git worktrees and subagent-driven development.

Core Features & Use Cases

  • Test-Driven Development (TDD): Enforces writing failing tests before production code, ensuring robust and verifiable features.
  • Systematic Debugging: Guides users through a structured process to find and fix bugs by identifying root causes, not just symptoms.
  • Git Worktrees: Facilitates working on multiple branches simultaneously in isolated environments.
  • Subagent-Driven Development: Orchestrates development tasks using specialized subagents for implementation and review, ensuring spec compliance and code quality.
  • Use Case: When starting a new feature, you'll use TDD to write tests first. If a bug arises, you'll follow the systematic debugging process to find the root cause. For concurrent work, you'll set up Git worktrees, and for complex tasks, you'll leverage subagents for implementation and review.

Quick Start

Use the superpowers-coding skill to begin implementing a new feature by writing a failing test first.

Frequently Asked Questions about superpowers-coding

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

FAQPage Schema
How do I start Test-Driven Development (TDD) when implementing a new feature?

To start Test-Driven Development (TDD), write a failing test first before writing any production code to ensure the feature is verifiable. This structured process provides guardrails for robust software development.

What is the best way to find the root cause of a bug during debugging?

The best way to find the root cause during debugging is to follow a structured process that identifies the origin rather than just treating symptoms. This systematic approach ensures reliable bug resolution.

How do I manage parallel development across multiple Git branches?

Manage parallel development across multiple Git branches by using Git worktrees to work in isolated environments simultaneously. This streamlines workflow management for concurrent feature development.

Can I use subagents to review code for spec compliance?

Yes, you can use subagent-driven development to orchestrate tasks for implementation and review, ensuring spec compliance and code quality. Specialized subagents handle the structured review process.

Does this development workflow require any specific external dependencies?

No, this development workflow requires no external dependencies to enforce rigorous practices. It provides structured processes and guardrails for TDD, debugging, and Git worktree management natively.

When should I use a systematic debugging process instead of patching symptoms?

You should use a systematic debugging process whenever a bug arises to ensure you are fixing the actual issue. Patching symptoms often leads to recurring errors and unresolved root causes.