Most days you write an intake and send one prompt path to the orchestrator. It bootstraps the job, honours any gates you enabled, and runs the pipeline. Grab a prompt below.
Create a jobSend the orchestrator a single prompt path — you do not need to paste the file. Copy a path below, paste it to your coding agent, done. New contexts (e.g. audit) get added here over time.
The single main-flow prompt. Discovers your intake in jobs/0_new/, bootstraps the job, and runs the pipeline. Also the prompt you re-send to resume after any gate.
_processes/02_orchestrator/orchestrator.prompt.mdFirst-run bootstrap. Inspects the host project and writes a contract-valid app.md plus config.json. Run this once before any other prompt on a new host.
_processes/00_app/app-init.prompt.mdRe-probes host facts and available runtimes, then rewrites app.md / config.json. Run it when the stack or tooling changed.
_processes/00_app/app-update.prompt.mdCreates/refreshes the host root CLAUDE.md (the real file) + AGENTS.md (symlink to it).
_processes/00_app/claude-agents-md-files.prompt.mdjobs/0_new/ by hand, or use the
intake form — open it as a file, or run the optional local helper app for one-click Create job + a dashboard (see Running the local app).
Standalone action types (D-45, D-48) that run their own logic instead of the staged pipeline. Drop a matching intake in jobs/0_new/ and send the orchestrator path above — it routes by type — or run the action prompt directly.
Whole-app or scoped report (security / find_issues / doc_drift / revalidate / custom), run as a per-kind 3-phase orchestrator. Writes a findings report, no code; report_fix mode also drops a follow-up feature intake.
_processes/03_action/audit/audit.prompt.mdParallel fan-out: one sub-agent per independent fix, joined and validated, then commit/PR per the job's Git config.
_processes/03_action/quick_fix/quick_fix.prompt.mdGovern an existing HTML docs folder against the code + UI kit (doc_upkeep), or generate new docs for a section or the full app (doc_create). See Documentation.
_processes/03_action/doc_upkeep/doc_upkeep.prompt.md
_processes/03_action/doc_create/doc_create.prompt.mdValidate externally-supplied code-review comments against the whole app, then fix only the verified-accurate ones in the working tree (untrusted-input posture; no commit/PR). Comments come from the mandate or a CommentsFile; the per-comment verdict lands in 09_action/action-report.md. See Code-review fix.
_processes/03_action/codereview_fix/codereview_fix.prompt.mdManual queue-management / recovery prompts. Most days you do not need these — the orchestrator advances jobs itself.
Add stages (plan / execute / test / document / review / validate) to a job and move it back to 2_ready/ in one pass.
_processes/_operations/extend/extend.prompt.mdManually advance a job between queues. Only needed for recovery; with the default after_creation: no the orchestrator advances 1_creation → 2_ready itself.
_processes/_operations/promote/promote.prompt.mdThe copy blocks on this site render paths to match where these docs are being served from, so you can paste them as-is. Viewed from the standalone workflow repo, they show the workflow-internal form (bare _processes/...) — what you paste when your session's cwd is _code_workflow/. Viewed from a _code_workflow/ install inside a host project (so the host's own CLAUDE.md / AGENTS.md auto-loads with full project context), the same blocks render the full _code_workflow/... form for paste from the host root.
Both modes work identically; agents likewise detect which mode they are in and emit subsequent next-step paths in the matching form. See How to use → Two invocation modes and the canonical rule _processes/_shared/handoff-paths.md.
| Step | What you do |
|---|---|
| 1 | Put an intake in jobs/0_new/. Copy jobs/0_new/_new.md or use the static intake form. Free-form prose is fine. |
| 2 | Send the orchestrator prompt path (above). It discovers the intake, bootstraps the job, and runs the pipeline (D-41). |
| 3 | Optional: set after_creation: yes in the intake to have the orchestrator pause in 1_creation/ so you can review the generated job, then re-run on the slug. |
| 4 | Resume with the orchestrator after any gate — re-send the same path. |
Task-oriented pages for everyday work, plus the deep reference.
Default path for normal work: intake, creation/bootstrap, auto-advance to ready, orchestrate. Creation review is opt-in with after_creation: yes.
Run the orchestrator, resume after gate stops, and understand slug selection.
Continue a brainstorm-only job into plan, execute, test, document, validate.
Fresh host setup (app-init), drift re-validation (app-update), app.md, and config.json.
How the document stage works and where project documentation rules come from.
Missing setup, stale lock, runtime gaps, version mismatch, and queue conflicts.
The complete how-to-use guide.
How the workflow is built and why.
Each stage, in order.
Defaults per request type.
The JOB.md / app.md contracts.
Every type — purpose, flow, logic, and fields — with visual flow diagrams.
Host-authored app-local types (D-74) — how a project adds its own, no repo commit.
All deep docs in one place.
Intake drafts
Generated job (review-staging)
Approved pickup
Running / paused
Complete
Explicitly cancelled jobs
Stages run in order; review is off by default. Disabled stages are skipped.
| # | Stage |
|---|---|
| 01 | clarify |
| 02 | brainstorm |
| 03 | plan |
| 04 | execute |
| 05 | test |
| 06 | document |
| 07 | review (off by default) |
| 08 | validate |