Decibel Superpowers

Skills

18 in the Claude listing

• brainstormingUse before creative work - creating features, building components, adding functionality.
• Dispatching parallel agentsUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
• Executing plansUse when you have a written implementation plan to execute in a separate session with review checkpoints
• Finishing 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
• Receiving 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
• Requesting code reviewUse when completing tasks, implementing major features, or before merging to verify work meets requirements
• Sentinel driven debuggingUse when debugging in a project with Decibel MCP tools — tracks bugs as sentinel issues with reproduction steps and resolution
• Sentinel driven planningUse when brainstorming or planning work in a project with Decibel MCP tools — creates sentinel issues, ADRs, and epics from design decisions
• Sentinel driven reviewUse when reviewing code in a project with Decibel MCP tools — escalates findings to sentinel issues when they need tracking
• Sentinel project healthUse when verifying work is complete in a Decibel project — checks sentinel for open issues, stale ADRs, and design debt before claiming done
• Subagent driven developmentUse when executing implementation plans with independent tasks in the current session
• Systematic debuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes
• Test driven developmentUse when implementing any feature or bugfix, before writing implementation code
• Using git worktreesUse when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verificat
• Using superpowersUse when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
• Verification 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
• Writing plansUse when you have a spec or requirements for a multi-step task, before touching code
• Writing skillsUse when creating new skills, editing existing skills, or verifying skills work before deployment