Explore a writing topic through ongoing questions and collect sentences, experiences, metaphors, and unfinished thoughts in one Markdown file. Build a pool of usable material without committing to an outline or article structure.
Writing, explore：挖掘原始 fragments，暂不施加任何结构。
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
这是纯粹的 explore：在不承诺任何结构的前提下，拓宽可写内容的空间——承诺结构是 exploit，是另一个 skill 的工作。运行一个产出 fragments 的 grilling session，围绕用户想写的任何主题持续访谈。在这里强加 phases、outlines 或文章结构都不在范围内。
当对话双方产生 fragments 时，把它们追加到单一 markdown 文件。
如果用户没有传入路径，只询问一次文档保存到哪里，然后在 session 剩余部分记住它。
从用户说的第一句话开始捕获 fragments，包括 initial prompt。
第一次写入时，在顶部放一个带 working title 的单一 H1（之后可以改），除此之外什么都不要放：不要 metadata、TOC 或 date。
</what-to-do> <supporting-info>Fragment 是任何可能进入最终文章的文本片段。它必须_对作者可读_，也就是作者能知道它是什么意思；但它不需要定义术语，也不需要让冷读者立即理解。标准是 “这是不是一段好写作素材？”，不是 “这是不是自洽论证？”
Fragments 刻意保持异质。可能成为 fragment 的例子：
在这些当中，leading word 是最值得落地的 fragment。它是 load-bearing 的：在 explore 阶段命名对的那一个，就会塑造之后的结构、transitions 和标题——在整个 exploit 阶段持续产生回报。当对话围绕一个反复出现的 idea 打转时，推动为它造一个词。
Novelist's diary 是模型：多年无结构的 noticings，之后被挖掘成 raw material。Fragments 就是 noticings。
# Working title
A first fragment lives here.
It can be multiple paragraphs. It can include lists, code, quotes — whatever
shape the fragment naturally takes.
---
A second fragment.
---
> A quoted line that the user wants to keep around.
A reaction to it.
---
- A cluster of related observations
- That hang together by feel
- And want to be near each other
Fragments 用 horizontal rule（\n---\n）分隔。正文内不要 headings。不要 tags。除了加入顺序之外，不做排序。
安静追加。不要为每个 fragment 请求许可。可以顺带说你添加了什么（"adding that"），但不要用 save dialogs 打断对话。
每次写入前：从磁盘重新读取文件。用户可能在回合之间编辑、重排或删除 fragments；保留他们的变化。永远不要 overwrite 文件；只 append（或者在用户要求时，就地编辑特定 fragment）。
用户随时可以说 "cut the last one"、"rewrite that one sharper"、"merge those two"。把它们当成一等指令。
</supporting-info>No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Find the right skill and sequence for your current development task, from shaping an idea to implementation, debugging, and review. The guide also explains when to prototype, prepare specifications, or move work into a fresh session.
Summarize the current conversation and launch a fresh background agent to continue the work. The handoff includes references to existing artifacts and suggested skills, removes sensitive information, and can emphasize the next session’s intended focus.
Review changes from a chosen Git reference against both project coding standards and issue or specification requirements. Separate parallel reviews report rule violations, possible design problems, missing requirements, and changes beyond the intended scope.
Design modules that expose simple interfaces while hiding substantial behavior. Use shared terms and principles to assess interface complexity, decide where behavior can be swapped, and organize code so callers and tests use the same interface.
Diagnose difficult bugs and performance regressions by first building a repeatable check for the exact symptom. Minimize the reproduction, test ranked hypotheses, apply a fix, and verify the original scenario with regression tests where suitable.
Clarify project terminology and the relationships between business concepts. Check definitions against concrete scenarios and code, update GLOSSARY.md as terms are agreed, and record significant design decisions with their trade-offs when the stated criteria are met.