writing-beats
Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.
1How It Works & Mechanism
Positioned as the exploit stage: the source material pile remains fixed, and the skill's task is to choose a path and mine the material beat by beat.
The user has passed (or will pass) a markdown file of raw material. This is **exploit**: the exploring is done, the pile is fixed. Commit to a path through it and mine the pile to fill each beat.
Interactive algorithm = choose-your-own-adventure beat journey: establish prerequisites first → offer 2-3 candidate starting beats for the user to choose → write only that chosen beat → re-read disk → offer 2-3 candidate next beats → loop until reaching a natural conclusion.
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.
Grounding constraint engine: every concept must be grounded before a beat uses it (assumed reader knowledge = prerequisite, or introduced by a preceding beat); the reachability of candidate beats is determined by the set of already grounded concepts.
Every **concept** has to be **grounded** before a beat can lean on it: the audience either walked in knowing it or met it in an earlier beat. A beat that reaches for an ungrounded concept loses the reader; that is the one move the journey can't make. The unit is the concept, not the word for it: a beat can lean on an idea the reader lacks even with no jargon in sight.
Pacing discipline: write only one beat at a time, never write ahead; re-read the file from disk before each write to strictly preserve user edits; allow the user to request a rewrite of any beat at any time.
Append one beat at a time. Never write ahead. Re-read the article file from disk before every write. Preserve user edits absolutely.
Definition of completion: stops when the journey is complete, not when source material is exhausted—most material piles naturally leave behind leftover fragments.
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.
2Core Capabilities
4Recommended Governance & Evidence
- 本地工作目录: File read/write and artifact output: User-specified article file: appends one beat per step; edits a specific beat in place upon user request ('rewrite that beat' in place)
5Second-Pass Verification
- [ok] choose-your-own-adventure 交互流程(候选拍 → 用户选 → 只写一拍 → 重读 → 再候选) — SKILL.md 步骤 1-5 逐字存在:'Write 2–3 candidate **starting beats**'、'write **only that beat**'、'Re-read the article file from disk. Then offer 2–3 candidate **next beats**'。
- [ok] grounding 机制(prerequisite/introduced + 运行清单 + 可达性) — Grounding 整节存在,含 'Keep a running list of what's grounded so far';候选拍可达性由 grounded 集决定。
- [ok] 只写一拍、不超前 — 'Append one beat at a time. Never write ahead.' 原文在。
- [ok] 每次写前重读磁盘、保留用户编辑 — 'Re-read the article file from disk before every write. Preserve user edits absolutely.' 原文在。
- [ok] 就地重写特定 beat — 'edit in place, leave the rest alone' 原文在。
- [ok] 文件写入范围 — 仅用户指定文章文件;'If the user did not say where to save the article, ask once and remember the path.' 无其它路径指令。
- [ok] 外部依赖为空 — token 扫描零命中;无 CLI/API/网络/包。
- [ok] 元数据 + beta 状态 — GitHub API MIT/257659/2026-09-04;本地 HEAD == 3cca18b;in-progress README 列为 beta。
6Verdict & Scenarios
e5908f87db6a7beb…