writing-beats

文档社区 @mattpocock

信任分: 88/100
兼容 Agent: 1

速查档案只列事实：领域、Agent、信任分、作者、原文章节。装与不装请看下方作者解读。

领域: 文档
兼容 Agent: Claude Code
信任分: 88 / 100 · 社区维护
作者 / 版本 / 许可: @mattpocock · 未声明 license
安装命令数: 1 条

需要注意： 未限定 allowed-tools，默认拥有全部工具权限。

解读由编辑根据原文凝练而成，命令、链接、术语均与作者原文一致；想看完整论述请切到右侧

writing-beats 把写作过程拆成「一个 beat 一个 beat」的旅程——你给一份 markdown 原料，技能跟你来回推进，每次只写一个 beat到文章文件里，然后停下，再列 2–3 个 next beat 让你选下一个方向。关键纪律：永远不写下一个 beat 之前的事；永远先 re-read 文件再写。

什么是 beat

一个 beat 是旅程中的一步动作——可能是布景、落点、提问、插入旁白、或翻一个角度，做完就停，让读者落在「下一 beat 可以从这里转弯」的位置。它的大小由它要做的事决定：一句话（"And then nothing happened for three weeks."）、一个段落（需要铺设的小动作）、几个自包含段落（一个完整 vignette / 论点 / 例子）。如果一个 "beat" 需要五段 + 三个小标题，那它不是 beat，是两个 beat 粘在一起，要拆。

工作流

① 用户传一份 markdown 原料；没说存哪问一次记下；② 写 2–3 个候选起始 beat——都从原料里来、各代表不同入口，先把候选给用户看再决定；用户选一个，并预览那个 beat 之后可能通向哪些路径；③ 选定后只写那一个 beat 到文章文件，停；④ 从磁盘 re-read 文章文件，再给 2–3 个候选 next beat（不同方向的 pivot）；⑤ 循环 ②–④ 直到旅程自然结束。

写作节奏

追加式，一次一个 beat，永不写在前面。每次写之前必须 re-read 文章文件，绝对保留用户的编辑。如果用户大改了前面的 beat，让它影响后面的方向。"rewrite that beat"、"go back and try a different beat 3"——就地改，其他不动。

旅程何时结束

当旅程完整时结束，不是当原料用完。多数原料会有剩余 fragment 没被收纳，这就是有更多原料的意义：你在挑选，不是在搬运。

适合的场景

把已沉淀的 fragment / 笔记长成一篇有节奏的文章
写技术博客 / essay 时想分段推进、每一步都让作者看到方向
多人 / 多 session 接力写作，每次写一个 beat 不污染上下文

何时不要用

想要一次性出整篇：用 writing-shape 段落式生长更顺
写说明性 doc / API 文档：beat 节奏不适合规约性内容

配套

writing-fragments（前置：先攒一份原料）、writing-shape（把原料按段落而非 beat 长成文章）、writing-skills（语调纪律）、grill-with-docs（按文档锚定术语）。

The user has passed (or will pass) a markdown file of raw material.

If the user did not say where to save the article, ask once and remember the path.

Then run a beat-by-beat journey:

Write 2–3 candidate starting beats, drawn from the raw material. Each is a different entry point into the article. Show the user the beats before writing it to the article file. The user picks one. Preview what beats that might lead to once written - as if the user is seeing a little way down the path.
Once the user picks a starting beat, write only that beat to the article file. A beat may be one sentence or several paragraphs — whatever that beat naturally is. Stop there.
Re-read the article file from disk. Then offer 2–3 candidate next beats — different directions the journey could pivot to from where the article now stands.
Loop steps 2–4 until the article reaches a natural end.

What is a beat

A beat is one move in the journey. It does one thing — sets a scene, lands a point, asks a question, drops an aside, twists the angle. Then it stops, leaving the reader at a place where the next beat can pivot.

A beat is sized by what it needs:

A single sentence if that's all the move is ("And then nothing happened for three weeks.").
A short paragraph if the move needs setup.
Multiple paragraphs if the beat is a self-contained vignette, argument, or example.

If a "beat" needs five paragraphs and three subheadings, it's not a beat — it's two beats glued together. Split it.

Writing one beat

Once a beat is picked, write that beat only to the article file. Do not write the next beat.

Pull material from the raw pile to populate the beat. You can paraphrase, split, recombine, or quote. The pile is a quarry.

Ending the journey

The article ends when the journey is complete — not when the pile is empty. Most piles will have leftover fragments that don't make it in. That is fine; that is the point of having more raw material than you need.

Writing rhythm

Append one beat at a time. Never write ahead.
Re-read the article file from disk before every write. Preserve user edits absolutely.
If the user edits a previous beat substantially, let it change what comes next.
If the user says "rewrite that beat" or "go back and try a different beat 3", do it — edit in place, leave the rest alone.