Individual skill
wiring-contract
Derive this project's own integration conventions from what the code already does, draft them as a wiring contract, and hold new work to it. Closes the built-but-not-wired gap at L3 (walking skeleton) — a mechanism that ships and is never called reads green in every other check.
plugins/mycelium/skills/wiring-contract/SKILL.md
Source commit d44421b0667bb71ad515ae7576dfc0f47b00504f
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 52
- Repository last updated
- Nov 6, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- ai-agent Repository topic
- delivery Repository topic
- devops Repository topic
- discovery Repository topic
- product-development Repository topic
- product-management Repository topic
- claude-code-skills Repository topic
- dora-metrics Repository topic
- product-discovery Repository topic
- legal Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Wiring Contract
Answer one question for this project and then keep answering it automatically: **when something is built here, what does it have to be connected to before it counts as done?**
The failure is not carelessness, it is structural. A model's context makes it unable to see whether the element it just generated is referenced anywhere else, so plausible-but-unreferenced code is the *expected* output. Across 304,362 verified AI-authored commits in 6,275 repositories, "unused variables or parameters" is the second most frequent issue class, and "undefined variable or reference" — writer and reader disagreeing about a name or path — is the most common runtime bug category. It does not wash out: AI-authored code survives **longer** than human-written code (53.9% vs 69.3% line death rate), so an orphan is *less* likely to be cleaned up than a human's.
Every ordinary signal misses it. Tests pass, coverage rises, lint is clean, review approves — because each of those verifies a thing **against itself**, and wiring is a property of a **pair**.
## When to Use
- **At L3, before implementation** — the walking-skeleton obligation (G-V13). A design is not complete until its joins are named.
- On an existing project, once, to discover what conventions it already has.
- After a structural change (new directory, new layer, a move) — **regenerate**, never hand-edit.
- When `check_wiring_contract.py` reports UNGOVERNED files you did not expect.