recipe-diagnose
Investigate problem, verify findings, and derive solutions
Profile →npx skills add shinpr/claude-code-workflows --skill recipe-diagnose --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
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. At each Agent invocation below, build the prompt as a mechanical extraction: copy the named source values into the exact fields, apply only the declared serialization, then invoke immediately. **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 Determinatio
- Orchestrator Definition
- Step 0: Problem Structuring (Before investigator invocation)
- 0.1 Problem Type Determination
- 0.2 Information Supplementation for Change Failures
- 0.3 Problem Essence Understanding
- Diagnosis Flow Overview
- Execution Steps
- Step 1: Investigation (investigator)
- Step 2: Investigation Quality Check
- Step 3: Verification (verifier)
- Step 4: Solution Derivation (solver)
- Step 5: Final Report Creation
- Completion Criteria
What does the recipe-diagnose skill do?
Investigate problem, verify findings, and derive solutions
How do I install it?
Run `npx skills add shinpr/claude-code-workflows --skill recipe-diagnose --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From shinpr/claude-code-workflows, a repository with 664 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.