plan-mode-trace
Follow one value through the system end to end. Use when explaining how something works, debugging a data flow, or verifying that a path exists as described.
SKILL.mdskills/plan-mode/trace/SKILL.md
GitHubTrace
Explain how something actually works by following one concrete instance end to end, not by summarizing the architecture.
- Pick one concrete instance to follow — a single request, record, or message with a real identifier. A trace of a real instance beats a description of the general flow.
- Follow it forward through every hop: entry point, validation, transformation, storage, and exit. Name the file, function, or service at each hop. Do not skip a hop because it seems obvious.
- At each hop, record what changes and what is preserved. Note where the instance could be dropped, duplicated, or reordered.
- Report the actual path as an ordered list of hops with the code or config that implements each. Flag any hop you inferred rather than read.
A trace is read-only. If the instance cannot be followed end to end, report the exact hop where the path breaks.
Record this output in docs/plans/ per the doc system, delegating the write to a subagent.