What problem does it solve? Features often fail silently because configuration or data gets dropped between layers of a codebase — an option exists at the entry point but never reaches the function that needs it. This Skill systematically traces a capability end-to-end to find dropped config, silent defaults, partial wiring, stale wrappers, and shape mismatches. ## Core Features & Use Cases - Architecture Mapping: Identifies entry points, orchestration layers, capability modules, and external integrations that a feature touches. - Gap Detection: Checks every layer boundary for seven failure modes including dropped config, silent defaults, dead exports, and shape mismatches, each reported with exact file:line evidence. - Structured Reporting: Produces a severity-ranked wiring trace report (Critical/High/Medium) and creates tasks for Critical or High severity gaps. - Use Case: A developer wonders why Gmail OAuth works in one flow but fails in another. Run the trace on "Gmail OAuth" to map every path from entry point to token consumption and pinpoint exactly where the token refresh is dropped. ## Quick Start Ask the assistant to trace the capability you are debugging, for example: trace the invoice source tracking capability through the full project.