Status scaffold – nothing here is drafted · Life living · Reader you, about to plan delivery so an agent can be handed a brief

How to plan delivery so an agent can be handed a brief¶

a plan of slices and features, each with the proof that closes it, and a packet an agent can be given as its whole brief

The worked example throughout is the example system.

What is in this folder¶


This guide	What the process is, why it is shaped this way, and what good output looks like. Written for you
`prompt.md`	The instruction set to paste into an agent session. Written for the agent
`templates/`	Skeletons for every file the process produces. Copy the directory

Read this once. Use the prompt every time.

Draft order: 2nd. See PLAN.md section 10.

[the artefact, and what it is for. If it is a document written to open a conversation rather than close one, say so here]

[figures, dated, re-read from source. Or "not measured" said plainly]

[the sections, as a map, with what happens in each]

Agent … · You …

[what to do]

Worked example.

[the actual thing, on the example system]

Agent … · Participant … · You …

These are yours to run, on the agent's output. Do not ask the agent whether its own work was good.

[the gaps, the proxies, the principles still unmet]

platform/plan/README.md — the delivery record, and the workflow-selection table.
platform/plan/model.md — the rungs, the who-says-it-is-done definition, and the delegation measurement.
platform/plan/workflows/*.yaml — the templates, with per-column delegation blocks, entry, produces, exit and human gates.
platform/plan/tree/ — the leaves.
redmoor_docs/delivery/README.md — the sprint docs, the ID chain, and the note about four disagreeing copies.
redmoor_docs/delivery/journals/ — per-feature delivery journals.