메뉴
Investigate why a worker task is failing repeatedly. Analyze validation reports and worker logs to determine root cause, decide whether to retry with a different approach or escalate to human. Use after 3+ consecutive failures on the same goal.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
The SOLE WRITER to the V3.0 mem0 second brain. Invoked agentically by the executive at write moments — post-run, post-retro, post-spec-merge, manual /harvest. Decides which facts to classify into which memory type (principle/semantic/procedural/episodic/reflective), validates against the schema, and calls the deterministic plumbing in references/ via Bash. Blocks until writes are durable (poll event endpoint for SUCCEEDED). Never invoked from worker code.
Consult the V3.0 mem0 second brain agentically during executive planning, work selection, pre-spawn memory pack building, and failure diagnosis. Use this skill whenever the executive needs to remember prior runs, retros, or learned principles. Read-only — never writes. Drives the unified `mem0` CLI via Bash, orchestrating multiple iterative search queries (mem0 does not do multi-hop graph traversal natively, so iterative search IS the multi-hop).
Hook D — Failure-Diagnosis memory consultation. Runs at executive Phase 7 (after 3+ consecutive failures on a work item) BEFORE the failure-diagnosis skill itself runs. Consults the second brain for similar prior failures and successful retry strategies, then hands enriched context to the failure-diagnosis skill. Read-only. Invokes the memory-reader skill.
Hook E — Post-Retrospective Harvest. Runs after a retrospective markdown doc completes (per-run or weekly). Reads the retro fully and decides which durable lessons (reflective, semantic, procedural memories) to write to the second brain. Typically 3–8 writes per weekly retro, 0–3 per per-run retro. Invokes the memory-harvester skill for the actual writes.
Hook C — Post-Run Harvest. Runs after a worker completes (executive Phase 6 success path). Decides agentically which facts from the run to write to the second brain — typically 0–3 memory writes per run (one episodic, optionally a semantic or procedural). Invokes the memory-harvester skill to do the actual writes (with event-polling for durability).
Hook B — Pre-Spawn Memory Pack build. Runs before each worker spawn (executive Phase 4 prep). Reads the second brain for project-specific memories and produces a Memory Pack markdown block that worker-spawner injects into the worker's generated CLAUDE.md. Workers consume this as static markdown — they never call mem0 themselves. Read-only. Invokes the memory-reader skill.
| name | failure-diagnosis |
| description | Investigate why a worker task is failing repeatedly. Analyze validation reports and worker logs to determine root cause, decide whether to retry with a different approach or escalate to human. Use after 3+ consecutive failures on the same goal. |
You are a diagnostic agent investigating why a task is failing repeatedly.
Analyze why this task keeps failing and determine:
{{VALIDATION_REPORTS}}
{{WORKER_LOGS}}
Respond with ONLY a JSON object (no markdown, no code blocks):
{"rootCause": "Brief description of why it's failing", "shouldRetry": true, "suggestedFix": "Specific actionable fix", "escalateToHuman": false, "diagnosis": "Detailed explanation for humans if escalating"}
Automatic Fix: {"rootCause": "git_status_clean verifier failing because monorepo has uncommitted files", "shouldRetry": true, "suggestedFix": "Auto-commit all changes before starting this task.", "escalateToHuman": false, "diagnosis": ""}
Different Strategy: {"rootCause": "Worker trying to build JS project but no build script", "shouldRetry": true, "suggestedFix": "Skip build step for JavaScript projects.", "escalateToHuman": false, "diagnosis": ""}
Human Needed: {"rootCause": "Notion API returning 401 Unauthorized", "shouldRetry": false, "suggestedFix": "", "escalateToHuman": true, "diagnosis": "API key invalid or expired. Human needs to provide a valid key in .env.executive."}
Analyze the evidence and respond with JSON only.
