# Span Closure
> Close out a stretch of work — one continuous thread of narrative — flushing, summarizing, and auditing what it leaves behind. The end of a stretch of work is signalled ahead of it: work completes, the person the work is for calls an end, notice arrives that the working text — the text in front of one right now — is about to be condensed, "close the session", "wrap up", "we're done here", "finish up", "before we stop".
- Skill: `ryzhakar/span-closure` (Agent Skill)
- Install (CLI): `npx skillmds@latest add ryzhakar/span-closure`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ryzhakar/span-closure/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: ryzhakar (https://skillmd.com/u/ryzhakar)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/ryzhakar/span-closure
---
Count a stretch of work as beginning where working text first carries the work now in hand; never count one as beginning before that.
Take a stretch of work as ended where the work in hand no longer continues its thread; never take one as ended while the work in hand still continues it.
Enter at a foreseeable end — an end something signals ahead of it; never enter where nothing signalled the end.
Refuse this whole procedure at a blind end — an end arriving with no signal ahead of it; never close a stretch of work nobody saw ending.
Read what this stretch of work wrote into the journal — where event-capture writes an event — against what it did; never skip that comparison.
Write every event this stretch of work left unwritten — every happening here of a kind schema-resolution names — each through event-capture; never write one by other means.
Treat this flush as a second pass over what should already be written; never treat it as what writes events.
Leave each event's own writing to event-capture at the moment it happens; never let an event wait for the end.
Add what is missing; never rewrite an event already written.
Write one closing summary of the whole working text this stretch of work carried — a lossy condensation, keeping what it can and dropping the rest — through record-writing; never write a second for one end.
Condense into a summary a set of records or the whole working text a stretch of work carried; never condense anything else into one.
Tell one summary from another by the set it condensed and by the occasion that produced it — what called for the writing, and when; never tell one from another by its content.
Write the summary oneself; never have another write one in one's place.
Grant every summary the full force of one's own record, whatever occasion produced it; never attach an exception to one.
Leave a summary's content unconstrained — no declared shape it has to match, no field of it guaranteed; never demand a named field of a summary.
Replace a summary by a fuller summary through record-writing; never edit one in place.
Write a `baseline` record — the standing statement of the state this work is expected to be in — naming the state this stretch of work leaves behind, through record-writing; never write one naming the state this stretch of work began in.
Take the baseline's shape from the schema — what fixes a record's shape — through schema-resolution; never take it from elsewhere.
Audit every waking cause — what begins later work — this stretch of work laid through staging-relay, confirming each still points at work that remains; never end a stretch of work leaving one unexamined.
Write what the audit found through event-capture; never leave a waking cause found stale unwritten.
Let the end come once the flush, the summary, the `baseline`, and the audit are done or written down as undone; never delay an end for a step of this procedure.