Diagnose → Review → Fix

An orchestration protocol that chains three skills into a single pipeline: find the root cause, write the fix, review it, and harden it. The human stays in the loop at every stage transition.

When to use

• YES: Uncertain bugs where root cause is unknown, multi-layer issues, high-risk changes needing diagnosis + review
• NO: Known bugs (skip to fix-loop), code review of existing changes (use two-pass-review directly), trivial fixes
• If you already know the root cause, skip Stage 1 and start at Stage 2

Pipeline

Four stages. Every stage transition requires human approval via AskUserQuestion with structured options and a recommended choice. Never auto-proceed.

Stage 1: Diagnose

Load the parallel-diagnosis skill. Pass it the problem statement and relevant file paths.

Receive: DiagnosisOutput with status, root_cause, confidence, agreement, affected_files, fix_direction.