Resume and execute a documentation job's phased roadmap. Discovers spec/{slug}/TECH.md from the current feature/fix/refactor branch, reads the FSM via next_phase.py, authors the next phase (default one at a time), runs that phase's verify command (mkdocs --strict + nav/render checks), updates state via set_phase.py, and makes one atomic content+state commit. May amend TECH.md freely as reality dictates; only a GOAL.md contradiction forces a stop. The resume-and-write driver of the documentation factory (see .agents/factory/methodology.md).
Start a new RCAC-Docs documentation job (feature/fix/refactor) from a clean main branch. Safety-checks the tree, derives a {slug}, creates feature/{slug} | fix/{slug} | refactor/{slug}, ingests an inline prompt or an untracked GOAL.md, and refines it into spec/{slug}/GOAL.md — appetite, non-goals, EARS acceptance criteria with stable R-IDs, resolved clarifications. Shaping only: no deep research, no drafting of pages. The first step of the documentation factory lifecycle (see .agents/factory/methodology.md).
Turn a shaped spec/{slug}/GOAL.md into a design and a phased roadmap. Runs an invariant gate against AGENTS.md, fans out read-only research subagents (scaled to appetite; existing-site-first), synthesizes spec/{slug}/PLAN.md, re-checks invariants, and generates spec/{slug}/TECH.md — the phased YAML-FSM driven by /docs-draft. Second step of the documentation factory (see .agents/factory/methodology.md).
Land an approved documentation branch on main. Default: push the branch and open a squash PR to main with a rich, artifact-linked body (Summary/Goal/Design/Research/Phases/Verification). Alternative (local): squash-merge into main locally. Confirms before any irreversible/outward step; never targets dev. NOTE: merging to main auto-deploys to production (Geddes) within ~5 minutes — this is the one irreversible, outward step. Final step of the documentation factory.
Adversarial QA of a completed documentation branch. Delegates the correctness pass to a FRESH reviewer subagent that sees only GOAL.md + the branch diff + the invariants + the style guide + the runnable repo — NOT PLAN.md/TECH.md (avoids grading-its-own-homework). The reviewer verifies by building (mkdocs --strict), rendering, and checking links/nav/front-matter/a11y; classifies each finding CONFIRMED (machine-checked) or PLAUSIBLE (HPC accuracy / prose a11y → human). CONFIRMED findings loop back to /docs-draft; high-impact files force a human gate. Fourth step of the documentation factory (see .agents/factory/review-rubric.md).