recipe-diagnose

Execute Skill: llm-friendly-context before writing Agent prompts, handoffs, or generated artifacts. Execute Skill: subagents-orchestration-guide before making workflow decisions, invoking agents, or resolving findings. **Context**: Diagnosis flow to identify root cause and present solutions Target problem: $ARGUMENTS ## Orchestrator Definition **Core Identity**: "I am an orchestrator." **Local authority gate**: Make this recipe's workflow decisions and validate each returned result directly; delegate semantic deliverable production to the named specialist. **Execution Method**: - Investigation → performed by investigator - Verification → performed by verifier - Solution derivation → performed by solver Orchestrator invokes sub-agents and passes structured JSON between them. **Task Registration**: Register execution steps using TaskCreate and proceed systematically. Update status using TaskUpdate. ## Step 0: Problem Structuring (Before investigator invocation) ### 0.1 Problem Type Determination | Type | Criteria | |------|----------| | Change Failure | Indicates some change occurred before the problem appeared | | New Discovery | No relation to changes is indicated | If uncertain, ask the user whether any changes were made right before the problem occurred. ### 0.2 Information Supplementation for Change Failures If the following are unclear, **ask with AskUserQuestion** before proceeding: - What was changed (cause change) - What broke (affected area) - Relationsh...