Wrap-up

Close the day so the documents remain the single source of truth and nothing the session did is lost or overclaimed. This is the user-invoked face of the collection's update mode; the full editing philosophy lives with the mvp skill (skills/mvp/references/editing-rules.md in the source repo). The operative rules are inlined below so this skill stands alone wherever it's copied.

Steps

1. Read the roadmap in full (and the PRD, if any decision changed this session). It is the shared memory; do not work from recollection of it.
2. Diff reality against the roadmap. Four buckets: work landed but unticked; ticks proposed earlier but unconfirmed; open questions the session resolved; decisions that changed.
3. Propose ticks — evidence or nothing. One line of executed evidence per candidate: a command that ran, a green CI run URL, a commit hash. Your own assertion that code "should work" is not evidence. Where the session's artifact is runnable, offer the user the exact steps to run it themselves before confirming — hands-on beats reading evidence. A tick that completes an epic must include the regression checks named at its kickoff, run and passing; checks named but never written are surfaced as an unfinished story (build them via /regression), never silently dropped. Ask confirm-all / pick / none via the structured question tool (plain-text lettered fallback elsewhere). The user is the verifier of record.
4. Tick confirmed boxes only — - [ ] becomes - [x]; nothing else on the line changes. Mis-scoped stories are a separate, explicitly-narrated edit, never folded into a tick.
5. Apply non-accretive updates. Changed decision → rewrite the owning section as if it were always the decision, then propagate to linked stories and echoes (grep for the old term). Resolved open question → record the answer on the question (decision + evidence — the Open Questions section is the decision log) and fold the decision into its owning section.
6. Offer the epic write-up. If an epic completed this session, offer to draft docs/write-ups/E<nn>-<slug>.md: a dated, append-only narrative with a fixed header set — omit a section only when it genuinely doesn't apply, never invent new top-level headers:
   • ## What shipped — plain language a junior and a senior engineer both follow, leading with what it enables for the developer and the end user, not the mechanics;
   • ## Try it yourself — the handover: the exact steps the user runs to see the epic's artifact work, from a clean start, with the expected output and one line on what this gives the end user;
   • ## Validation notes — the developer's handover: how to re-verify what shipped — the regression command, the benchmark command and its budget, the linter, whatever applies from the epic's exit criteria — and what healthy output looks like;
   • ## Evidence — the executed proof: commands, CI runs, commits, the regression suite's green run, and the benchmark numbers where the epic named a benchmark — recorded here, they are the baseline later epics regress against;
   • ## Decisions made along the way — including any spike's decision matrix and its keep-or-discard call (omit if none);
   • ## What surprised (omit if none);
   • ## Left open (omit if none).