Investigate a reported problem, find root cause, and create a GitHub issue with a TDD fix plan. Mostly hands-off — minimize questions.
Process
1. Capture the problem
Get a brief description; if none, ask: "What's the problem you're seeing?" Then start investigating.
2. Explore, diagnose, and plan the fix
Use the Agent tool with subagent_type=Explore to find where the bug manifests, the code path, and why it fails (root cause, not symptom) — plus related tests and working patterns. Check git log. Then determine the minimal fix, affected modules, and needed test coverage.
3. Design TDD fix plan
List ordered RED-GREEN cycles, one vertical slice each: RED — test for the broken/missing behavior; GREEN — minimal change to pass. Assert on public interfaces, not internals. See the tdd skill for methodology.
4. Create the GitHub issue
Create via gh issue create with the template below; share the URL after.
Problem
Actual behavior, expected behavior, repro steps.
Root Cause Analysis
Code path, why it fails, contributing factors. Describe behaviors/contracts, not file paths or line numbers.
TDD Fix Plan
- RED: test for [behavior] → GREEN: [minimal change to pass]
- RED: test for [next behavior] → GREEN: [minimal change to pass]
REFACTOR: [any cleanup needed]
Acceptance Criteria
- Criterion 1
- Criterion 2
- All new tests pass
- Existing tests still pass
Print the URL and a one-line root-cause summary.