writing-fragments

Captures unstructured writing fragments into a single markdown file through exploratory interviews.

Updated Jul 30, 2026
One-click install
npx skills add https://github.com/j172/bid --skill writing-fragments-j172
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-fragments
Source: https://github.com/j172/bid/tree/main/agent/skills/writing-fragments
Command: npx skills add https://github.com/j172/bid --skill writing-fragments-j172

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Early-stage writing ideas are scattered, half-formed, and easily lost before they can become an article. This Skill runs a relentless exploratory interview that mines raw fragments from the conversation and appends them to one markdown file, without imposing outlines or structure prematurely. ## Core Features & Use Cases - Exploratory Interviewing: Grills the user about their topic to surface sentences, claims, vignettes, half-thoughts, quotes, and leading metaphors worth keeping. - Append-Only Fragment Capture: Writes fragments separated by horizontal rules into a single markdown file, re-reading the file before every write to preserve user edits. - Leading Word Mining: Pushes to coin a compact metaphor or term that can anchor the later structure, transitions, and title of the piece. - Use Case: A writer wants to explore an essay idea about debugging culture. The Skill interviews them, captures every promising line and anecdote into fragments.md, and coins a load-bearing term that later shapes the full article. ## Quick Start Ask the assistant to start a writing fragments session about your topic and tell it where to save the markdown file.

Frequently Asked Questions about writing-fragments

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I collect raw ideas before writing an article?

Run an exploratory interview that captures every promising sentence, claim, vignette, or half-thought as a fragment in one markdown file. Fragments are separated by horizontal rules and carry no headings, tags, or ordering beyond when they were added.

What is a writing fragment in early drafting?

A fragment is any text that might survive into the final piece and is readable by its author, such as a sharp sentence, a claim with a one-line justification, a vignette, a quote, or a leading metaphor. It does not need to be self-contained or clear to a cold reader.

Can I edit or delete fragments after they are saved?

Yes, you can edit the markdown file directly between turns or issue commands like cut the last one, rewrite that one sharper, or merge those two. The file is re-read before every write so manual edits are preserved.

When should I not use fragment-based exploration?

Avoid it once you are ready to commit to structure, since imposing outlines, phases, or article organization is out of scope for exploration. At that point switch to a structuring or drafting workflow that consumes the collected fragments.

What is a leading word and why does it matter?

A leading word is a compact metaphor or coinage that names the central idea of the piece, similar to tracer bullets or fog of war. Landing one during exploration shapes the structure, transitions, and title of the later article.