trace

Trace a capability through every project layer to find dropped config and wiring gaps.

4|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/willem4130/sageo-cli --skill trace-willem4130
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trace
Source: https://github.com/willem4130/sageo-cli/tree/main/.gg/skills/trace
Command: npx skills add https://github.com/willem4130/sageo-cli --skill trace-willem4130

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about trace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug why a feature doesn't work end-to-end?▼

Trace the capability from each entry point through orchestration and modules to its destination, checking what data enters and leaves each layer. This Skill automates that trace and reports exactly where config or data gets dropped, with file:line evidence at both ends.

How to find dropped config or missing wiring in a codebase?▼

Map all files referencing the capability with grep, then follow imports and function calls from entry points to consumption points. The trace checks seven gap types including dropped config, silent defaults, stale wrappers, and dead exports.

What kinds of wiring issues does a capability trace detect?▼

It detects dropped config, silent defaults replacing passed values, partial wiring where one path works and another doesn't, stale wrappers missing interface fields, missing user gates, dead exports, and shape mismatches where data arrives missing fields.

Does the trace report issues it cannot prove from the code?▼

No. It only reports gaps proven by reading the code at both the entry point and consumption point. Style issues, theoretical problems, and correctly working paths are explicitly excluded, and a clean trace is reported as a valid result.

What happens after a wiring trace finds critical gaps?▼

Each gap is reported with severity (Critical, High, Medium), the exact files and lines involved, the concrete failure, and a suggested fix. Tasks are then created via the tasks tool for any Critical or High severity gaps found.