bug-hunt
Systematically debug issues using Sherpa's Bug Hunt workflow. Activates when fixing bugs, investigating errors, debugging broken functionality, or handling regressions. Prevents symptom-fixing by enforcing reproduction-first approach.
systematic-development
Use Sherpa's systematic development workflow for general coding tasks. Activates when starting development work, adding features, or implementing functionality. Ensures guide check before coding and guide done after completion for progress tracking and celebrations.
tdd-cycle
Follow strict TDD methodology using Sherpa's workflow enforcement. Activates when implementing new features, adding functionality, or building code that requires tests. Ensures RED-GREEN-REFACTOR discipline with guide check/done tracking.
logic-flow
Explain the logic flow of a function step-by-step by analyzing its implementation and call graph. Use when the user asks "how does this function work", "walk me through this", "step through this code", or wants to understand the control flow and decision points in a function.
call-trace
Trace the call path between two functions by iteratively following callers/callees using deep_dive and fast_refs. Use when the user asks how function A reaches function B, wants to see the connection between two symbols, or asks "what calls what" between two points in the code.
dependency-graph
Show module dependencies by analyzing imports, exports, and cross-references between files. Use when the user asks what a file imports, what depends on a module, how modules are coupled, or wants to understand the dependency structure of any part of the codebase.
explore-area
Orient on a new area of the codebase using get_context for token-budgeted exploration with pivots and neighbors. Use when the user asks "what does this module do", "I'm new to this code", "explain this part of the codebase", or wants to understand an unfamiliar area before making changes.
impact-analysis
Analyze what would break if a symbol is changed — finds all callers, groups by risk level, and assesses change impact. Use when the user asks about the blast radius of a change, wants to know who uses a symbol, or is planning a refactor and needs to understand downstream effects.
search-debug
Diagnose why a search returns unexpected results — analyze scoring factors, tokenization, and index health for dogfooding Julie's search quality. Use when a Julie search misses an expected symbol, returns wrong results, ranks something surprisingly low, or when investigating search quality issues during development.
type-flow
Trace how types flow through a function — parameters, transformations, and return types. Use when the user asks what types a function accepts or returns, how data transforms through a pipeline, or wants to understand type conversions in a code path.