Skip to content

astroville/sprout / .claude/skills/challenge-diagnosis

challenge-diagnosis

Verified

Protocol for challenging and revising a bug diagnosis — layer vs reject modes, investigation history format, re-diagnosis instructions.

What I do

Define how an engineer's challenge to a bug diagnosis gets processed: which mode to use, how to preserve the reasoning chain, and what the debug-investigator should do differently in each mode.

Investigation History format

Appended to the bug spec after each challenge round. Never delete existing rounds — the history is append-only.

## Investigation History

### Round 1 — Initial diagnosis
- **Date**: 2026-04-22T14:00:00Z
- **Agent**: debug-investigator
- **Root cause**: <one-line summary>
- **Confidence**: High | Medium | Low
- **Key evidence**: <what pointed to this root cause>

### Round 2 — Challenged (layer)
- **Date**: 2026-04-22T15:30:00Z
- **Challenged by**: engineer
- **Feedback**: "<verbatim engineer feedback>"
- **Revised root cause**: <updated root cause incorporating both threads>
- **What changed**: <what's different from the previous round and why>
- **Confidence**: High | Medium | Low

Round fields

FieldRequiredNotes
DateyesUTC ISO-8601
Agentyesdebug-investigator or engineer
Root cause / Revised root causeyesOne-line summary
ConfidenceyesHigh / Medium / Low
Challenged bychallenge rounds onlyAlways engineer
Feedbackchallenge rounds onlyVerbatim engineer feedback
What changedchallenge rounds onlyDelta from previous round
Key evidenceinitial round onlyWhat pointed to the root cause

Mode detection

Scan the engineer's feedback for mode signals:

Reject signals — if ANY of these appear, use reject mode:

  • "wrong", "incorrect", "not correct", "off base"
  • "re-diagnose", "start over", "start fresh"
  • "this isn't it", "missed the mark"
  • Explicit --reject flag

Layer signals — everything else defaults to layer:

  • "also consider", "what about", "I think it might also be"
  • "have you looked at", "related to"
  • "in addition to", "another possibility"

When ambiguous, default to layer — it's safer because nothing is discarded.

Layer mode protocol

The debug-investigator receives:

  1. The full existing spec (including current Root Cause and Fix Plan)
  2. The engineer's feedback as additional context
  3. These instructions:

Treat the existing analysis as valid evidence. The engineer has added a new hypothesis or thread. Investigate both the original root cause AND the new hypothesis. Produce a single merged analysis — not two competing explanations. If the new hypothesis supersedes the original, say so explicitly. If they're complementary (e.g. a root cause and a contributing factor), explain the relationship.

The investigator updates the spec's Root Cause and Fix Plan sections in place, then appends a new round to Investigation History.

Reject mode protocol

Before the debug-investigator runs:

  1. Archive the current ## Root Cause, ## Fix Plan, and any ## Investigation sections into ## Investigation History as the previous round. Mark them clearly as superseded.
  2. Clear the Root Cause and Fix Plan sections (replace with placeholders for the investigator to fill).

The debug-investigator then receives:

  1. The spec with cleared Root Cause / Fix Plan sections
  2. The full Investigation History (so it can reference — but not assume the correctness of — previous findings)
  3. The engineer's feedback as the starting hypothesis
  4. These instructions:

The previous analysis has been rejected by the engineer. Their feedback is your starting hypothesis. You may reference the archived findings in Investigation History as evidence, but do not assume they are correct. Start your investigation from the engineer's hypothesis and follow the evidence.

What this skill does NOT do

  • Does not auto-accept or auto-reject diagnoses — the engineer decides
  • Does not delete previous analysis — layers merge, rejects archive
  • Does not require the original session — the spec on disk is the input
  • Does not modify the debug-investigator's core investigation logic — only the input framing changes
  • Does not add Go code — this is instructions in markdown
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall