Role Overview

STANDARDS divides work among nine roles. Each has a clear responsibility:

Role	What it helps you do
Scoper	Decide what to build and what counts as done.
Tester	Test the change and record what the results prove.
Architect	Resolve the technical design before coding.
Navigator	Understand the project or check your understanding.
Developer	Plan and implement the change with your approval.
Auditor	Establish the project facts the change depends on.
Reviewer	Get an independent assessment of the work.
Documenter	Keep documentation accurate and useful.
Synchronizer	Check that the work offered for sign-off matches what was assessed.

Their initials spell S.T.A.N.D.A.R.D.S.; this is not their running order. The workflow depends on whether the project is new or existing and whether the cycle uses standard, expedited, or documentation work. A cycle is one request, ending in your sign-off or cancellation.

Each role has eval cases describing expected behavior. The skill eval report covers an earlier run; the new completion-policy and documentation-cycle cases have not been run against a model.

Run a role

You choose when to run each role. Use $scoper in Codex or /scoper in Claude Code, replacing scoper with the role’s name. Each page below includes examples.

The saved workflow state determines which role can work next. At a handoff, the outgoing role saves its progress and gives you the next command; it does not automatically run it. Tester and Reviewer require separate assessment conversations.

Navigator is available at any point, even without an active cycle. It explains existing work without changing files or workflow state. For a standalone documentation assignment, Documenter can initialize the Brownfield route before handing off to Auditor; see Updating Documentation on Its Own.

Know what completion means

Each workflow role saves its work and checks it before moving on. These checks are its completion gate. If a problem belongs to another role, work returns to that role for correction. The recovery process keeps track of what must be repeated and where to return.

A role’s completion does not mean the whole change is accepted. You make the final sign-off decision. Expedited cycles run only Developer and implementation Reviewer; if they need a skipped role, the cycle must move to the standard workflow.

Standard cycles can also finish after implementation review when you choose that policy and Reviewer confirms that no required work remains. This keeps all standard steps through full testing and implementation review.

Files and setup

The role pages explain what each role produces. The templates define the required contents; ownership rules protect files from other cycles. In the paths shown here, <Active Work.Id> means the current cycle’s saved identifier.

See Installation and Setup for the installer command. The packages’ evaluation scenarios describe intended behavior, not proof of successful model runs.