godmode

godmode-code-of-law

Use at the start of every session and before every new task - read GODMODE-CODE-OF-LAW.md at the project root when it exists (the project's generated Code of Law; `godmode law compile` writes it), and follow its guards before acting.

godmode-continuity

Reconstruct and preserve private project continuity from local evidence. Use when resuming work, changing branches or worktrees, detecting drift, recording handoffs, or explaining why context is missing or stale.

godmode-governance

Preview and govern protected engineering actions without executing them implicitly. Use before destructive, externally visible, history-changing, database-changing, release, credential, branch, or worktree operations.

godmode-investigation

Diagnose technical failures with reproducible evidence and bounded hypotheses. Use when a bug, regression, test failure, build failure, performance problem, or repeated unsuccessful fix needs root-cause investigation.

godmode-repair

Re-pitch an answer that did not land, and record why it did not. Use when the operator says they do not follow, asks for clarity, repeats a question already answered, or asks what is being waited on.

godmode-skill-forge

Create an original, compact project skill after a repeated capability gap is proven. Use when at least two real tasks need the same missing workflow and existing skills do not cover it reliably.

godmode

Coordinate local context continuity, evidence, and guarded coding workflows. Use when starting or resuming substantive repository work, when current reality is uncertain, or when a request spans multiple Godmode capabilities.