boyscoutlisted

# boyscout Apply the Boy Scout Rule: leave things better than you found them. While working on a task, scan the surrounding context for improvement opportunities — flaky tests, broken scripts, missing coverage, dead code, interesting refactors, outdated docs, skill gaps, etc. New findings are silently archived to the backlog so the primary task is not interrupted. When the user explicitly invokes `/boyscout` (or `/boyscout clean` / `/boyscout deep`), present the accumulated findings and let them attack each in an isolated worktree (branched from an up-to-date base branch), route to a detailed ticket, or leave in the backlog for later. **Golden rule: default to silent archive — never auto-fix without explicit user opt-in.** New findings are added to the backlog without interrupting the primary task. Triage and fixes are opt-in: the user invokes `/boyscout` to see the selection form, or explicitly says "fix item N now" during the scan. When a finding is attacked from the backlog, success consumes the entry (deletes it). ## When to use Invoke `/boyscout` when you notice opportunities while working on a primary task: - Flaky or intermittently failing tests - Scripts that don't behave as expected or are clearly broken - Refactoring opportunities (extract function, rename, simplify) - Missing or insufficient test coverage - Dead code: unused imports, unreachable branches, obsolete flags - Leftover TODOs or FIXMEs with a clear path forward - Side tasks uncovered during investig