Workflows catalog

Workflow files drive the runner phase loop (workflowPath on each job). Paths below are relative to the materialised _intelligence/ root.

job — STANDARD implementation lane

Path: workflows/job/workflow.md

Phases (spec-writing → planning → coding → review → evaluation), each optionally interactive_checkpoint: true; coding declares the code-reviewer subagent.

• spec-writing uses tier: coding (typically Sonnet-class models). The spec-writer posts feature-spec.md via post_artifact({ kind: "spec-md", … }).
• overrides.jira.initial_phase keeps tracker-triggered jobs on spec-writing; there is no CLI override that skips spec-writing in the base layer.

job-fast — FAST lane

Path: workflows/job-fast/workflow.md

Phases: planning → coding (with code-reviewer) → review-and-verify (combined reviewer + verification responsibilities).

Planner must set params.lane = fast via switch_workflow before this file executes.

job-deep — DEEP lane

Path: workflows/job-deep/workflow.md

Phases: spec-writing → analysis → planning → coding (code-reviewer) → review → qa → evaluation.

DEEP runs spec-writing for CLI jobs too — the analysis phase needs a concrete spec, not a one-line CLI description. Spec-writing uses tier: coding like STANDARD.

campaign

Path: workflows/campaign/workflow.md

Phases: campaign-architecture → campaign-planning → coordinating (agent-less dispatcher) → campaign-integration → aggregation.

self-update

Path: workflows/self-update/workflow.md

Internal bookkeeping workflow for automated intelligence proposals — tracking phase only, agent: null, waits on PR merges without an LLM phase loop.

memory-curator

Path: workflows/memory-curator/workflow.md

Single phase curating (agents/memory-curator.md) flagged interactive so humans approve destructive memory edits.

---

Lane switching

Agents call switch_workflow({ workflowPath, reason, paramsPatch?, toPhase? }) to hop between job, job-fast, and job-deep. Promoting to campaign uses convert_to_campaign which rewrites workflowPath internally.