Loading...
Loading...
Found 11 Skills
Invoke IMMEDIATELY via python script when user requests problem analysis or root cause investigation. Do NOT explore first - the script orchestrates the investigation.
Use when you need to analyze Java profiling data collected during the detection phase — including interpreting flamegraphs, memory allocation patterns, CPU hotspots, threading issues, systematic problem categorization, evidence documentation with profiling-problem-analysis and profiling-solutions markdown files, or prioritizing fixes using Impact/Effort scoring. Part of the skills-for-java project
Comprehensive A3 one-page problem analysis with root cause and action plan
Socratic questioning to examine beliefs, uncover assumptions, and develop deeper understanding. Use to challenge thinking, evaluate proposals, or teach without lecturing.
Deep multi-framework reasoning using Gemini. Use for complex problem analysis, challenging ideas, and evaluating multiple options with structured thinking.
문제를 분석하여 Agent Teams를 자동 구성하고, 4가지 조율 패턴(distribute/monitor/discourse/sequence) 중 최적 패턴으로 협업한다. "/teams {문제 설명}"으로 호출한다.
The combined phase of mathematical modeling competition problem analysis and modeling design. It is used to read the problem statement and attachments, and complete sub-problem decomposition, data understanding, hypothesis pre-check, variable definition, model formulas, objective functions, constraint conditions, solution strategies, and a modeling report that can be handed over for code implementation.
Think carefully no matter what question you answer. Before answering any question or performing any task, conduct in-depth analysis and reasoning first.
Comprehensive A3 one-page problem analysis with root cause and action plan
Use when a selective defect needs IS/IS-NOT difference analysis or a consequential option choice needs must/want weighting and adverse-consequence comparison.
Помогает совместно прояснить задачу, проверить идею, найти корневую причину проблемы или выбрать подход без реализации. Используй, когда пользователь просит обсудить задачу, разобраться в проблеме, сравнить варианты или задаёт вопросы «что думаешь?» и «как лучше сделать?». Не используй, когда пользователь явно просит составить план, реализовать задачу, проверить изменения кода или сохранить знания проекта.