Loading...
Loading...
Found 17 Skills
Improve activation, retention, and engagement through hypothesis-driven growth experiments.
Systematic debugging methodology — binary search isolation, hypothesis-driven debugging, reproducing issues, and root cause analysis. Use when debugging errors, unexpected behavior, or test failures.
Core consulting thinking frameworks and methodologies for structuring business problems, communicating findings, analyzing strategy, building financial models, and designing operations. Use when any agent or command needs to apply MECE decomposition, pyramid principle, hypothesis-driven analysis, issue trees, SCR communication, Porter's Five Forces, TAM/SAM/SOM market sizing, value chain analysis, NPV/IRR decision criteria, build/buy/partner evaluation, RACI matrices, or any standard consulting framework. This skill provides procedural guidance — not just framework names, but how to apply them correctly.
This skill should be used when the user's request or requirement is ambiguous and needs iterative questioning to become actionable. Trigger on "clarify requirements", "refine requirements", "요구사항 명확히", "요구사항 정리", "뭘 원하는 건지", "make this clearer", "spec this out", "scope this", "/clarify". Turns vague inputs into concrete specs. For strategy blind spots use unknown; for content-vs-form reframing use metamedium.
Methodology for debugging non-trivial problems systematically. This skill should be used automatically when investigating bugs, test failures, or unexpected behavior that isn't immediately obvious. Emphasizes hypothesis formation, parallel investigation with subagents, and avoiding common anti-patterns like jumping to conclusions or weakening tests.