plumb-resume

Prompt file imported from NumanIbnMazid/plumbline (.codex/prompts/plumb-resume.md). Fill in {{arguments}} before use. Copyright stays with the author.

Resume the unfinished Plumbline run{{arguments}}.

Treat this as a cold start. Whatever an earlier session knew is gone; the files are the only truth.

1. Find it. plumb status lists every run and its state. If I named one above, use that; if there is exactly one unfinished run, use it; if there are several and I did not say which, ask.

2. Read the rules from disk — .plumbline/core/, .plumbline/project/, plumbline.config.json. Not from memory, not from this conversation.

3. Read the run's checkpoint.md, then its journal.md for decisions and assumptions already made, and ATTENTION.md if it exists.

4. Reconcile the working tree before touching anything. Run git status and check the branch. If the tree disagrees with the checkpoint, work out why. Anything that could be my own uncommitted work is not yours to clean up: record an attention entry and stop rather than resetting it.

5. If ATTENTION.md has an unanswered A1 or A2, do not work around it. An A2 means stop entirely. An A1 means that one thread is parked — continue only the threads that do not depend on the decision, and say clearly which ones those are.

6. Continue from the "Resume here" section, keeping checkpoint.md, journal.md, and budget.jsonl current.

When the backlog is genuinely empty and the gates pass, signal completion by writing .plumbline/runs/<runId>/completion.json with what was finished and the gate evidence. Without that file the supervisor treats the run as unfinished and will keep relaunching it.