What problem does it solve? Planning a non-trivial code change requires understanding execution flows, blast radius, and statement-level dependencies across a repository, which is slow and error-prone when done by hand. This Skill automates that investigation and produces a 13-section implementation-ready plan document that a follow-up implementation agent can execute without re-investigating the repository. ## Core Features & Use Cases - Graph-guided investigation: Uses GitNexus query, context, impact, and trace tools plus statement-level Program Dependence Graph slices to locate the symbols, callers, and tests a change touches. - Verified, provenance-pinned plans: Every cited claim is source-verified and pinned to a commit plus a versioned dirty-tree evidence digest, with claims tagged as verified, graph, inferred, or assumed. - Machine-readable context pack: Section 11 of each plan is a structured implementation context pack consumed by executor agents, and a Deepen mode strengthens existing plans in place through a descriptor-anchored safe reader/writer. - Use Case: Run "/gitnexus-plan Add retry support to the ingestion pipeline" to receive a dated plan under docs/plans/ with proposed changes, test scenarios, risks, and verification commands. ## Quick Start Ask the agent to run gitnexus-plan for your task, for example: create an implementation plan for fixing the stale warm-cache invalidation bug in exportedTypeMap.
