Debug Playbook

Operational playbook for systematic debugging — hypothesis ledgers, discriminating experiments, mechanism sentences, minimal fixes, sibling hunts. Read in full at the start of every bug investigation.

49 stars 3 forksSoftware Development Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add toffyui/ccteams

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add toffyui/ccteams --skill debug-playbook
Manual install
git clone --depth 1 https://github.com/toffyui/ccteams.git /tmp/ccteams
mkdir -p ~/.claude/skills
cp -r /tmp/ccteams/teams/debug/skills/debug-playbook ~/.claude/skills/debug-playbook

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Debug Playbook

This is the literal procedure a frontier model follows when debugging. Follow
it step by step; the order is the point. Skipping ahead to "the obvious fix"
is the single most expensive mistake in debugging.

## Operating loop

1. **Capture the failure verbatim.** Copy the exact error text, stack trace,
   failing assertion, or wrong output into your notes before touching
   anything. You will compare against this later — after a change, "a
   different error" and "the same error" are opposite results, and memory
   will lie to you about which one you're seeing.
2. **Reproduce before reasoning.** Run the smallest thing that fails: the one
   test (`<runner> <path>::<test>`), the one request (`curl` the endpoint),
   the one function (a REPL call). If you cannot reproduce, STOP — collect
   environment facts (versions, env vars, data state) and report what's
   missing. Never debug from a description of a failure you haven't seen.
   - Suspected flaky? Run it 10× in a loop and record the failure rate
     before anything else. A 3/10 failure is a different class of bug
     (ordering, time, shared state) than a 10/10 failure.
3. **Read the trace bottom-up, and find YOUR frame.** The deepest frame in
   code you own is where evidence starts. The reported line is where the
   error *surfaced*, not where the bug *lives* — treat it as the end of a
   thread to pull, not the answer.
4. **Write a hypothesis ledger.** List 2–3 candidate causes explicitly (in a
Read the full skill on GitHub

Details

Skill name
debug-playbook
Path
teams/debug/skills/debug-playbook/SKILL.md
License
MIT
Repo updated
31 August 2026

FAQ

What does the Debug Playbook skill do?

Operational playbook for systematic debugging — hypothesis ledgers, discriminating experiments, mechanism sentences, minimal fixes, sibling hunts. Read in full at the start of every bug investigation.

How do I install the Debug Playbook skill?

Claude Code plugin: /plugin marketplace add toffyui/ccteams. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Debug Playbook popular?

It lives in toffyui/ccteams, which has 49 GitHub stars and 3 forks.

Related skills

Choose Team

49

toffyui/ccteams

Pick and apply the best ccteams agent team for a described need using natural language — reads team metadata, selects the closest match, and applies it.

AI, LLMs & Agents

Django Playbook

49

toffyui/ccteams

Operational playbook for Django + DRF — settings/version detection, ORM loading strategy, migration discipline, serializer field hygiene, timezone rules, and exact verification commands. Read in full at the start of every task on this team.

Software Development

Frontend Playbook

49

toffyui/ccteams

Operational playbook for framework-agnostic UI/UX/a11y — semantic-element-first markup, keyboard/focus verification, responsive layout checks, reuse of existing tokens over new CSS. Read in full at the start of every task on this team.

Frontend & Design

D365fo CLI

49

dynamics365ninja/d365fo-cli

D365 Finance & Operations X++ AI development skill powered by the d365fo CLI. Use whenever the user is working in a D365 F&O X++ project: writing, reading, searching, reviewing, or debugging classes, tables, forms, CoC extensions, event handlers, entities, security, batch jobs, business events, labels, or any AOT artifact — including bug investigation and code-reading tasks, not just new authoring. Prefer `d365fo search`/`get`/`find` over Grep/Glob when locating or inspecting AOT objects. Points to the topic-specific d365fo skills installed next to it.

Software Development26

Go API Playbook

49

toffyui/ccteams

Operational playbook for Go HTTP APIs — error wrapping, goroutine lifetimes, database/sql resource discipline, race-flagged verification. Read in full at the start of every task on this team.

Software Development

Skill Tester

48

harvard-lil/lawskills-hub

Helps create rubrics and test scenarios for evaluating AI skills, and evaluates conversation traces against those rubrics. Triggers when the user wants to test a skill, write a rubric for a skill, evaluate whether a skill is working well, define quality criteria for a skill, or assess a conversation where a skill was used.

Software Development

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.