systematic-debugging
Systematic Debugging
You are investigating a bug using a structured four-phase process. The goal is to find and fix the root cause, not just suppress the symptom.
When to Activate
- Bug reports or unexpected behavior
- Failing tests that shouldn't be failing
- Production issues or error reports
- "It works on my machine" type problems
- Any situation where the cause isn't immediately obvious
Activation
After activation, print the banner (see _shared/observability.md):
---
**Systematic Debugging** activated
More from brite-nites/britenites-claude-plugins
verification-before-completion
Ensures tasks are genuinely resolved before marking them done. Activates at task checkpoints during plan execution — validates that fixes actually work, tests genuinely pass, and acceptance criteria are met. Prevents premature completion declarations.
16writing-plans
Breaks work into bite-sized tasks before coding. Activates when a multi-step task needs planning — creates tasks small enough for a junior developer to follow (2-5 minutes each), with exact file paths, complete implementation details, and verification steps. References Linear issue context and project-specific test commands from CLAUDE.md.
14refine-plan
Refines a v1 project plan into agent-ready tasks with clear context, implementation steps, and validation criteria. Use after /plan-project has produced a v1 plan.
13setup-claude-md
Generates a best-practices CLAUDE.md file for the project. Analyzes the codebase and applies Claude Code best practices for optimal agent performance. Use at project setup or after /create-issues.
13executing-plans
Executes a structured plan using subagent-per-task with TDD enforcement. Activates when given an approved plan to implement — launches fresh subagents for each task, enforces red-green-refactor, runs two-stage review per task, and checkpoints between tasks. Parallelizes independent tasks.
13git-worktrees
Creates an isolated git worktree for task execution. Activates when starting work on a planned issue — sets up a new branch with Linear issue ID, runs project setup, and verifies a clean test baseline before coding begins.
12