What problem does it solve?
Saves time and prevents errors when starting a recursive dependency trace by interactively collecting the entry file, repository root, output directory, and worker cap with sensible defaults and validations so users do not have to hand-type absolute paths.
Core Features & Use Cases
- Candidate discovery: Scans the current working directory (and one level down in common source folders) for plausible entry-point files and ranks them by priority and recency.
- Safe output proposal: Infers repository root by looking for repo markers and proposes artifact directories that avoid polluting read-only or vendor snapshots.
- Single-step confirmation: Presents the four decisions in one AskUserQuestion turn, supports "other" free-form inputs, and requires explicit confirmation before creating any directories or launching the parallel trace.
- Use case: Ideal for developers who want to run a single, interactive dependency analysis on a script without manually resolving paths or risking artifacts in the wrong tree.
Quick Start
Invoke /trace-deps to interactively select an entry, repo root, output directory, and cap, then confirm to create the output directory and start the parallel dependency trace.
