Plumbline diagnose engine
Internal Plumbline engine. Use only after the Plumbline router or a Plumbline phase wrapper selects diagnosis.From its SKILL.md
npx -y skills add nickyfactz/plumbline --skill plumbline-diagnose-engineAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
3.2 KB, as published. Nobody here has run it
Diagnose engine
Outcome and completion
Identify the minimum sufficient root cause, not merely the next error, and
choose the proportional next action for the user's symptom. For a runtime
blocker, regression, contract violation, repeated failure, or failed expensive
gate, complete a bounded failure-path trace before proposing the correction:
reproduce the symptom, inspect the relevant caller and callee or state owner,
compare observed behavior with the contract or invariant, and locate the fix
boundary at the owner of the broken behavior. Expand the trace only when a
shared caller, contract, or state transition makes it necessary. A trivial
local fix may stay lightweight when the report records Local cause confirmed
and why wider tracing is unnecessary.
Complete Diagnosis with a reproducible signal, the relevant failure path, root-cause evidence, the violated contract or invariant, fix boundary, verification result, and remaining uncertainty. A green rerun that only moves the error is not diagnosis. Keep a small bug fix outside feature-plan ceremony unless its scope genuinely escalates.
Reproduce the exact symptom
Use the active checkout and a direct feedback signal for a small clear fix. For
a hard bug or performance regression, read the current code path, user
timeline, logs, tests, and bounded relevant history before broad archaeology.
Read references/research-policy.md and
references/runtime-value-testing.md when the diagnosis needs external facts
or a runtime proof gate.
Build and run the smallest deterministic loop that can go red on the exact symptom: a focused test, CLI call, HTTP probe, trace replay, or narrow harness. If no red-capable loop exists, name the missing artifact or environment access and request the smallest useful addition.
Reproduce and minimize before theorizing. Rank only the plausible falsifiable
hypotheses needed to explain the failure and use discriminating probes rather
than a fixed probe count. Diagnostic tests and probes are working artifacts:
remove them before checkpoint completion when they only locate the cause. If
they expose a durable regression, generalize the proof at a stable public seam;
when no correct seam exists, record the seam gap instead of creating false
confidence. Rerun the original loop after the fix. Use repository history
selectively rather than automating git bisect.
Add a regression test only at a stable public seam that exercises the real failure. When no correct seam exists, record the seam gap instead of creating false confidence. Do not patch the reported error line solely to make the current loop green before the failure path and fix boundary are understood, except for immediate safety containment; mark containment provisional and continue diagnosis. When Diagnose follows a failed Execute checkpoint, keep the same candidate and checkpoint active. Return a correction path to Execute; do not close the objective or select a successor. Environment and harness failures may require repairing or replacing the evidence path before implementation resumes. Report root cause, evidence, fix boundary, and remaining uncertainty.