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.
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.
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.
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.
Prepare Task
|
Workflow
|
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.
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.
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.
Build Project
|
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 d…
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.