Agent skill · software engineering · abhigyanpatwari
gitnexus-plan
Use when you need a deep, implementation-ready engineering plan for a code change — built from GitNexus graph intelligence, statement-level PDG analysis, and targeted source verification, compact enough that an implementation agent can start without re-investigating. Also strengthens existing plans via Deepen mode. Examples: "/gitnexus-plan Add retry support to the ingestion pipeline", "/gitnexus-plan deepen docs/plans/<plan>.md", "plan this change using the knowledge graph".
Why this skill is useful
Adds a comprehensive, executable planning framework that integrates with GitNexus for generating implementation-ready engineering plans.
What it needs
Requires gitnexus installed locally. About 11k tokens when loaded. Last updated 2026-08-06. 45,147 stars on the source repository.
What this skill does
gitnexus-plan — implementation-ready engineering plans Produce an implementation-ready plan for an engineering task. GitNexus is the navigation layer (where to look), statement-level PDG is the constraint layer (what gates and feeds the behavior), and your native targeted source reads are the verification layer (what is actually true right now). The output is a plan document plus a compact, machine-readable implementation context pack that a follow-up implementation agent (gitnexus-work, or any executor) can consume without repeating the investigation. This skill plans. It never implements. Do not modify production code, tests, or configuration while running it. The only repository file it writes is the plan document (a working ledger kept outside the repo is fine). The only other permitted state change is an index refresh via analyze --index-only, which writes only the .gitnexus index store. It must not build analyzer dist/ output and must not mutate source, tests, configuration, or evaluation data. Stale analyzer provenance is disclosed as a source-weighted limitation, never repaired by a planning run. Hard rules Ledger first. Before every GitNexus call and every repo file read, check the context ledger. Never repeat a query or reread an unchanged range that already answered the same question (allowed repeats are defined in references/context-ledger.md; this skill's own reference files are exempt from ledger bookkeeping). Every graph query answers a named planning question. Record the question and the conclusion in the ledger. No exploratory dredging. Source beats graph. The graph navigates; current source is authoritative. Verify before asserting (see Phase 4). Comments are the weakest evidence — never stronger than executable code. No fabrication. Never invent symbols, filenames, test names, tool results, or PDG edges. Unknowns go to Assumptions and Open Questions. No scope creep. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills abhigyanpatwari/gitnexus-plan--e876a5