executing-plans
Use to execute bd tasks iteratively - executes one task, reviews learnings, creates/refines next task, then STOPS for user review before continuing
managing-bd-tasks
Use for advanced bd operations - splitting tasks mid-flight, merging duplicates, changing dependencies, archiving epics, querying metrics, cross-epic dependencies
building-hooks
Use when creating Claude Code hooks - covers hook patterns, composition, testing, progressive enhancement from simple to advanced
using-hyper
Use when starting any conversation - establishes mandatory workflows for finding and using skills
brainstorming
Use when creating or developing anything, before writing code - refines rough ideas into bd epics with immutable requirements
sre-task-refinement
Use when you have to refine subtasks into actionable plans ensuring that all corner cases are handled and we understand all the requirements.
analyzing-test-effectiveness
Use to audit test quality with Google Fellow SRE scrutiny - identifies tautological tests, coverage gaming, weak assertions, missing corner cases. Creates bd epic with tasks for improvements, then runs SRE task refinement on each.
debugging-with-tools
Use when encountering bugs or test failures - systematic debugging using debuggers, internet research, and agents to find root cause before fixing
dispatching-parallel-agents
Use when facing 3+ independent failures that can be investigated without shared state or dependencies - dispatches multiple Claude agents to investigate and fix independent problems concurrently
finishing-a-development-branch
Use when implementation complete and tests pass - closes bd epic, presents integration options (merge/PR/keep/discard), executes choice
fixing-bugs
Use when encountering a bug - complete workflow from discovery through debugging, bd issue, test-driven fix, verification, and closure
refactoring-design
Use when designing a refactor after diagnosis - selects patterns, defines composition and DI seams, and produces a test-ready refactor design spec
refactoring-diagnosis
Use when identifying bad code/design and selecting refactor targets - produces a diagnosis report with smells, risks, and refactor vs rewrite decision
refactoring-safely
Use when refactoring code - test-preserving transformations in small steps, running tests between each change
review-implementation
Use after hyperpowers:executing-plans completes all tasks - verifies implementation against bd spec, all success criteria met, anti-patterns avoided
root-cause-tracing
Use when errors occur deep in execution - traces bugs backward through call stack to find original trigger, not just symptom
skills-auto-activation
Use when skills aren't activating reliably - covers official solutions (better descriptions) and custom hook system for deterministic skill activation
test-driven-development
Use when implementing features or fixing bugs - enforces RED-GREEN-REFACTOR cycle requiring tests to fail before writing code
testing-anti-patterns
Use when writing or changing tests, adding mocks - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies
verification-before-completion
Use before claiming work complete, fixed, or passing - requires running verification commands and confirming output; evidence before assertions always
writing-plans
Use to expand bd tasks with detailed implementation steps - adds exact file paths, complete code, verification commands assuming zero context
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work - applies TDD to documentation by testing with subagents before writing