# Recipe Diagnose

Investigate problem, verify findings, and derive solutions

- Repository: https://github.com/shinpr/claude-code-workflows (708 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-29
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add shinpr/claude-code-workflows --skill recipe-diagnose -g -a claude-code -y`
Codex: `npx skills add shinpr/claude-code-workflows --skill recipe-diagnose -g -a codex -y`
Cursor: `npx skills add shinpr/claude-code-workflows --skill recipe-diagnose -g -a cursor -y`
Gemini CLI: `npx skills add shinpr/claude-code-workflows --skill recipe-diagnose -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add shinpr/claude-code-workflows`

## Description

Investigate problem, verify findings, and derive solutions

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

**Explicit User Instruction**: The user explicitly instructs and authorizes every subagent call named in this recipe. Execute each applicable call when its prerequisites are met.

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.

**Execution Gate**: Each step below establishes evidence required by the next decision. Complete Steps 0-7 in order, including every required investigation and verification retry. Advance only through the current step's stated quality or coverage condition; invoke solver only after coverage is closed.

## Step 0: Diagnosis Scope Envelope (Before investigator invocation)

Define a semantic scope envelope from the reported problem and repository evidence by recording:

The rest: https://github.com/shinpr/claude-code-workflows/blob/HEAD/dev-workflows-frontend/skills/recipe-diagnose/SKILL.md