dr-zog
UserLight-touch, enforced traceability from requirements to code — a zero-dependency Go engine + a Claude Code plugin of skills.
Categories
Indexed Skills (6)
audit
Run the Plumbline engine over a repository and narrate the traceability scorecard — coverage, uncovered requirements, dead-ends, zombie code, broken anchors, orphan code-areas and warnings — prioritising the weakest areas. Use when someone asks to audit, score, or check requirement↔code traceability, or how well a codebase is anchored.
enforce
Install Plumbline's traceability gate so unanchored code can't land — offer the developer a pre-commit hook, a CI job, both, or neither, and set up whichever they choose. Use this whenever someone wants to enforce, gate or require traceability, add a pre-commit or CI check for Plumbline, "make the build fail on broken anchors", wire the engine into their pipeline, or asks how to stop unanchored code being committed. Reach for it once a project is onboarded and the team wants the discipline enforced automatically rather than by hand.
new-ticket
How to write a ticket for the Plumbline repo — where they live and how much they carry. Use when capturing a Plumbline requirement, TODO, feature idea or bug as a ticket, or when you need this repo's ticket conventions. Dev-process skill for building Plumbline itself; not shipped in the plugin.
raise-pr
How a change lands on main in the Plumbline repo. Use when a Plumbline change is ready to land, you're about to open or merge a pull request, or you need this repo's PR/merge conventions. Dev-process skill for building Plumbline itself; not shipped in the plugin.
work-ticket
The local development loop for a change to the Plumbline repo — how a ticket goes from requirement to landed code here. Use whenever you start work on a Plumbline ticket/feature/change, are about to implement something in this repo, or need this repo's convention for how a change is built. Dev-process skill for building Plumbline itself; not shipped in the plugin.
write-adr
When and how to record an architecture decision for Plumbline as an ADR, and how that differs from a process doc. Use when a structural/architectural decision is being made that commits the project to a path, when someone says "let's record this decision", or when you need this repo's ADR conventions. Dev-process skill for building Plumbline itself; not shipped in the plugin.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.