Codex Workflow

by Queopius

Build with autonomy. Advance with evidence.

A controlled workflow layer for AI-assisted software development.

Plan
Implement
Validate
Review
Gate

No valid gate. No next phase.

CW gives Codex bounded room to implement while keeping advancement under a deterministic supervisor. Plans are explicit, implementation and review use separate agents, validation runs before approval, and every next phase depends on verified gate evidence.

New workflows also declare what evidence would prove the product-level goal. After authorized phase work finishes, an independent completion review either records final evidence or proposes the smallest coherent extension for explicit human authorization.

Quick start¶

Run these commands from a Git repository after installing CW:

Create and run a controlled workflow

cw init
cw plan --goal "Implement subscription billing"
cw plan show
cw plan approve
cw

The final cw command starts or resumes the current phase. CW does not silently run every remaining phase; use a bounded cw run request when you intentionally want more than one gated phase.

Choose your path¶

Start with CW Install CW, initialize a repository, approve a plan, and run your first phase. Understand CW Learn the lifecycle, state transitions, independent review, and gate invariants. Operate CW Follow live execution, inspect runs, use bounded batches, and manage integrations. Recover safely Diagnose symptoms, understand error codes, and reconcile state without discarding evidence. Use governed MCP Inspect CW or request one of four controlled actions without exposing shell or filesystem access.

What makes progression trustworthy¶

Control	What it guarantees
Explicit plan	Implementation cannot rewrite its own acceptance criteria.
Deterministic validation	Required commands and artifact checks run before semantic review.
Independent reviewer	A separate read-only Codex process evaluates current-phase evidence.
Verified gate	Artifact hashes and review evidence must validate before advancement.
Fail-closed state	Contradictory cached state and gate evidence stop normal execution.

Find the command you need

Use the CLI reference for concise syntax, options, and examples validated against the source parser.

When every authorized phase has a valid contiguous gate chain, planned scope is complete and no further implementer is launched. Contract-aware projects become semantically COMPLETED only after valid completion evidence; legacy projects retain their existing completion behavior.

All valid gates. No next phase.

CW product website · Source repository