writing-fragmentslisted

<what-to-do> This is pure **explore**: widen the space of what could be written without committing to structure — committing is _exploit_, a separate skill's job. Run a grilling session that produces fragments, interviewing the user relentlessly about whatever they want to write about. Imposing phases, outlines, or article structure is out of scope here. As fragments emerge from either side of the conversation, append them to a single markdown file. If the user did not pass a path, ask once where to save the document, then remember it for the rest of the session. Capture fragments from the very first thing the user says, including the initial prompt. 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 lik