Verified Jun 4, 2026

Use the agentic setup without guessing.

This is the team SOP for the project-local ADW runtime installed in Codex. Start with the folder check, design with /workflow, turn the design into tasks, then execute and verify.

Visual map showing ADW moving from request to workflow spec, task plan, execution, and verification.

Project folder Open the folder that contains .agents, .codex, package.json, and CODEX_RESTART.md

Quick Start

Open Codex Desktop in the workspace folder.
Run the doctor command below.
Start new work with /workflow.

$env:CODEX_AGENT_ROOT=(Get-Location).Path
npm run adw:skills:doctor

Daily flow

Four steps every team member can follow

Describe the change

Use plain language. Keep it to one feature, fix, audit, or refactor.

/workflow add the billing status panel

Create the spec

ADW turns the request into file names, types, interfaces, and phases.

.agents/runs/<plan-name>/spec

Convert to tasks

Task orchestration creates tracked builder and reviewer tasks.

/task-orchestration convert-to-tasks <plan-name>

Execute and verify

Run tasks, complete them through the runtime, and verify before moving on.

/task-orchestration execute <plan-name>

Command menu

Use the right command for the job

`/workflow`

Best for a new feature, fix, or refactor that needs a real implementation plan.

/workflow build a local dashboard for Hermes profile setup status

`/task-orchestration`

Turns a spec into managed tasks, then executes the plan.

/task-orchestration convert-to-tasks <plan-name>
/task-orchestration execute <plan-name>

`/architecture`

Audits structure, boundaries, naming, types, observability, and test surface.

/architecture audit this folder for the full codebase

`/execution-integrity`

Checks runtime reliability, task lifecycle, recovery, and fragile handoffs.

/execution-integrity audit this folder for task lifecycle reliability

Team roles

Who does what

Role Responsibility Default command

Requester Explains the outcome and checks whether the finished work matches the need. /workflow

Builder Executes scoped tasks and records verified changes. /task-orchestration execute

Reviewer Looks for bugs, missing tests, weak boundaries, and regressions. tasks.ts complete

Operator Confirms the runtime is healthy and restart instructions are saved. npm run adw:skills:doctor

Checklist

Before calling a task done

Codex is opened in the correct workspace. npm run adw:skills:doctor passes. The work has a spec or a clear direct scope. Managed tasks are tracked in .agents/data/tasks.db when needed. Verification commands ran and results are reported.

Do

Keep requests small enough to review.
Use project-local skills under .agents/skills.
Save restart notes when setup changes.

Do not

Route this setup through VS Code unless the team changes the rule.
Edit .agents/data databases by hand.
Treat chat memory as task state.

Restart and handoff

Where the setup is saved

Restart note

CODEX_RESTART.md has the exact recovery and verification commands.

Usage guide

outputs/AGENTIC_SETUP_USAGE.md is the short text version of this SOP.

Runtime state

.agents/runs stores artifacts and .agents/data stores local DB state.

Troubleshooting

Fast fixes

Slash commands do not seem to work.

Run npm run adw:skills:doctor. The doctor checks global prompt shims, project prompt copies, skill files, contracts, and runners.

The agent is using the wrong folder.

Set CODEX_AGENT_ROOT to the workspace path, then reopen Codex in that folder.

VS Code opens unexpectedly.

This setup is scoped to Codex Desktop/chat. Search for launcher shapes like code, code.cmd, Code.exe, or workspace launch commands before assuming ADW caused it.

No tasks are listed yet.

That is normal before you create a plan. Start with /workflow, then run /task-orchestration convert-to-tasks <plan-name>.