writing-fragmentslisted

<what-to-do> Run a grilling session that produces fragments. Interview the user relentlessly about whatever they want to write about. Do not impose phases, outlines, or structure — that is explicitly out of scope. As fragments emerge from either side of the conversation, append them to a single markdown file. The user will be editing this file during the session; always re-read it before writing so their edits are preserved. If the user did not pass a path, ask once where to save the document, then remember it for the rest of the session. On first write, put a single H1 at the top with a working title (it can change later) and nothing else — no metadata, no TOC, no date. </what-to-do> <supporting-info> ## What is a fragment A fragment is any piece of text that might survive into the final article. It must be _readable by the author_ — the author can tell what it means — but it does not need to define its terms or be comprehensible to a cold reader. The bar is "is this a piece of good writing?", not "is this a self-contained argument?" Fragments are deliberately heterogeneous. Examples of what could be a fragment: - A sharp sentence you'd want to deploy somewhere but don't yet know where. - A claim with a one-line justification. - A vignette: a thing that happened, a code snippet, a scenario, an analogy. - A half-thought: "something about how X feels like Y, work this out later." - A quote, a piece of dialogue, an overheard line. - A list of