Core Concepts

Workflows

Process playbooks for common task types.

Workflows live in .agents/workflows/*.md and describe repeatable ways to approach common tasks such as planning, implementation, debugging, review, testing, preview, and deployment.

They encode process, not domain knowledge.

A workflow is not a CLI command. In practice, you either let Codex route to it through AGENTS.md or you ask for it explicitly in your prompt.

Workflow Selection

Classify the request before loading extra skills or spawning subagents.

Once the task shape is clear, choose the narrowest workflow that matches it.

How To Invoke A Workflow

Let Codex route automatically from the request and the rules in AGENTS.md.
Or name the workflow explicitly in your prompt, for example: Use the plan workflow before making changes.
Use workflows as execution modes or playbooks, not as shell commands.

Shipped Workflows

brainstorm
check
create
debug
deploy
enhance
orchestrate
plan
preview
review
ship
status
test
ui-ux-pro-max
verify

Validation Tiers

Use check for normal development and narrow changes.
Use verify for release-sensitive, deployment-affecting, or cross-cutting work.
Use test when test execution or test authoring is the main objective.
Promote from check to verify when release risk is non-trivial or validation signal is weak.