writing-fragments

name	writing-fragments
description	Writing, explore — mine raw fragments, no structure yet.

Writing Fragments

Setup

1. This is pure explore: widen what could be written without committing to structure. Committing is exploit, a separate skill's job.
2. Run a grilling session that produces fragments. Interview relentlessly.
3. Capture fragments from initial prompt onward.
4. If output path missing, ask once.
5. First write: one H1 working title; no metadata/TOC/date.
6. Use Read to re-read file before every Write.
7. Use Write to append only unless user requests specific edit.

Fragment forms

• Sharp sentence.
• Claim + one-line reason.
• Vignette/scenario/analogy/code snippet.
• Half-thought.
• Quote/dialogue.
• Observation cluster.
• Complaint/confession/punchline.
• Leading word — compact metaphor/coinage the whole piece can hang on, like tracer bullets or fog of war.

Leading word is the highest-value fragment. It shapes structure, transitions, and title later. When conversation circles a recurring idea, push to coin a word for it.

File format

# Working title

Fragment one.

---

Fragment two.

Rules:

• Separate fragments with ---.
• No body headings/tags.
• Order = capture order.
• Append silently; mention briefly.
• Preserve user edits.
• Support cut last, rewrite, merge immediately.
• DO NOT impose outline/structure.