/gitnexus-work

name: gitnexus-work
description: 'Use when executing an engineering plan produced by gitnexus-plan (or a small bounded task directly) — implements step by step with GitNexus impact checks before every symbol edit, tests from the plan''s scenarios, and detect_changes gating every commit. Examples: "/gitnexus-work docs/plans/2026-07-11-gitnexus-plan-ingestion-retry.md", "/gitnexus-work" (latest plan), "execute the plan".'

gitnexus-work — execute a gitnexus-plan

Execute an implementation plan produced by `gitnexus-plan`, shipping it as a sequence of verified, atomic commits. The plan's section 11 (`implementation_context` pack) is the primary machine-readable input; the prose sections are its rationale. This skill **does** edit code — it is the executor counterpart to the planning-only `gitnexus-plan`.

/gitnexus-work <plan path>        # execute this plan
/gitnexus-work                    # newest docs/plans/*gitnexus-plan*.md here
/gitnexus-work <small task text>  # direct mode, see Input triage

Input triage

• **Plan path** (or blank → the newest `docs/plans/*gitnexus-plan*.md` under

the current repo root): the normal mode; continue to Phase 1. Schema-2 plans have a normalized repo-relative `docs/plans/YYYY-MM-DD-gitnexus-plan-<3-5-word-slug>.md` `generated_plan_path`. Resolve only a lexical candidate, then invoke `scripts/evidence-provenance.mjs read-plan --repo <root> --generated-plan <candidate>` and load only the exact bytes in its descriptor-anchored receipt. Require the receipt's canonical repo-relative path to equal the document's `generated_plan_path` byte-for-byte; reject an external, escaping, differently scoped, or mismatched value. A plan in another target repo may still be passed by explicit path. If Phase 1's pre-completed check finds every §7 step of the newest plan already landed, stop and ask instead of re-executing it.

• **Bare task text**: trivial and bounded (1–2 files, no architectural

decisions) → implement directly with the same discipline: `impact` before every symbol edit, minimal change, tests when behavior changes, verification commands taken from the repo's own scripts (package.json / CI), `detect_changes` before every commit, and the shared Build-current/index-current procedure before graph-dependent impact and final verification. Anything larger → recommend running `/gitnexus-plan` first; honor the user's choice if they decline.

Phase 1 — Load and re-anchor the plan

1. Resolve the target repo and normalized plan candidate, then invoke this skill's descriptor-anchored `scripts/evidence-provenance.mjs read-plan` command exactly as specified in `references/evidence-provenance.md`. Reject a missing, external, escaping, symlinked, or differently scoped path. Decode and read the receipt's exact `plan_bytes_base64` completely; never read or reopen the lexical path directly. It is a decision artifact, not a script: scope boundaries and `avoid` entries bind you; exact code is yours to write. Retain the receipt's canonical `generated_plan_path` and `plan_digest` in session state. Never edit the plan body. 2. Parse the §11 `implementation_context` pack: `acceptance_criteria`, `evidence_provenance`, `primary_symbols`, `related_symbols`, `files_to_modify`, `execution_path`, `pdg_constraints`, `architectural_patterns`, `tests`, `verification_commands`, `risks`, `assumptions`, `open_questions`, `avoid`. Compact plans carry the mini-pack subset — absent optional fields are empty, not errors. `evidence_provenance` is mandatory: absence or schema 1 means a legacy plan, not a clean tree. Before relying on it, require exact byte-for-byte equality between the read-plan receipt's canonical `generated_plan_path` and `evidence_provenance.generated_plan_path`. 3. **Two-layer drift check — always recompute.** Even when current HEAD is the same HEAD as the plan pin, recompute both the canonical global dirty digest and the sorted cited-path manifest. Read `references/evidence-provenance.md`, then invoke this skill's `scripts/evidence-provenance.mjs` with the plan's exact `generated_plan_path`, every cited manifest path, and schema version 2. Never recreate its bytes in shell or prose. Schema 1 cannot be recomputed unambiguously and requires conservative re-anchoring. Include object kind plus HEAD/index/worktree/untracked layer digests, and classify `staged`, `unstaged`, `untracked`, `deleted`, `renamed`, `mixed`, and `absent` evidence. Honor the generated-plan exclusion exactly; do not exclude all plans. 4. **Re-anchor on either mismatch.** Missing or legacy provenance, a HEAD mismatch, or a global dirty digest mismatch requires a conservative re-anchor before work:

• Diff every cited-path manifest entry. Changed cited paths — including

staged-only, unstaged-only, deleted, both rename endpoints, mixed staged+unstaged, and disappeared untracked paths — get their cited ranges re-read before reliance.

• Compare the current whole-tree dirty set with the pinned global digest.

New uncited dirty paths get a scope assessment: determine whether they overlap the plan, requirements, tests, or a key technical decision; do not silently ignore them merely because they are uncited.

• Unreadable or unclassifiable cited evidence blocks every dependent step

until it can be restored, read, or resolved with the user. Never substitute an invented digest or treat absence as an empty file.

• Keep the re-anchor result in session state; never mutate the plan body.

Use Deepen only if reconciliation invalidates scope, requirements, a key technical decision (KTD), or the planned implementation seam. Ordinary byte drift that leaves those decisions valid is re-verified locally. 5. **Re-verify `assumptions` cheaply** (each one names what to check). A failed assumption is a stop-and-replan sig