Eyes on the target and the bug-to-check ledger (free sample)
by PaperChaseWebb
Seven ways to let a coding agent see what a device or old program is doing, a CHECKS.md ledger that turns every fixed bug into a build check, and two prompts.
- Price
- Free
- Difficulty
- Intermediate
- Setup
- 20 min
- Format
- .md file
eyes-on-the-target-bug-to-check-ledger-free-sample.md · 3 KB · direct download, no signup
What you end up with
Your agent stops claiming things work that it cannot see, and fixed bugs stay fixed.
What you get
- The eyes on the target table
- The CHECKS.md template
- Two prompts
Who it is for
Anyone pointing a coding agent at hardware, firmware or old software.
Works with
Solid chips: the agent is named in this listing's own tools list. Dashed chip: Plain Markdown, so it also pastes into other agents such as Grok Bot, Hermes, OpenClaw or Muse. We list those as compatible by format only, not as tested.
Tools needed
Cost to run: Free.
Time to result: Twenty minutes
Sample prompts, free to use
We just fixed [bug]. Write the rule we learned in one line, add a check that fails the build if it is broken again, add a row to CHECKS.md, and prove it: show the check failing on the old code and passing on the new.
Run it after every fix so lessons stay learned.
Free preview of the file
# Eyes on the target and the bug-to-check ledger (free sample) A free sample from Revive Old Tech with Coding Agents, by PaperChaseWebb. Written for Claude Code and Codex, and plain Markdown, so it works with any coding agent that can run a terminal. When people use coding agents to make old hardware and software work again, two habits separate the projects that finish from the ones that go in circles. The agent can see the target, and every lesson becomes a check that runs on every build. This sample gives you both. ## What is inside | Section | What it is for | |---|---| | 1. Eyes on the target | Seven ways to let the agent see what the device is doing | | 2. The bug-to-check ledger | A CHECKS.md template and the kinds of checks that work | | 3. Two prompts | Build the eyes, and turn a fixed bug into a check |
Worth knowing
- Work on copies of anything original.
Questions
What is in the full pack?
A REVIVAL.md brief, six revival lanes, a closed build and read loop, ordered goals with three-part proof, do-no-damage rules, a rules block and 14 prompts.
Details
Version 1.0 · Updated Oct 27, 2026 · Markdown version of this page
License: Personal and commercial use. Download terms
Related
Revive Old Tech with Coding Agents: drivers, firmware, crash patches and device bridges
A Markdown method for making abandoned hardware and old software work again with a coding agent: a REVIVAL.md brief, six revival lanes, ways to let the agent see the target, a closed build and read loop, a bug-to-check ledger, do-no-damage rules, a rules block and 14 prompts.
Reverse engineer a console kernel with Claude Code so new controllers work on old hardware
Claude Code read the Xbox 360 kernel's USB stack through a Ghidra MCP server, ported an open Linux driver to C and built a boot plugin, so up to four Xbox Series controllers pair wirelessly with a modded 360.
Spec-First Build Docs: PRD, design system, architecture note, agents guide and readiness check
A Markdown pack of the four documents to write before an agent builds anything, sized to the stakes: a PRD an agent can build from without inventing scope, the smallest design system that holds, a one-page architecture note with reversal costs, an agents guide with a project tree for Claude Code, Codex and Cursor, a weekly staleness pass and a nine-area readiness check.