research-synthesize
Use when user says "research", "find out about", "what do sources say", "gather information on", "learn about", "investigate", or needs to gather and combine information from multiple sources for technical research, market analysis, or learning new topics.
compare-options
Use when user says "compare X vs Y", "which should I use", "pros and cons", "what's the difference between", "A or B", "help me choose", "tradeoffs", "what are the tradeoffs", or needs to compare tools, libraries, approaches, or architectures with tradeoffs clearly presented.
summarize-efficiently
Use when user says "summarize", "tl;dr", "key points", "give me the gist", "what's important here", "condense this", "brief overview", or needs to compress documents, conversations, PRs, articles, meeting notes, or codebases while preserving key information.
explain-step-by-step
Use when user asks to "explain", "walk through", "break down", "help me understand", or needs to understand something complex progressively. Works for any domain — PR changes, code, documents, concepts, processes, architectures. Also triggers on "explain this PR", "walk me through", "break down these changes", "step by step", "what does this do". For "break down" into actionable work items with dependencies, use decompose-problem instead.
root-cause-analysis
Use when user says "why does this happen", "find the root cause", "diagnose", "keeps happening", "what's causing", "5 whys", "get to the bottom of", or needs to find underlying causes for bugs, performance issues, process failures, or system outages.
evolve
Use when user says "/evolve", "manage my toolkit", "initialize toolkit", "release my changes", "switch toolkits", "toolkit status", "setup my toolkit", "sync my setup", or asks about toolkit management and cross-machine synchronization.
workflow
This skill should be used when the user says "/workflow", "what phase am I on", "show my workflow", "workflow status", "next phase", "skip phase", "workflow done", "switch workflow", "what's my current phase", "advance phase", "how is my project going", "where am I", "what should I do next", "what's left to do", "what phase is next", "track my progress", "check progress", "mark this phase done", "move to the next step", "expand this phase", "break this down into sub-tasks", "let's start over", "change direction", "pivot". Manages ACTIVE multi-phase workflows using native Claude Code tasks. To get a workflow RECOMMENDATION for a new task, use prepare-task instead.
decompose-problem
Use when user says "break this down", "where do I start", "this is overwhelming", "too big", "decompose", "chunk this", "step by step plan", or faces a complex problem needing breakdown into manageable pieces with dependencies and order identified. Do NOT use for new project setup — use build-project skill instead. For "break down" to understand/explain something, use explain-step-by-step instead.
setup-audit
Use when user says "audit my setup", "review configuration", "apply learnings", "optimize Claude Code setup", "check security settings", "check my config", "is my setup secure", "what agents do I have", "review my agents", "check my skills", "consolidate my toolkit", "migrate", "import from .claude", or "/evolve audit". Also use for maintenance or after major projects.
verify-completion
Use when user says "am I done", "before I commit", "final check", "did I miss anything", "ready to ship", "sanity check", "verify complete", or before claiming work is done to systematically check requirements, edge cases, and cleanup.
prepare-task
Use when user says "/evolve prepare", "prepare toolkit", "check toolkit gaps", "do I have the right agents", "what tools do I need", "analyze my toolkit", "what workflow should I follow", or before complex tasks that might need specialized agents, skills, or workflow guidance. To manage an ACTIVE workflow (advance, skip, check status), use the workflow skill instead.
build-project
This skill should be used when the user says "let's build", "build this project", "build me", "build a", "create this", "implement this", "make this", "make me a", "develop this", "let's make", "start building", "build it", "create it", "let's create", "let's implement", "new project", "new feature", "help me create", "start a new", "from scratch", "greenfield", "scaffold", "bootstrap", "set up a new", "initialize", "I want to build", "I want to create", "I want to make", or initiates any new development task. Provides STRUCTURED requirements gathering using native AskUserQuestion UI with adaptive, depth-aware elicitation. Works for any domain — code, writing, research, design, ops. Gathers goal through interactive questions, then runs an adaptive elicitation loop that derives questions from context (not templates). Creates an implementation doc, then hands off to /workflow for phase guidance.
learn
Use when user says "extract learnings", "save what we learned", "capture insights", "remember this", "remember this for next time", "document this pattern", "what did we learn", "save this approach", "save this pattern", or "/learn". Use after debugging sessions, problem-solving, or when valuable patterns are discovered.