executing-plans
Use to execute an approved local markdown task directory iteratively - work the current Now slice, update docs, then stop
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 skill selection and the local task-doc workflow
brainstorming
Use when shaping a feature before implementation - turns rough ideas into an approved markdown spec and local task directory
sre-task-refinement
Use when hardening a spec or task docs - stress-tests edge cases, failure modes, and acceptance checks before implementation
analyzing-test-effectiveness
Use to audit test quality with SRE scrutiny - identifies weak tests, missing cases, and creates task docs for improvements
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work - applies TDD to documentation by testing with subagents before writing
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 is complete and verified - delete finished local task docs, present integration options, and clean up safely
fixing-bugs
Use when encountering a bug - reproduce it, track it in task docs, fix it with a regression test, and verify the result
managing-task-docs
Use for advanced markdown task-doc operations - split work, reprioritize slices, delete finished local task dirs, and keep docs clean
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 - tracks the refactor in task docs and preserves behavior through small verified changes
review-implementation
Use after executing a task directory - verifies implementation against plan.md, acceptance checks, and anti-goals
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 fresh evidence before any completion claim
writing-plans
Use after a spec is approved - distills plan.md into context.md and a rolling markdown backlog