writing

name	writing
description	Outline, approve, draft, and deliver a written artifact.
disable-model-invocation	true
argument-hint	<task>

Writing pipeline

Use this pipeline when the deliverable is prose for humans — a document, guide, note, or announcement — rather than code. The outline is the plan: it carries the approval gate, and the draft must not silently outgrow it.

Task: $ARGUMENTS Record harness as claude in the run ledger.

1. Intake

Clarify the requested outcome from available context. Inspect the repository before asking questions that the files can answer. Create the run folder and write task.md containing the outcome, constraints, assumptions, and acceptance checks. Reserve an empty evidence/ folder.

2. Outline

Write outline.md in the run folder. State the audience, the job the document does for that audience, and the intended destination path. Lay out the structure section by section with one line on what each section must accomplish, and note voice and length constraints. Keep the outline strong enough that another capable agent could draft from it.

Gate: plan-approval

STOP after completing this stage. Do not execute until the user explicitly approves the written plan. Request the verdict by writing approvals/plan-approval.md.request in the run folder describing what needs approval, then stop. The verdict is recorded from outside the session: base approve <run-slug> plan-approval (or --deny) writes approvals/plan-approval.md — a standing directive counts only when recorded that way, with --note citing it. Never create the verdict artifact yourself. If the recorded verdict is denied, skip to record with outcome aborted.

3. Draft

Write the deliverable following the approved outline: working copy in the run folder, delivered to the destination path named in task.md. Where the draft must deviate from the outline, deviate and record why in result.md. Before presenting, reread the piece cold — as its audience, without the conversation in mind — and revise whatever does not survive that read. Capture the final path(s) in result.md.

4. Record

Always run this stage, including after rejection, failure, or abort. Append exactly one compact JSON object line to .base/history.jsonl with slug, date, pipeline, harness, outcome, and paths. Use completed, aborted, or failed for outcome; never rewrite previous lines.