Planning, TDD, and debugging
Use Superpowers to guide agent work through brainstorming, implementation planning, test-driven development, systematic debugging, parallel execution, code review, and finish-the-branch workflows.
Skills 15 in the ChatGPT listing
Brainstorming You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). Diagnosing Superpowers Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. Dispatching Parallel Agents Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies Executing Plans Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available Finishing a Development Branch Use when implementation is complete, all tests pass, and you need to decide how to integrate the work Receiving Code Review Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation Requesting Code Review Use when completing tasks, implementing major features, or before merging to verify work meets requirements Subagent-Driven Development Use when executing implementation plans with independent tasks in the current session Systematic Debugging Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes Test-Driven Development Use when implementing any feature or bugfix, before writing implementation code Using Git Worktrees Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback Using Superpowers Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions Verification Before Completion Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always Writing Plans Use when you have a spec or requirements for a multi-step task, before touching code Writing Skills Use when creating new skills, editing existing skills, or verifying skills work before deployment