Plan, review, build, precommit, decide, commit.

This is the operating procedure to give AI-assisted work a real engineering trail. Use it when the change matters enough to explain later.

One-command-at-a-time SOP

Plan to commit

> almightygpt plan --topic checkout-hardening --text "tighten checkout flow"> almightygpt review --plan docs/claude-plans/checkout-hardening.md --reviewer codex --topic checkout-plan> npm test> almightygpt review --diff --worker claude --reviewer codex --topic checkout-hardening> almightygpt precommit --strict> almightygpt decide latest --status approved --note "ready to ship"> git commit -m "Harden checkout flow"

What each stage proves

Plan

The Worker turns a requirement into a durable plan before code momentum starts.

Review the plan

The Reviewer checks the approach before implementation risk compounds.

Build and test

The human or Worker changes code, then local tests prove basic behavior.

Review the diff

A separate provider reviews the actual change and must produce concrete findings.

Precommit

Gemini runs the last-mile check over the uncommitted diff.

Decide

The human records approved, needs_changes, rejected, or deferred.

Commit

The change and the readable decision trail enter git together.

Artifacts to look for

Plan

docs/claude-plans/<topic>.md

Plan review

docs/codex-reviews/plan-<topic>.md

Diff review

docs/codex-reviews/<topic>.md

Precommit

docs/precommit-reviews/precommit-<timestamp>.md

Decision

Human Decision section inside the review artifact

Commit policy

Commit human-facing Markdown artifacts when they explain a decision. Do not commit raw `.almightygpt/runs/` machine folders unless your team has intentionally changed that rule.