From ab6006e161893dd9abf9dee746c752d42ac05b0c Mon Sep 17 00:00:00 2001 From: Milan Date: Wed, 8 Apr 2026 21:39:33 -0700 Subject: [PATCH] =?UTF-8?q?fix:=20diagnose=20next-step=20suggestions=20?= =?UTF-8?q?=E2=80=94=20planning=20and=20shipping,=20not=20investigate?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Replace /investigate suggestions with actionable next steps: - Simple fix → implement it, then /review + /ship - Complex fix → plan + /plan-eng-review - Scope question → plan + /plan-ceo-review - Fix PR ready → /review + /ship Co-Authored-By: Claude Opus 4.6 --- diagnose/SKILL.md | 12 ++++++------ diagnose/SKILL.md.tmpl | 12 ++++++------ 2 files changed, 12 insertions(+), 12 deletions(-) diff --git a/diagnose/SKILL.md b/diagnose/SKILL.md index 9b81a5314..bc7987708 100644 --- a/diagnose/SKILL.md +++ b/diagnose/SKILL.md @@ -1649,13 +1649,13 @@ NEXT STEPS After printing the report, suggest the most relevant next skill: -- **ROOT_CAUSE_ESTABLISHED + fix is straightforward:** → `/investigate` to implement and test the fix -- **ROOT_CAUSE_ESTABLISHED + fix is complex / risky / multi-system:** → Write a plan, then `/plan-eng-review` to lock in the architecture before implementing -- **ROOT_CAUSE_ESTABLISHED + fix needs scope/strategy discussion:** → Write a plan, then `/plan-ceo-review` to decide scope (is this a quick patch or a redesign?) +- **ROOT_CAUSE_ESTABLISHED + fix is straightforward:** → Ask the user to implement the fix (the diagnostic report has enough detail). Then `/review` before merging and `/ship` to land it. +- **ROOT_CAUSE_ESTABLISHED + fix is complex / risky / multi-system:** → Write a plan, then `/plan-eng-review` to lock in the architecture before implementing. +- **ROOT_CAUSE_ESTABLISHED + fix needs scope/strategy discussion:** → Write a plan, then `/plan-ceo-review` to decide scope (is this a quick patch or a redesign?). - **PROBABLE_CAUSE:** → Suggest what additional data/access would upgrade to ROOT_CAUSE. If browse is available and issue is UI-visible, suggest `/qa` to reproduce the exact flow. -- **INSUFFICIENT_EVIDENCE:** → Suggest `/investigate` with specific instructions on what to look for, or suggest instrumenting the code (add logging) and waiting for recurrence. -- **Security implications found:** → `/cso` for a security audit of the affected area -- **Multiple systems affected:** → `/review` when the fix PR is ready, to catch cross-system issues +- **INSUFFICIENT_EVIDENCE:** → Suggest instrumenting the code (add logging) and waiting for recurrence, or specific data/access that would unblock the diagnosis. +- **Security implications found:** → `/cso` for a security audit of the affected area. +- **Fix PR ready:** → `/review` before merging, then `/ship` to land it. --- diff --git a/diagnose/SKILL.md.tmpl b/diagnose/SKILL.md.tmpl index aa71595ea..f371c1fdb 100644 --- a/diagnose/SKILL.md.tmpl +++ b/diagnose/SKILL.md.tmpl @@ -1065,13 +1065,13 @@ NEXT STEPS After printing the report, suggest the most relevant next skill: -- **ROOT_CAUSE_ESTABLISHED + fix is straightforward:** → `/investigate` to implement and test the fix -- **ROOT_CAUSE_ESTABLISHED + fix is complex / risky / multi-system:** → Write a plan, then `/plan-eng-review` to lock in the architecture before implementing -- **ROOT_CAUSE_ESTABLISHED + fix needs scope/strategy discussion:** → Write a plan, then `/plan-ceo-review` to decide scope (is this a quick patch or a redesign?) +- **ROOT_CAUSE_ESTABLISHED + fix is straightforward:** → Ask the user to implement the fix (the diagnostic report has enough detail). Then `/review` before merging and `/ship` to land it. +- **ROOT_CAUSE_ESTABLISHED + fix is complex / risky / multi-system:** → Write a plan, then `/plan-eng-review` to lock in the architecture before implementing. +- **ROOT_CAUSE_ESTABLISHED + fix needs scope/strategy discussion:** → Write a plan, then `/plan-ceo-review` to decide scope (is this a quick patch or a redesign?). - **PROBABLE_CAUSE:** → Suggest what additional data/access would upgrade to ROOT_CAUSE. If browse is available and issue is UI-visible, suggest `/qa` to reproduce the exact flow. -- **INSUFFICIENT_EVIDENCE:** → Suggest `/investigate` with specific instructions on what to look for, or suggest instrumenting the code (add logging) and waiting for recurrence. -- **Security implications found:** → `/cso` for a security audit of the affected area -- **Multiple systems affected:** → `/review` when the fix PR is ready, to catch cross-system issues +- **INSUFFICIENT_EVIDENCE:** → Suggest instrumenting the code (add logging) and waiting for recurrence, or specific data/access that would unblock the diagnosis. +- **Security implications found:** → `/cso` for a security audit of the affected area. +- **Fix PR ready:** → `/review` before merging, then `/ship` to land it. ---