← ClaudeAtlas

plumb-line-methodlisted

Use when an edit would make the system look more real, finished or certain than it is, to make the honest version instead: a failing test or red CI that cannot honestly pass (a dependency down, a bar missed, nobody knows why) under pressure to get it green anyway; a fallback, fixture or generated value passed off as real; a guessed threshold hardcoded as if measured; a stub called production-ready; a baseline regenerated without explaining the drift; a confidence or provenance field dropped; an inconclusive result shown as a number; a layer shortcut. It answers yes, and: meet the need, keep what is uncertain visible. Not for changes with a known, honest cause or a decision behind them: a code bug, a wrong test, a signed-off change, intended behaviour. Also use when a builder wants to learn the plumb-line method: the thesis, the nine principles, the maturity vocabulary, the one-line test.
slopstopper/plumb-line · ★ 4 · Code & Development · score 70
Install: claude install-skill slopstopper/plumb-line
# The plumb-line method Read `reference/portable-principles.md` (relative to the plugin root) and teach from it. Do not restate the principles here — that file is the single source. If the file cannot be read, stop immediately and report: "Cannot teach: `reference/portable-principles.md` is missing or unreadable. Do not continue from memory." If you were invoked in the middle of a task, go straight to the section for that moment; the walk can wait. A failing test or red CI that has to be made to pass, where the reason may lie outside the code: **Mid-task: a test that cannot pass honestly**. Any other edit that would make something look more real, finished or certain than it is: **Mid-task: other moments**. When invoked: 1. Read the principles document. 2. Give the builder the thesis and the spine (null results are valid) first. 3. Walk the nine principles only as deep as asked; lead with the one most relevant to what the builder is doing. 4. Always end on the one-line test as the portable gut-check. 5. Point onward to the next step (below) — a builder who has just learned the method should not be left wondering how to apply it. This skill never edits files or installs anything. ## Mid-task: a test that cannot pass honestly The moment: you have been asked to make a failing test pass, or CI green, and the reason it fails is outside the code you can change. A service is unreachable, a credential is not provisioned, the data does not contain what the test needs, the