Writing Fragments — Experimental

What it does

This experimental writing skill is an exploration stage. It interviews the author and appends fragments that may later survive into an article: observations, examples, half-thoughts, quotations or a useful metaphor. A fragment needs to make sense to the author, but does not have to teach a cold reader its terminology. The source values finding a leading word that can name the recurring idea. It explicitly leaves article structure to another workflow. The file is intentionally simple: one working-title H1, fragments separated by horizontal rules, and no internal headings, tags or table of contents.

When to use it

• Capture the lived details behind an engineering incident before deciding the lesson.
• Develop a personal essay from anecdotes and competing observations.
• Find a useful metaphor for a repeated product or team problem without forcing a thesis too early.

Step-by-step workflow

1. Agree a Markdown destination once and begin capturing useful material from the initial prompt.
2. Interview for specific scenes, examples, contradictions and language the author wants to keep.
3. Append readable fragments separated by horizontal rules, keeping the body free of imposed section headings.
4. Re-read the current file before every write so manual edits, deletions and reordered material survive.
5. Continue exploration until the author has a useful pile; move to structure or prose only in a separately chosen stage.

Example request

Use writing-fragments to interview me about the deployment that looked successful but served stale content. Save at notes/deployment-fragments.md. Ask about the actual moments, misleading signals and what finally exposed the issue. Keep promising sentences and examples. Do not outline the article or invent dialogue. If a metaphor emerges, capture it as a fragment rather than making it the thesis.

Worked example

The author recalls a green deployment badge, a customer screenshot and a missing cache purge. These can become three distinct fragments without deciding the final order. A phrase such as “a green light on the wrong road” might be worth retaining, but it remains raw material. Before adding the next example, the agent rereads the file and sees that the author removed a customer name; the name must stay removed. The exploration can end with contradictory fragments because deciding the argument belongs to a later editorial step.

What you get

A growing Markdown collection of original raw material, including concrete details and potentially useful language.

How to evaluate the result

• The file has one working-title H1 and clear fragment separators.
• No invented quotations or facts enter the pile.
• Manual deletions remain deleted and exploration does not silently become an outline.

What you need

An author willing to answer questions, a writable agreed file and permission to retain the specific material. Sensitive anecdotes need anonymization before storage or publication.

Setup and activation

Experimental source: this folder is under skills/in-progress and is not a stable-release recommendation. Its frontmatter disables automatic model invocation, so explicitly select it in a host that supports that behavior. This directory reviewed source only; it did not install or execute the skill. Before adopting it, scan the exact version, inspect requested tools and permissions, and test on disposable non-sensitive inputs. A compatible instruction format does not establish identical host capabilities.

Limits and considerations

An in-progress source that does not produce a finished article. Appending text is not fact-checking, quotation clearance or consent to publish. An unstructured file can become large; curation should preserve the author’s intentional edits.

Related workflows

• Use writing-beats once the pile is fixed and the author wants to assemble a reader journey.
• Use a factual review before turning remembered incidents into public claims.

License and reuse

MIT at repository level. Preserve copyright and license notices; check companion files and external dependencies for their own terms.

Further reading

• Publisher setup and compatibility instructions
• Reviewed source at immutable commit