Bugscope

BugScope

**A two-skill suite that scopes a bug before fixing it.** `bugscope-finder` turns a bug report into a written, falsifiable plan on disk; `bugscope-resolver` executes that plan and nothing else — and stops when the diagnosis turns out to be wrong.

Works with **Claude Code**, **OpenAI Codex**, and **GitHub Copilot**. Framework-agnostic: it reads your project's own agent configuration instead of guessing at your stack.

---

The problem it addresses

The common failure mode of a coding agent on a bug is not that it can't find the cause. It is that it finds *a* cause and fixes it in the same breath: nine files touched, the original symptom possibly still there, and no way to tell which change was the fix. The reasoning that justified the diff evaporates the moment the diff exists.

BugScope splits the two halves and puts a document between them.

  bug report ──► bugscope-finder ──► .bugscope/plan-.md ──► bugscope-resolver ──► diff
   text                                       ▲                        │
   screenshot                                 │  you read it,          │  hypothesis
   stack trace                                │  edit it, reject it    │  refuted?
   issue                                      │                        ▼
                                              └──────────────── status: invalidated
                                                                 (no code changed)

The plan is a file, not conversation state. You can read it, argue with it, hand-edit it, or hand it to a different agent tomorrow. And because the plan names a scope, the diff you get is the diff you approved.

---

The two skills

`bugscope-finder` — diagnose, don't fix

1. Phase 0 — detect the project. Reads AGENTS.md, .claude/CLAUDE.md, .github/copilot-instructions.md, .cursor/rules/ and friends first, because they carry intent no file-sniffing recovers ("tests run via make check", "never edit generated/").