loom-wiring-test
Wiring Test Skill
Overview
Tests pass and code compiles, yet the feature is never wired up — command not registered, endpoint not mounted, module not imported, component never rendered. This is the exact failure loom's goal-backward verification exists to catch. Use this skill to write strong verification fields for a stage.
⚠️
truthsis GONE. It was removed as a standalone field. Behavioral commands now live inacceptance; the goal-backward layers areartifacts,wiring,wiring_tests,dead_code_check. Any plan still using a top-leveltruths:block is stale — serde silently ignores it, so the "check" runs NOTHING and false-passes.
The five verification fields
| Field | Type | Proves | Timeout |
|---|---|---|---|
acceptance |
Vec<AcceptanceCriterion> |
Build/test/lint AND observable behavior (the old truths commands) |
5 min (Simple) / 30 s (Extended) |
artifacts |
Vec<String> (globs) |
Files exist with real implementation | — |
wiring |
Vec<WiringCheck> |
Static connection point present (regex in a file) | — |
wiring_tests |
Vec<WiringTest> |
Runtime integration: command output matches criteria | — |
dead_code_check |
Option<DeadCodeCheck> |
No orphaned code (see /loom-dead-code-check) |
— |
loom check <stage-id> [--suggest] runs the goal-backward layers (artifacts, wiring, wiring_tests, dead_code_check). acceptance runs during loom stage complete / loom stage verify.