메뉴
Use when user reports an error, bug, or something not working. Search-first troubleshooting with diagnostic phase. Triggers: debug, error, broken, not working, failing, crash, exception.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Diagnose an agent FAILURE and prescribe the cheapest/earliest guardrail to add NEXT — then scaffold it ready to paste. Craft-on-the-fly, friction-driven, minimal: grow a harness to fit the real failure mode instead of designing one upfront. Sibling of /pick-model (picks the model) and /pick-workflow (picks the topology); this picks the GUARDRAIL. Domain-general — any agentic task, not just code. Use when 'agent keeps failing at X', 'it hallucinated/broke the contract/wasted tokens', 'what guardrail do I add', 'harness for X', 'how do I stop it doing Y', or when starting a new agentic task and you want a minimal starter harness. Recommends + scaffolds; does NOT run the task.
Resume session from CONTEXT-llm.md. Use when resuming work, loading saved context, continuing a previous session. Triggers include "load context", "resume session", "continue where I left off".
Decide HOW work should EXECUTE — linear vs parallel fan-out, sub-agents vs teams vs dynamic Workflow, and the per-step seam — instead of defaulting to linear+single-model. Produces an execution design, does NOT run the task. Delegates the per-step model+effort call to a model-picker skill when the environment has one. Use when authoring/challenging a skill or agent, AND mid-task when deciding how to run real work — 'should I fan this out', 'should this fan out', 'parallel or linear', 'sub-agents or workflow', 'per-step seam', 'execution topology', 'execution architecture'. For a trivial few-item call, early-exit to linear cheaply rather than a full analysis.
Save session to CONTEXT-llm.md with conversation summary. Use when saving work, checkpointing progress, preserving session state. Triggers include "save context", "save session", "checkpoint", "save my progress".
Challenge, push back, play devil's advocate on AI output or intentions. Use when: challenge this, are you sure, push back, prove it, what if you're wrong, devil's advocate, stress test, poke holes, second opinion, sanity check, too confident, really?, question this decision, avant de commencer, je veux faire X, aide-moi à décider. Modes: route (default — any invocation whose first word isn't a recognized subcommand, including a free-text description), forward (before starting), anchor (committed too fast), verify (facts wrong?), framing (wrong problem?), deep (full devil's advocate in fresh context).
Capture a session's verbatim "meat" — the exact phrasing of constraints, rejected paths, corrections, live reasoning, learnings, pivots, open questions — into CHECKPOINT-*-llm.md, plus a synthesized summary of state. Use before /clear on a long reasoning session, when exact wording matters, or when saving a session you'll resume cold. Triggers: "checkpoint", "save the meat", "capture verbatim", "checkpoint before clear".
| name | troubleshoot |
| description | Use when user reports an error, bug, or something not working. Search-first troubleshooting with diagnostic phase. Triggers: debug, error, broken, not working, failing, crash, exception. |
| allowed-tools | WebSearch, WebFetch, AskUserQuestion, Read, Glob, Grep |
| model | opus |
| context | main |
| argument-hint | <error or symptom description> |
| cynefin-domain | complicated |
| cynefin-verb | analyze |
Search-first diagnostic workflow. Human executes commands.
CRITICAL: After EVERY AskUserQuestion call, check if answers are empty/blank. Known Claude Code bug: outside Plan Mode, AskUserQuestion silently returns empty answers without showing UI.
If answers are empty: DO NOT proceed with assumptions. Instead:
0.Load → 1.Search → 2.Qualify → 3.Diagnose → 4.Investigate → 5.Persist → 6.Learn
Read $PRAXIS_DIR/reference/troubleshoot/learnings.yaml if exists. Apply known patterns before searching.
80% of bugs solved online.
[error] [stack] [framework] on SO, GitHub, Docs, RedditAskUserQuestion:
See protocols/diagnose.md for details.
Pattern matches → suggest fix, skip OODA
Only if diagnosis inconclusive.
Exit when root cause confirmed and fix verified.
MUST execute after root cause confirmed and fix verified. DO NOT skip. DO NOT wait for user to ask.
Persist the diagnostic session to $PRAXIS_DIR/thinking/troubleshoot/{project}/{date}-{slug}-llm.md.
{project} = current project folder name. {slug} = lowercase hyphenated from primary symptom/error. Create directory if missing.
Collision handling: If filename exists, append sequence: {date}-{slug}-2-llm.md, {date}-{slug}-3-llm.md. First write gets clean name.
Guard: If $PRAXIS_DIR is unset, skip artifact persistence silently (troubleshooting must not fail because of missing env var).
Content (required sections):
This is the active thinking trail — distinct from learnings.yaml which captures distilled, reusable conclusions.
After resolution, AskUserQuestion: "Save this learning?"
$PRAXIS_DIR/reference/troubleshoot/learnings.yamlscope: project:<name>Before responding to user, verify:
$PRAXIS_DIR/thinking (or guard triggered if unset)protocols/diagnose.md - Mental models, bisect strategies