Labsco
obra logo

superpowers

247,050

Claude Code plugin · obra/superpowers · MIT

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

14 skills · hooks — installs as one unit

⌁ skills (14)

brainstorming

🔥🔥🔥🔥✓ Verified

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Full instructions & audit →

dispatching-parallel-agents

🔥🔥🔥🔥✓ Verified

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

Full instructions & audit →

executing-plans

🔥🔥🔥🔥✓ Verified

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

Full instructions & audit →

finishing-a-development-branch

🔥🔥🔥🔥✓ Verified

Use 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

Full instructions & audit →

receiving-code-review

🔥🔥🔥🔥✓ Verified

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

Full instructions & audit →

requesting-code-review

🔥🔥🔥🔥✓ Verified

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

Full instructions & audit →

subagent-driven-development

🔥🔥🔥🔥✓ Verified

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

Full instructions & audit →

systematic-debugging

🔥🔥🔥🔥🔥✓ Verified

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

Full instructions & audit →

test-driven-development

🔥🔥🔥🔥✓ Verified

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

Full instructions & audit →

using-git-worktrees

🔥🔥🔥🔥✓ Verified

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

Full instructions & audit →

using-superpowers

🔥🔥🔥✓ Verified

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

Full instructions & audit →

verification-before-completion

🔥🔥🔥🔥✓ Verified

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

Full instructions & audit →

writing-plans

🔥🔥🔥🔥✓ Verified

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

Full instructions & audit →

writing-skills

🔥🔥🔥🔥✓ Verified

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

Full instructions & audit →

⌁ also included

  • Hooks — automations that run on events (e.g. before/after every edit or commit)