Writing Beats — Experimental

What it does

Writing Beats begins after exploration: the user supplies a fixed pile of raw material and chooses a path through it. The experimental source treats a beat as one narrative move, which may be a sentence or several paragraphs. Before writing, the author and agent agree audience prerequisites. Each candidate beat must rely only on grounded concepts and declare which new ideas it introduces. The user chooses among two or three reachable directions, and only that chosen beat is written. This separates purposeful article construction from gathering more material or generating an entire draft in one pass.

When to use it

• Turn interview notes into a technical explainer for a precisely defined audience.
• Build a migration post whose concepts must appear before later examples depend on them.
• Explore alternative openings without overwriting an author’s approved prose.

Step-by-step workflow

1. Agree the article path and which ideas the audience already knows before the first beat.
2. Offer two or three possible openings from the supplied material, naming the concepts each establishes.
3. Write only the selected beat and update the set of concepts the reader can now use.
4. Re-read the article from disk before proposing the next reachable moves, preserving the author’s intervening edits.
5. Continue by selection until the argument reaches a natural end; leave unused fragments out rather than forcing them into the article.

Example request

Use writing-beats on notes/module-boundaries.md to write an explainer for JavaScript developers new to package design. Save the article at drafts/boundaries.md. Treat imports as known, but establish public interfaces before discussing deep imports. Offer three openings and wait for my choice. Write one chosen beat at a time and preserve any edits I make between turns.

Worked example

The raw pile includes a dependency graph, a broken build and a proposed package rule. Opening with the graph may assume the reader understands a public boundary, while opening with the broken build can establish that idea through a concrete failure. Once the selected opening grounds the boundary concept, a later beat can explain how deep imports cross it. A tempting paragraph about cycles may still need its own setup. The grounded-concept list exposes that missing bridge before the article jumps ahead.

What you get

An incrementally authored article with an intentional concept sequence, user-selected direction and preserved edits.

How to evaluate the result

• Each beat depends only on prerequisites or ideas already introduced.
• The saved file contains only selected beats and retains author edits.
• The ending serves the argument rather than exhausting every fragment.

What you need

A fixed source-material file, an agreed output path and an author available to select directions. The source sets disable-model-invocation, so this is an explicitly chosen workflow.

Setup and activation

Experimental source: this folder is under skills/in-progress and is not a stable-release recommendation. Its frontmatter disables automatic model invocation, so explicitly select it in a host that supports that behavior. This directory reviewed source only; it did not install or execute the skill. Before adopting it, scan the exact version, inspect requested tools and permissions, and test on disposable non-sensitive inputs. A compatible instruction format does not establish identical host capabilities.

Limits and considerations

The skill is experimental and deliberately interactive; it is unsuitable for an unattended whole-article batch. Grounding is a reasoning aid rather than proof every reader understands the result. Source claims and quotations still require factual and rights checks.

Related workflows

• Use writing-fragments first when the raw material is still being explored.
• Use writing-shape when the task is selecting a larger organizing form rather than incremental prose.

License and reuse

MIT at repository level. Preserve copyright and license notices; check companion files and external dependencies for their own terms.

Further reading

• Publisher setup and compatibility instructions
• Reviewed source at immutable commit