Run a trace-driven, source-backed bug discovery and produce a self-contained discovery document plus a proposed plan. Invoke explicitly with /nehir-bug-discovery when a runtime symptom needs investigation before any code change.
BEFORE writing fixed, works, resolved, bug found, confirmed, verified, root cause, or another success/root-cause claim in an answer, document, changeset, commit message, or worker handoff. Separates observed facts, hypotheses, mechanical validation, user…
BEFORE writing or updating a discovery, plan, completed write-up, ticket, or other durable document that records a runtime bug, finding, or decision. Checks for ephemeral references, machine-specific paths, unanchored relative language, unsupported claims,…
Re-open an investigation after an attempted fix failed and the user captured a new trace from a build containing that attempt. Invoke explicitly with /nehir-retry-with-new-trace when the symptom survived the change.
Record what actually landed on main after a change was reviewed and merged — prove the merge, capture the landed state including deviations and leftovers, then update and move the affected documents on the plans branch. Invoke explicitly with…
Set up one isolated implementation lane and hand it to a worker with the project's discipline fences attached. Invoke explicitly with /nehir-delegate-lane when a well-specified cluster of work should run in its own worktree.
Finalize a Nehir change — produce or update the Changesets fragment and prepare the commit message — without performing any unauthorized git mutation. Invoke explicitly with /nehir-finalize-change once the implementation is done.
BEFORE any git mutation—stage/add, commit, push, amend, reset, restore, revert, stash, rebase, merge, branch creation/switch/deletion, tag, or git rm. Each mutation requires explicit user permission for that exact action; one permission never implies the next.