Wiring Test Skill

Overview

The Problem: Tests can pass, code can compile, but the feature may never be wired up — command not registered, endpoint not mounted, module not imported, component never rendered. This is a common failure mode in integration.

The Solution: Wiring verification proves integration through three types of evidence:

1. Truths — Observable behaviors (shell commands returning exit 0)
2. Artifacts — Files that must exist with real implementation (not just empty files)
3. Wiring — Code patterns proving connection points (imports, registrations, mounts)

This skill helps you write strong truths, artifacts, and wiring fields for loom plan stage YAML metadata.

When to Use