Workflows

Workflows describe phase order, assigned agents, tiers, checkpoints, subagents, and optional overrides for tracker-triggered launches. Markdown narrative explains intent; YAML frontmatter is machine-readable for the harness.

The four headline shapes

Name	Canonical path intent	Typical use
job (STANDARD)	workflows/job/workflow.md	Balanced automation: tracker spec writing, planner decomposition, coder + reviewer, merge gatekeeping, evaluator closure.
job-fast (FAST)	workflows/job-fast/workflow.md	Very small deltas with tight FAST signals (~few files, no new public surface, trivial rollback). Compresses redundant reviews but still honours SCM policy.
job-deep (DEEP)	workflows/job-deep/workflow.md	Elevated-risk work: introduces analyzer design notes earlier and QA after merge verification; more tool budget per phase by design.
campaign	workflows/campaign/workflow.md	Tracker-scale features fanning across multiple repos or issues with explicit cross-contract management.

When the Planner switches lanes

During planning, the Planner may call switch_workflow whenever the inspected repository contradicts the caller’s lane guess—for example FAST was requested but migrations or new endpoints appear—or when params.lane coming from upstream (such as campaign child registration) must be honoured verbatim.

Lanes are orthogonal to language: FAST vs STANDARD vs DEEP governs rigour and which agents activate; conventions come from Skills.

Incorrect classification is recoverable mid-flight (e.g. coding escalates complexity into DEEP) and stays auditable via workflowPathHistory carried on the Job object.

STANDARD job phase overview

1. spec-writing — Structured feature spec (spec-writer, coding tier). Runs for all CLI and plan-mode jobs as well as tracker-triggered ones: the agent reads params.description (or the ticket via tracker_get_issue), writes feature-spec.md, and registers a spec-md artefact. Only the tracker-read and tracker-comment steps are skipped on non-tracker jobs.
2. planning — Work items plus lane sizing (planner).
3. coding — Implementation + bundled code-reviewer subagent (coder).
4. review — Human SCM workflow (pr-reviewer).
5. evaluation — Merge verification plus wrap-up responsibilities (evaluator).

FAST merges some responsibilities (see its workflow prose for nuances); DEEP inserts analysis before planning and activates downstream QA tooling.

Detailed YAML and override keys are enumerated in Workflow reference.