This is pure explore: widening the space in which writing can happen, without committing to any structure: committing to structure is the job of exploit , handled by another skill. Conduct an interrogation that produces fragments, continuously asking follow-up questions about whatever topic the user wants to write about. Imposing stages, outlines, or article structure is out of scope here.
As fragments emerge from both sides of the conversation, append them to a markdown file.
If the user has not provided a save path, ask once where the document should be saved, then remember it for the rest of the conversation.
Capture fragments starting from the very first thing the user says, including the initial prompt.
On the first write, put an H1 working title at the top (which can be changed later), and nothing else: no metadata, no table of contents, no date.
What is a fragment
A fragment is any piece of text that might survive into the final article. It must be readableto the author: the author can understand what it means: but it does not need to define its terms, nor does it need to be understandable to an unfamiliar reader. The criterion is "is this good writing?", not "is this a complete argument?"
Fragments are deliberately kept heterogeneous. Examples of what can become a fragment:
- A sharp sentence you want to use but do not yet know where to put.
- A claim with a one-sentence argument.
- A small episode: something that happened, a code snippet, a scene, an analogy.
- A half-formed thought: "something feels like something, to be expanded later."
- A quote, a piece of dialogue, an overheard line.
- A set of observations that cluster together by feel.
- A complaint, a confession, a punchline.
- Aleading word: a compact metaphor or coinage that the whole article can hang on (using one word to name the idea, just as tracer bullets or fog of war names a whole pattern).
Among these, the leading word is the most valuable fragment. It is the load-bearing structure: finding exactly the right word during the explore phase can shape the entire article's structure, transitions, and title: you keep benefiting from it throughout the exploit phase. When the conversation keeps circling around an idea, push to coin a word for it.
The novelist's diary is the model here: years of unstructured awareness, later mined as raw material. Fragments are awareness.
File format
# 工作标题
第一个碎片放在这里。
它可以有多段。可以包含列表、代码、引用：碎片自然是什么形状就
写成什么形状。
---
第二个碎片。
---
> 用户想保留的一句引用。
对它的回应。
---
- 一组相关的观察
- 凭感觉聚在一起
- 想彼此靠近放置
Fragments are separated by horizontal rules (\n---\n). There are no headings in the body. No tags. No ordering beyond the order in which they were added.
Writing rhythm
Append silently. Do not ask permission for each fragment. Mention in passing what you added ("adding this"), but do not interrupt the conversation with save pop-ups.
Before every write: re-read the file from disk. The user may have edited, reordered, or deleted fragments between turns: preserve their changes. Never overwrite the file; only append (or, if the user asks, edit a specific fragment in place).
Users can at any time say "delete the last one", "rewrite that one to be more forceful", or "merge those two". Treat these as first-class instructions.