Use for open-ended brainstorming, ideation, strategy, or tradeoff analysis. Do not use for implementation plans for code, packages, features, migrations, or refactors; use the plan skill instead.
Use when the user asks for an implementation plan for a package, feature, migration, or refactor. Research the relevant code and produce one concrete, execution-ready plan.
Syntax-aware code search and refactoring with ast-grep. Use for precise structural follow-up after broad discovery, or when the user asks for a specific code shape/codemod such as function calls, imports, hooks, JSX, Lua API calls, or API migrations. Do not use as the first pass for broad inventories, plain text, docs, configs, logs, or fuzzy discovery.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".