Extend an existing job

Use this when a job is already done or in flight and you want to add more stages without losing the audit trail.

Copy this for brainstorm-to-build

Extend operation

_processes/_operations/extend/extend.prompt.md

Two invocation modes — copy blocks show the workflow-internal path; prefix with _code_workflow/ when your cwd is the host project root. See How to use → Two invocation modes.

When to use extend

Use extend

The brainstorm was the first phase of this same work. You want one job history and the orchestrator should skip already-complete stages.

Create a child job instead

The old brainstorm is just a reference for a separate implementation effort. Start a new intake and cite the parent artifact.

Common invocations

Paste the extend prompt path, then add a slug or stage list in prose when you already know the exact request.

Extend operation prompt

_processes/_operations/extend/extend.prompt.md

Examples of extra request text: <slug> or <slug> add plan, execute, test, document, validate.

What extend changes

Rebuilds JOB.md → ## Stages to the current schema.
Adds per-stage config for newly enabled stages.
Adds expected artifacts for those stages.
Updates the informational Status line.
May update approval gates (before_commit / before_pr) after explicit user confirmation.
Moves the folder back to 2_ready/.
Appends audit notes to PROGRESS.md.
Authors a separate operation_record job born complete in jobs/4_done/ as the audit trail for the extend run.

What it does not do — it does not rewrite the mandate unless you explicitly opt into an extension note. It does not mark stages complete. The orchestrator still owns stage progress.

After extend

Run the orchestrator. It reads PROGRESS.md, skips stages already marked [x], and starts at the first newly pending stage.

Orchestrator

_processes/02_orchestrator/orchestrator.prompt.md