Update to Matt Skills Curated

{
  "description": "Develop long-form writing through an interactive progression of narrative and argumentative beats. Use when drafting essays, articles, documentation, or blog posts where structure evolves beat by beat — even if the user says \"write this post with me\". Do NOT use for quick single-sentence copy edits.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 99
    }
  ],
  "name": "writing-beats",
  "skill_md_contents": "---\nname: writing-beats\ndescription: \"Develop long-form writing through an interactive progression of narrative and argumentative beats. Use when drafting essays, articles, documentation, or blog posts where structure evolves beat by beat — even if the user says \\\"write this post with me\\\". Do NOT use for quick single-sentence copy edits.\"\n---\n\n# Writing Beats\n\nDrive an interactive, choose-your-own-adventure drafting loop where each beat introduces a focused narrative move, respects grounded prerequisites, and unlocks reachable subsequent pathways.\n\n---\n\n## Core Invariants\n\n1. **One Beat per Turn**: Propose 2–3 candidate next moves, preview what each unlocks, and write strictly ONE chosen beat per turn to disk.\n2. **Dynamic Reachability & Grounding**: A candidate beat is only reachable if all required concepts are already grounded (either as baseline prerequisites or introduced by previous beats).\n3. **No Batch Writing Ahead**: Never jump ahead to write unapproved beats; each beat must establish state before subsequent branches are computed.\n4. **Preserve Author Revisions**: Always re-read the draft file from disk before generating next candidates to incorporate user edits seamlessly.\n5. **Complete Journey Over Empty Pile**: The essay concludes when the narrative journey is complete, not when every raw fragment in the pile is exhausted.\n\n---\n\n## Architecture & Map of Content (MOC)\n\n```\n[ Raw Fragment Pile ] ──► [ Settle Grounded Prerequisites ] ──► [ Present 2-3 Candidate Beats ]\n                                                                             │\n                                           ┌─────────────────────────────────┴─────────────────────────────────┐\n                                           ▼                                                                   ▼\n                                  [ Candidate Beat A ]                                                [ Candidate Beat B ]\n                                  - Requires: Grounded X, Y                                           - Requires: Grounded X\n                                  - Grounds: New Concept Z                                            - Grounds: New Concept W\n                                  - Unlocks: Path Alpha                                               - Unlocks: Path Beta\n                                           │\n                                           ▼\n                               [ User Chooses Beat A ] ──► [ Append Beat A to Disk ] ──► [ Compute Next 2-3 Candidates ]\n```\n\n| Beat Scale | Structure | Narrative Function |\n|---|---|---|\n| **Micro Beat** | 1 punchy sentence | Scene transition or timing pause |\n| **Standard Beat** | 1 tight paragraph | Setup + punchline or claim + rationale |\n| **Macro Beat** | 2–3 paragraphs | Self-contained vignette or code walkthrough |\n\n---\n\n## Step-by-Step Procedure (TWI)\n\n### Step 1: Initialize Grounding Matrix & Prerequisites\n- **Action**: Ingest the raw pile and agree with the user on what concepts the audience knows walking in.\n- **Key Point**: Track the active list of grounded concepts in session memory.\n- **Why**: Ensures every candidate branch is conceptually accessible to the reader.\n\n### Step 2: Formulate Candidate Next Beats\n- **Action**: Offer 2–3 candidate beats drawn from the pile, explicitly stating: (1) what concepts it requires, (2) what new concept it grounds, (3) what directions it unlocks.\n- **Inline Checklist**:\n  - [ ] All candidates reachable from currently grounded set\n  - [ ] Each candidate represents a distinct narrative branch\n  - [ ] Unlocked paths previewed for the user\n\n### Step 3: Append Chosen Beat & Re-Read Disk\n- **Action**: Write the user-selected beat to the draft file and re-read the entire draft before computing the next step.\n- **Key Point**: If the user asks to backtrack or rewrite an earlier beat, edit it in place and re-compute available branches.\n- **Why**: Gives the author complete interactive agency over article pacing and narrative tone.\n\n---\n\n## Anti-Rationalization Guardrails\n\n| Tempting Rationalization | Binding Rule | Engineering Rationale |\n|---|---|---|\n| *\"Write 3 beats at once to speed up drafting.\"* | **Write exactly 1 beat per turn.** | Batching beats removes the author's ability to steer branch direction. |\n| *\"Force every leftover raw fragment into the draft.\"* | **Conclude when the journey is complete; leave excess in the pile.** | Forcing unused fragments into the draft dilutes clarity and clutters the narrative. |\n| *\"Offer candidate beats that require ungrounded concepts.\"* | **Enforce prerequisite reachability on all candidates.** | Leaping into ungrounded concepts confuses readers and breaks argument continuity. |\n\n"
}