writing-fragments

Generated source view for the actual executable personal/writing-fragments skill. The durable routing article is Writing and Content Skills. Source: skills/personal/writing-fragments/SKILL.md

Runtime Source

Bundled Resources

No bundled resource files.

Description

Writing explore skill for mining raw article fragments before structure exists. Use when Kevin says "/writing-fragments", "mine fragments", "collect raw writing material", "interview me for article fragments", or wants a messy idea pile saved before drafting.

Skill Source

---
name: writing-fragments
description: Writing explore skill for mining raw article fragments before structure exists. Use when Kevin says "/writing-fragments", "mine fragments", "collect raw writing material", "interview me for article fragments", or wants a messy idea pile saved before drafting.
origin: personal
source_slug: writing-fragments
---

# Writing Fragments

Use this before an article has a structure. The job is exploration: widen the pile of material without committing to an outline, headline, thesis order, or platform format.

## Boundary

- Use `writing-fragments` for raw long-form material.
- Use `writing-beats` when Kevin wants to assemble a journey from a fragment pile.
- Use `writing-shape` when Kevin wants to shape a raw file into a coherent article.
- Use `social-draft` for X/LinkedIn posts.
- Use `content-strategy` for calendars, positioning, and topic selection.

## File Contract

Ask once where the fragment file should live if Kevin did not provide a path. Remember that path for the session.

On first write:

- Create one Markdown file.
- Put a single H1 working title at the top.
- Do not add metadata, a table of contents, tags, or date blocks.

Before every later write, re-read the file from disk. Kevin may have edited, reordered, or deleted material between turns. Preserve those edits.

Never overwrite the file blindly. Append fragments unless Kevin asks to edit a specific fragment in place.

## What Counts As A Fragment

A fragment is any piece of text that might survive into the final article. It should be readable to Kevin, but it does not need to be self-contained for a cold reader.

Useful fragments include:

- a sharp sentence
- a claim plus a one-line reason
- a vignette, scenario, analogy, or code example
- a half-thought marked for later development
- a quote or line Kevin wants to keep
- a complaint, confession, joke, or tension
- a compact leading word that names the whole idea

The leading word is especially valuable. When the conversation circles the same idea, try to name it in a phrase Kevin could reuse later.

## Conversation Loop

1. Capture fragments from the initial prompt too.
2. Interview Kevin for concrete scenes, claims, examples, objections, and language.
3. Append good fragments as they appear.
4. Mention additions briefly, but do not interrupt every fragment with a confirmation request.
5. Keep structure out of scope unless Kevin explicitly asks to switch skills.

## File Format

Separate fragments with a horizontal rule:

```markdown
# Working title

First fragment.

---

Second fragment.

---

> A quoted line Kevin wants to keep.

Reaction to the quote.
```

No headings inside the body. No tags. No imposed order beyond append order.

## Related Skills

- `writing-beats`
- `writing-shape`
- `social-draft`
- `content-strategy`
- `humanizer`

---

Timeline

• 2026-07-15 | Generated a browseable source page from the actual executable skill file. Source: skills/personal/writing-fragments/SKILL.md