debug
Systematic Debugging
Iron Law
IF >= 3 FIXES TRIED, STOP AND QUESTION THE ARCHITECTURE
Phases
1. Reproduce
Confirm the bug with a minimal, exact reproduction case.
- Get the exact error message and stack trace
- Write a failing test if possible
- If you cannot reproduce it, you cannot fix it
2. Hypothesize
Form 3 hypotheses about the root cause.
- Rank them by likelihood
- Explain the reasoning behind each
- Do NOT skip to fixing before hypothesizing
More from scando1993/sugar
worktree
Git worktree lifecycle management. Use when creating, navigating, syncing, or cleaning up git worktrees for parallel development.
12ralph
Convert PRDs to prd.json format for the Ralph autonomous agent system. Use when you have an existing PRD and need to convert it to Ralph's JSON format. Triggers on: convert this prd, turn this into ralph format, create prd.json, ralph json.
12respond-review
Guidance for receiving and responding to code review feedback. Use when addressing PR review comments, incorporating reviewer suggestions, or managing review discussions.
12tdd
Test-driven development with strict RED-GREEN-REFACTOR enforcement. Enforces: write failing test first, minimal implementation, then refactor. Use when adding new features or fixing bugs.
11prd
Generate a Product Requirements Document for a feature. Use when planning a feature, starting a project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.
11finish
Branch finishing and PR preparation. Use when completing a feature branch, preparing a pull request, or cleaning up commit history.
11