superpowers

Skills (18)

• code-reviewer

  49 lines542 words

  |

• IDE / Platform Support Request

  24 lines112 words
• Bug Report

  53 lines235 words
• Feature Request

  35 lines188 words
• using-git-worktrees

  219 lines784 words10 blocks

  Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees w...

  bash
• dispatching-parallel-agents

  183 lines923 words4 blocks

  Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

  dotmarkdowntypescript
• receiving-code-review

  214 lines929 words12 blocks

  Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires ...

• using-superpowers

  116 lines760 words1 blocks

  Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying ...

  dot
• brainstorming

  165 lines1553 words1 blocks

  "You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user inten...

  dot
• writing-plans

  153 lines914 words5 blocks

  Use when you have a spec or requirements for a multi-step task, before touching code

  bashmarkdownpython
• finishing-a-development-branch

  201 lines679 words10 blocks

  Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by prese...

  bash
• writing-skills

  656 lines3212 words21 blocks

  Use when creating new skills, editing existing skills, or verifying skills work before deployment

  bashdotmarkdownyaml
• systematic-debugging

  297 lines1504 words3 blocks

  Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

  bash
• test-driven-development

  372 lines1496 words13 blocks

  Use when implementing any feature or bugfix, before writing implementation code

  bashdottypescript
• requesting-code-review

  106 lines400 words2 blocks

  Use when completing tasks, implementing major features, or before merging to verify work meets requirements

  bash
• executing-plans

  71 lines360 words

  Use when you have a written implementation plan to execute in a separate session with review checkpoints

• subagent-driven-development

  278 lines1528 words3 blocks

  Use when executing implementation plans with independent tasks in the current session

  dot
• verification-before-completion

  140 lines668 words7 blocks

  Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming...