Writing Beats is the second half of a two-step writing workflow. You hand it a Markdown file of raw material, and it runs a choose-your-own-adventure journey: it offers two or three candidate beats, you pick one, and it appends only that beat to the article file.
Before the first beat it settles what the audience already knows. Every later beat may lean only on concepts the reader already holds or met in an earlier beat.
What You Get
- An article file that grows one beat at a time
- A running list of grounded concepts
- Two or three candidate beats at every turn with a preview of what each unlocks
- Edits in place when you ask to rewrite or revisit a beat
Common Use Cases
- Turning a fragment pile into a blog post
- Writing a technical explainer where each term must be defined before use
- Reworking a draft by asking for a different beat three
- Building a narrative essay where the order of reveals matters
What Makes It Unique
Most writing skills draft a whole piece in one pass. This one writes a single beat, stops, re-reads the file from disk to keep your edits, and only then offers the next options. The grounding rule is the core idea: a beat that needs an ungrounded concept is unreachable, so the path always stays readable for the audience.
Under The Hood
The skill is a single Markdown file with an agent metadata file for Codex. It reads your raw material and the article file, and it writes only to the article path you give it. It runs no scripts and reaches no network service. It is user-invoked only.