root-cause-tracing

59

withzombies

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

sre-task-refinement

59

withzombies

Use when you have to refine subtasks into actionable plans ensuring that all corner cases are handled and we understand all the requirements.

managing-bd-tasks

59

withzombies

Use for advanced bd operations - splitting tasks mid-flight, merging duplicates, changing dependencies, archiving epics, querying metrics, cross-epic dependencies

debugging-with-tools

59

withzombies

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

refactoring-safely

59

withzombies

Use when refactoring code - test-preserving transformations in small steps, running tests between each change

using-hyper

59

withzombies

Use when starting any conversation - establishes mandatory workflows for finding and using skills

review-implementation

59

withzombies

Use after hyperpowers:executing-plans completes all tasks - verifies implementation against bd spec, all success criteria met, anti-patterns avoided

test-driven-development

59

withzombies

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

brainstorming

59

withzombies

Use when creating or developing anything, before writing code - refines rough ideas into bd epics with immutable requirements

verification-before-completion

59

withzombies

Use before claiming work complete, fixed, or passing - requires running verification commands and confirming output; evidence before assertions always

testing-anti-patterns

59

withzombies

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

writing-plans

59

withzombies

Use to expand bd tasks with detailed implementation steps - adds exact file paths, complete code, verification commands assuming zero context

executing-plans

59

withzombies

Use to execute bd tasks iteratively - executes one task, reviews learnings, creates/refines next task, then STOPS for user review before continuing

writing-skills

59

withzombies

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

fixing-bugs

59

withzombies

Use when encountering a bug - complete workflow from discovery through debugging, bd issue, test-driven fix, verification, and closure

building-hooks

59

withzombies

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

dispatching-parallel-agents

59

withzombies

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

finishing-a-development-branch

59

withzombies

Use when implementation complete and tests pass - closes bd epic, presents integration options (merge/PR/keep/discard), executes choice

skills-auto-activation

59

withzombies

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

analyzing-test-effectiveness

59

withzombies

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.