Tracing who-calls-X or a data flow — mid-debug, not only before a refactor — or exploring code structure: where a symbol is defined, who calls it, blast radius, routes/contracts. Reach here before grep. Command by question: definition→ecp find, who-calls/blast-radius→ecp impact, full context→ecp inspect, filename-read-vs-written→ecp impact --literal, routes/contracts→ecp routes/ecp contracts, trace execution flow→ecp processes, graph question with no verb (orphans, all-impls)→ecp cypher. Grep only for non-code text: config values, log strings, fs layout.
$npx -y skills add coseto6125/egent-code-plexus --skill ecpInstalls into the current project.
Run `npx skills use "https://github.com/coseto6125/egent-code-plexus" --skill "coseto6125/egent-code-plexus/ecp"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/coseto6125/egent-code-plexus" that are relevant to the current task. Run `npx skills add "https://github.com/coseto6125/egent-code-plexus"` and select the relevant skills, then follow their instructions.