Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Systematic Debugging
## Overview
Random fixes waste time and create new bugs. Quick patches mask underlying issues.
**Core principle:** ALWAYS find root cause before attempting fixes. Symptom fixes are failure.
**Violating the letter of this process is violating the spirit of debugging.**
## The Iron Law
```
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST
```
If you haven't completed Phase 1, you cannot propose fixes.
## When to Use
Use for ANY technical issue:
- Test failures
- Bugs in production
- Unexpected behavior
- Performance problems
- Build failures
- Integration issues
**Use this ESPECIALLY when:**
- Under time pressure (emergencies make guessing tempting)
- "Just one quick fix" seems obvious
- You've already tried multiple fixes
- Previous fix didn't work
- You don't fully understand the issue
**Don't skip when:**
- Issue seems simple (simple bugs have root causes too)
- You're in a hurry (rushing guarantees rework)
- Manager wants it fixed NOW (systematic is faster than thrashing)
## The Four Phases
You MUST complete each phase before proceeding to the next.
### Phase 1: Root Cause Investigation
**BEFORE attempting ANY fix:**
…
The line at the top of this page pins the label git:20260623.d2a2f44, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (9854 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag
Source
GitHub
jkaloger/lazyspec · 10 stars · license MIT · pushed 2026-11-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_s5eoyy3tz34a2lu7
GET https://markdownregistry.com/api/v1/resolve?ref=jkaloger/lazyspec/systematic-debugging
GET https://markdownregistry.com/api/v1/blob/3c56f4556f4d72444c597dd2899ec56345cd727a42a5225fb9ba4cbc0e1b0de2
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
jkaloger/lazyspec · examples/spec/skills/create-plan/SKILL.md · Use when planning implementation against a Spec or as a standalone plan for bug fixes, tweaks, and refactors. Creates…
jkaloger/lazyspec · examples/spec/skills/create-spec/SKILL.md · Use when locking down technical contracts for a vertical slice. Creates Spec documents with data models, API surface…
jkaloger/lazyspec · examples/spec/skills/lazy/SKILL.md · Use when starting new work, planning a feature, or deciding what to implement next. Detects existing RFCs, Specs, and…
jkaloger/lazyspec · examples/spec/skills/resolve-context/SKILL.md · Use when an agent needs full context before beginning work on a Spec or Plan. Gathers the document chain from plan…
jkaloger/lazyspec · examples/spec/skills/review-plan/SKILL.md · Use when a Plan is complete and ready for review. Two-stage review -- spec contract compliance first, code quality…
jkaloger/lazyspec · examples/spec/skills/write-rfc/SKILL.md · Use for heavy, cross-cutting, or architecturally significant designs. Creates an RFC document with intent, interface…
jkaloger/lazyspec · skills/advance/SKILL.md · Use when moving a document to its next status along the type's lifecycle DAG, maintaining links across the transition.
jkaloger/lazyspec · skills/co-write/SKILL.md · Use when drafting a document of a configured type collaboratively -- AI proposes a draft body, the human edits, iterate…
jkaloger/lazyspec · skills/configure-type/SKILL.md · Use when adding a new custom document type to a lazyspec project. Interviews the user to co-author the type's…
mvschwarz/openrig · skills/_canonical/process/systematic-debugging/SKILL.md · Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
mvschwarz/openrig · packages/daemon/specs/agents/shared/skills/process/systematic-debugging/SKILL.md · Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
cbrock84/headcount · plugins/technology/skills/systematic-debugging/SKILL.md · Finds the root cause of a bug, test failure, or unexpected behavior before proposing any fix. Use this whenever…
a5c-ai/babysitter · library/methodologies/superpowers/skills/systematic-debugging/SKILL.md · Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Requires root cause…
