Directory
‹ Back to apps

Superpowers

Core skills library: TDD, debugging, collaboration patterns, and proven techniques

What’s inside

14 skills
  • SkillbrainstormingYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
  • Skilldispatching-parallel-agentsUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
  • Skillexecuting-plansUse when you have a written implementation plan to execute in a separate session with review checkpoints
  • Skillfinishing-a-development-branchUse when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
  • Skillreceiving-code-reviewUse 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
  • Skillrequesting-code-reviewUse when completing tasks, implementing major features, or before merging to verify work meets requirements
  • Skillsubagent-driven-developmentUse when executing implementation plans with independent tasks in the current session
  • Skillsystematic-debuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes
  • Skilltest-driven-developmentUse when implementing any feature or bugfix, before writing implementation code
  • Skillusing-git-worktreesUse 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
  • Skillusing-superpowersUse when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
  • Skillverification-before-completionUse 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
  • Skillwriting-plansUse when you have a spec or requirements for a multi-step task, before touching code
  • Skillwriting-skillsUse when creating new skills, editing existing skills, or verifying skills work before deployment