withzombies-hyper

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

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 implementation complete and tests pass - closes bd epic, presents integration options (merge/PR/keep/discard), executes choice

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

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

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

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

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

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

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

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