---
name: writing-fragments
description: Grilling session that mines Bo for fragments — heterogeneous nuggets of writing (claims, vignettes, sharp sentences, half-thoughts) — and appends them to a single markdown file as raw material for a future article or X post. Use when Bo says "fragments", "ideate", "braindump", "raw material", "help me think through", or wants to develop ideas before imposing structure. Also use proactively before drafting long-form writing (X articles, blog posts) when Bo has a topic but no clear angle yet.
---

# /writing-fragments — Fragment Mining

Grilling session that extracts raw writing material. No structure, no outline, no phases. Just mining.

## What this is for

Bo has an idea but hasn't found the angle, the hook, or the structure yet. This session excavates the raw material. Shape comes later.

## How to run it

1. **Ask where to save** if Bo didn't specify a path. Save to `workspace/fragments/TOPIC-YYYYMMDD.md`. Remember the path for the whole session.

2. **Start mining immediately** — capture fragments from Bo's first message, including the initial prompt itself.

3. **Interview relentlessly** — ask one sharp question at a time. Don't bundle questions. Push on:
   - What's the thing you actually believe here? (not the diplomatic version)
   - What's the moment or example that made you think this?
   - What would someone smart disagree with?
   - What's the thing everyone else gets wrong about this?
   - What's the version of this you'd say at dinner vs. in a paper?
   - Is there a specific number, result, or moment you keep coming back to?

4. **Append silently** — don't ask permission for each fragment. Just say "adding that" in passing. Never interrupt the conversation with file confirmations.

5. **Re-read the file before every write** — Bo may have edited between turns. Preserve his edits. Append only (or edit specific fragment if Bo asks).

## What counts as a fragment

Deliberately heterogeneous. Any of these:
- A sharp sentence you'd want to deploy somewhere but don't know where yet
- A claim with a one-line justification
- A vignette: something that happened, an analogy, a scenario, a code pattern
- A half-thought: "something about how X feels like Y — work this out later"
- A quote, a line overheard, a statistic that sticks
- A cluster of related observations that hang together by feel
- A complaint, a confession, a punchline

The bar is "is this a piece of good writing?" not "is this a self-contained argument?"

## File format

```markdown
# Working title

First fragment here. Can be multiple paragraphs, code, quotes — whatever shape it naturally takes.

---

Second fragment.

---

> A quoted line worth keeping.

A reaction to it.

---

- A cluster of related observations
- That hang together by feel
```

Fragments separated by `\n---\n`. No headings inside the body. No tags. No enforced order beyond the order added.

## Writing rhythm

Append silently. Mention what you added in passing. Keep the conversation moving.

Bo can say:
- "cut the last one" → delete it
- "rewrite that one sharper" → edit in place
- "merge those two" → combine
- "that's it for now" → stop, summarize what's in the file

## What NOT to do

- Don't impose an outline or structure — that's explicitly out of scope for this phase
- Don't ask "shall I save that?" for every fragment — just save it
- Don't bundle multiple questions — one at a time
- Don't summarize what Bo said back to him before capturing it — capture first, respond second
- Don't add metadata, TOC, dates, or tags to the file

## After the session

When Bo is done, note:
- How many fragments were captured
- Any obvious clusters or tensions worth flagging
- Suggest next step: `/writing-shape` to impose structure on the raw material