Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts Article Beats Journey Writer

writer writing skill risk: low

Article Beats Journey Writer

Instructs the model to write an article one beat at a time in choose-your-own-adventure style from a user-provided markdown file of raw material. It requires offering 2-3 candidate…

  • External action: medium

SKILL 1 file

SKILL.md
---
name: writing-beats
description: "Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to"
---
<what-to-do>

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:

1. 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.
2. 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.
3. 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.
4. Loop steps 2–4 until the article reaches a natural end.

</what-to-do>

<supporting-info>

## 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.

</supporting-info>

REQUIRED CONTEXT

  • markdown file of raw material

OPTIONAL CONTEXT

  • save path for the article

TOOLS REQUIRED

  • file_read
  • file_write

ROLES & RULES

  1. If the user did not say where to save the article, ask once and remember the path.
  2. Write 2–3 candidate starting beats drawn from the raw material.
  3. Show the user the beats before writing it to the article file.
  4. Preview what beats that might lead to once written.
  5. Write only that beat to the article file.
  6. Stop after writing one beat.
  7. Re-read the article file from disk before offering next beats.
  8. Offer 2–3 candidate next beats.
  9. Loop until the article reaches a natural end.
  10. A beat does one thing then stops.
  11. Size the beat by what it needs.
  12. Split if a beat needs five paragraphs and three subheadings.
  13. Write that beat only to the article file.
  14. Do not write the next beat.
  15. Pull material from the raw pile to populate the beat.
  16. The article ends when the journey is complete.
  17. Append one beat at a time.
  18. Never write ahead.
  19. Re-read the article file from disk before every write.
  20. Preserve user edits absolutely.
  21. If the user edits a previous beat substantially, let it change what comes next.
  22. If the user says rewrite that beat or go back and try a different beat, edit in place and leave the rest alone.

EXPECTED OUTPUT

Format
markdown
Constraints
  • write only the chosen beat to the article file
  • append one beat at a time
  • re-read file from disk before each step
  • offer exactly 2-3 candidate beats each turn

SUCCESS CRITERIA

  • Write 2–3 candidate starting beats
  • Write only the chosen beat to the file
  • Re-read the article file from disk before every step
  • Offer 2–3 candidate next beats
  • Stop when the journey reaches a natural end
  • Preserve user edits

FAILURE MODES

  • May write multiple beats at once
  • May fail to re-read the file from disk
  • May continue after the journey is complete
  • May ignore user edits to previous beats

CAVEATS

Dependencies
  • Requires a markdown file of raw material
  • Requires user to pick a starting beat
  • Requires user to pick each next beat
  • Requires a save path for the article file
Ambiguities
  • Description field is truncated mid-sentence at 'wants to'

QUALITY

OVERALL
0.85
CLARITY
0.80
SPECIFICITY
0.90
REUSABILITY
0.85
COMPLETENESS
0.85

IMPROVEMENT SUGGESTIONS

  • Complete the truncated description sentence for full clarity.
  • Specify the exact format or interface for user beat selection (e.g., numbered list, keywords).

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR WRITER