hyperpowers

Use when shaping a feature before implementation - turns rough ideas into an approved markdown spec and local task directory

Use to execute an approved local markdown task directory iteratively - work the current Now slice, update docs, then stop

Use when implementation is complete and verified - delete finished local task docs, present integration options, and clean up safely

Use for advanced markdown task-doc operations - split work, reprioritize slices, delete finished local task dirs, and keep docs clean

Use after executing a task directory - verifies implementation against plan.md, acceptance checks, and anti-goals

Use when starting any conversation - establishes skill selection and the local task-doc workflow

Use before claiming work complete, fixed, or passing - requires fresh evidence before any completion claim

Use after a spec is approved - distills plan.md into context.md and a rolling markdown backlog

Use when shaping a feature before implementation - turns rough ideas into an approved markdown spec and local task directory

Use to execute an approved local markdown task directory iteratively - work the current Now slice, update docs, then stop

Use when implementation is complete and verified - delete finished local task docs, present integration options, and clean up safely

Use for advanced markdown task-doc operations - split work, reprioritize slices, delete finished local task dirs, and keep docs clean

Use after executing a task directory - verifies implementation against plan.md, acceptance checks, and anti-goals

Use when starting any conversation - establishes skill selection and the local task-doc workflow

Use before claiming work complete, fixed, or passing - requires fresh evidence before any completion claim

Use after a spec is approved - distills plan.md into context.md and a rolling markdown backlog

Use to audit test quality with SRE scrutiny - identifies weak tests, missing cases, and creates task docs for improvements

Use when encountering bugs or test failures - systematic debugging using debuggers, internet research, and agents to find root cause before fixing

Use when encountering a bug - reproduce it, track it in task docs, fix it with a regression test, and verify the result

Use when refactoring code - tracks the refactor in task docs and preserves behavior through small verified changes

Use when hardening a spec or task docs - stress-tests edge cases, failure modes, and acceptance checks before implementation

Use when implementing features or fixing bugs - enforces RED-GREEN-REFACTOR cycle requiring tests to fail before writing code

Use when creating new skills, editing existing skills, or verifying skills work - applies TDD to documentation by testing with subagents before writing

Use to audit test quality with SRE scrutiny - identifies weak tests, missing cases, and creates task docs for improvements

Use when encountering bugs or test failures - systematic debugging using debuggers, internet research, and agents to find root cause before fixing

Use when encountering a bug - reproduce it, track it in task docs, fix it with a regression test, and verify the result

Use when refactoring code - tracks the refactor in task docs and preserves behavior through small verified changes

Use when hardening a spec or task docs - stress-tests edge cases, failure modes, and acceptance checks before implementation

Use when implementing features or fixing bugs - enforces RED-GREEN-REFACTOR cycle requiring tests to fail before writing code

Use when creating new skills, editing existing skills, or verifying skills work - applies TDD to documentation by testing with subagents before writing

Use when designing a refactor after diagnosis - selects patterns, defines composition and DI seams, and produces a test-ready refactor design spec

Use when identifying bad code/design and selecting refactor targets - produces a diagnosis report with smells, risks, and refactor vs rewrite decision

Use when facing 3+ independent failures that can be investigated without shared state or dependencies - dispatches multiple agents to investigate and fix independent problems concurrently

Use when you want to spawn a specialized subagent using the standard Hyperpowers agent prompts (test-runner, code-reviewer, codebase-investigator, internet-researcher, test-effectiveness-analyst).

Use when errors occur deep in execution - traces bugs backward through call stack to find original trigger, not just symptom

Use when writing or changing tests, adding mocks - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies

Use when creating Claude Code hooks - covers hook patterns, composition, testing, progressive enhancement from simple to advanced

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

Use when errors occur deep in execution - traces bugs backward through call stack to find original trigger, not just symptom

Use when skills aren't activating reliably - covers official solutions (better descriptions) and custom hook system for deterministic skill activation