Markdown intake
Copy jobs/0_new/_new.md to a sibling file, fill in the request, then save it under jobs/0_new/.
Create a new job
The default operator path: turn a new request into a structured job, then hand it to the orchestrator.
Copy this most days
Orchestrator
_processes/02_orchestrator/orchestrator.prompt.md
Two invocation modes — copy blocks show the workflow-internal path (bare
_processes/...); prefix with _code_workflow/ when your cwd is the host project root. See How to use → Two invocation modes and _processes/_shared/handoff-paths.md.
1. Write the intake
Put exactly one new intake file under jobs/0_new/ when possible. The orchestrator's creation/bootstrap step (D-41) accepts free-form prose and infers the structure.
Form intake
Open the intake form, fill it in, then save or copy the generated markdown into jobs/0_new/.
Feature only — KISS mode (D-77, on by default since D-83). For
Feature, the form shows a pre-ticked Enable KISS Mode — POF / POC / MVP checkbox below the mandate — the feature preset declares KISS on, so a default feature job is born in KISS posture. When selected, the build stages seek the smallest correct implementation and proportionate verification; review and validate stay independent and evaluate both missing protection and unjustified complexity against concrete risk. Existing controls may be simplified only through the evidence-based rule in the shared directive. Un-tick it to opt out — nothing is emitted, and creation derives the flag solely from a positive intake block, so the preset never resurrects it. See Feature — the fields.
2. Run the orchestrator
Send the orchestrator prompt path to a fresh coding-agent session — it discovers the intake in jobs/0_new/ and runs its creation/bootstrap step (D-41; there is no separate creation prompt). Add an explicit intake path such as jobs/0_new/<file>.md after the prompt path when there are multiple drafts.
Default
_processes/02_orchestrator/orchestrator.prompt.mdWhat the creation/bootstrap step writes
jobs/1_creation/<slug>/JOB.md— the mandate and workflow config.jobs/1_creation/<slug>/PROGRESS.md— initial resume state.jobs/1_creation/<slug>/note.md— root continuity notes, seeded with the empty state.jobs/1_creation/<slug>/key-findings.md— root durable findings, seeded with the empty state.jobs/1_creation/<slug>/00_intake/<source filename>— the original request.- An optional Git branch when
Git → Create branch: yes.
3. Review the generated job (optional)
By default (after_creation: no) the orchestrator does not stop — it advances the job through the pipeline automatically (D-41). To review the generated JOB.md first, set after_creation: yes in your intake; the orchestrator then stops in 1_creation/ and you re-run it on the slug when happy.
| Check | Why it matters |
|---|---|
| Type / preset | Controls default stages and gates. |
| Stages | Pipeline jobs list all eight stages; disabled ones carry (disabled). Action-layer types (audit/quick_fix/doc_upkeep/doc_create/codereview_fix) have no ## Stages block (D-45, D-48). |
| Approval gates | These are the deliberate human stop points. |
| Git | Branch, commit, and PR behavior must match what you want. |
| Mandate | This is what downstream agents treat as the job. |
| KISS mode | Present on a feature job unless you un-ticked the box (D-77; on by default since D-83). ### KISS mode / - Enabled: yes first under ## Per-stage config puts the whole build flow in POF / POC / MVP posture; an absent block means off — there is no Enabled: no form. |
4. Continue (only if you set after_creation: yes)
If you opted into the review pause, re-run the orchestrator on the slug after reviewing — it advances 1_creation → 2_ready → 3_ongoing and runs the pipeline. With the default after_creation: no, none of this is needed. For non-standard / recovery queue moves, the promote operation agent is still available.
Re-run orchestrator
_processes/02_orchestrator/orchestrator.prompt.mdPromote (manual / recovery)
_processes/_operations/promote/promote.prompt.md