discovery-drafting
This skill should be used when the user asks about "pantsing", "discovery write", "write without an outline", "discovery draft", "write into the dark", "story kernel", "reconcile a chapter", "dead end", "drafting sprint", "writing cadence", or wants to draft a story by discovery with retrospective bible reconciliation. NOT for outline-first drafting, or mysteries and other clue-dependent genres where setup must come before payoff (use chapter-writing), or a reverse outline of an existing linear draft, a subplot cut, or another revision pass on existing chapters (use revision-continuity).
danjdewhurst · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add danjdewhurst/story-skills --skill discovery-draftingAbout this skill
name: discovery-drafting description: This skill should be used when the user asks about "pantsing", "discovery write", "write without an outline", "discovery draft", "write into the dark", "story kernel", "reconcile a chapter", "dead end", "drafting sprint", "writing cadence", or wants to draft a story by discovery with retrospective bible reconciliation. NOT for outline-first drafting, or mysteries and other clue-dependent genres where setup must come before payoff (use chapter-writing), or a reverse outline of an existing linear draft, a subplot cut, or another revision pass on existing chapters (use revision-continuity).
Discovery Drafting
Overview
Draft by discovery ("pantsing"): start from a one-paragraph story kernel rather than a beat sheet, write forward, then reconcile each chapter back into the story bible through a structured loop (extract entities → reverse outline → diff against the bible → reconcile). This is the complement to chapter-writing's outline-first workflow. The bible is maintained after the prose, not before — which the repo's import-style entity extraction and continuity checks already support.
Prerequisites
A story project must already exist (created via the story-init skill), with
at least a story.md and one character. No plot structure is required to
start — arcs get built during reconciliation.
When to Use
- The user wants to draft without outlining first, or identifies as a discovery writer
- Starting a project from a situation/character rather than a plot
- NOT for mysteries or other clue-dependent genres where setup must precede
payoff (use chapter-writing; see
genre-craft) - NOT for revising existing chapters, including a reverse outline of an
existing linear draft or cutting a subplot as a revision pass (use
revision-continuity). The reverse outline inside the reconcile loop, and cutting dead ends in a batch review, stay here - The user can switch modes per project or per chapter; record the mode so audits know which discipline applies
Workflow
- Write the story kernel. Consult
references/story-kernel.mdand draft the one-paragraph kernel with the user (character in a situation, a want, an obstacle, a tone signal). Store it instory.mdunder## Story Kerneland setdraft-mode: discoveredin frontmatter. - Draft forward. Create the chapter with
story add chapter 'Title' --number N --mode discoveredsostory nextflags it until it is reconciled (in adraft-mode: discoveredproject a drafted chapter with nomodeis flagged too). Write the chapter from the kernel using the session shape inreferences/drafting-cadence.md(re-read → write → close with a next-session note). Write forward only; park bible questions as[TODO: check bible]inline rather than stopping. Follow the prose craft inchapter-writing/references/writing-guidelines.mdand the scene-grain tools in thescene-craftskill as usual, and write in the voice and house style recorded instyle-sheet.md— discovery changes planning order, not prose standards. Write in thelanguageset instory.md(a missing field meansen); the craft references' word-level advice is English, so in another language keep its aims and follow the style sheet's conventions. - Run the reconcile loop. After each chapter, follow
references/reconcile-loop.mdexactly:- Extract new entity/promise candidates (import-style, user-approved),
keeping names as the prose spells them. Ids stay ASCII kebab-case:
Cyrillic and Greek names get one automatically (
Пётрgivespetr), and a name in a script with no transliteration table (李明) needsstory add character '李明' --id li-ming, with the id agreed with the user - Reverse-outline the chapter into the chapter file and
scenes/records - Diff against the bible (new / contradiction / enrichment / dangling)
- Reconcile: update the bible or revise the chapter — never neither
- Add post-hoc chapter notes above
## Chapter Text(below it they count and ship as prose); set chapter frontmattermode: discovered
- Extract new entity/promise candidates (import-style, user-approved),
keeping names as the prose spells them. Ids stay ASCII kebab-case:
Cyrillic and Greek names get one automatically (
- Batch review every 3–5 chapters. Re-read post-hoc notes, sweep the
promise/question ledgers for dangling setups, and cut dead ends per
references/dead-ends.md(abandoned ledger entries keep a recorded reason; cut characters getstatus: cut, not deletion). - Hold the cadence. Keep the agreed target (see
references/drafting-cadence.md) and log each session withstory progress . --log; at midpoint and draft completion, hand the batch torevision-continuityfor developmental checks before continuing. - Close the loop on mode. When the draft is complete, every
mode: discoveredchapter must have post-hoc notes and a completed diff —story nextlists any without post-hoc notes underReconcile discovered chapters; finish those, then hand the manuscript torevision-continuityfor revision passes.
Conventions
story.mdfrontmatterdraft-mode: discoveredmarks a discovery project; per-chaptermode: discovered/mode: outlinedtracks mixed projects.- Chapters carry a
## Chapter Notes (post-hoc)section, above## Chapter Text, recording what was discovered, what was cut, and open questions — the project's memory of why the bible looks the way it does. - Entity candidates extracted from prose are presented for user approval
before bible files are created (same discipline as
story import). - Cut threads are logged, not erased: abandoned promises/questions keep
status: abandonedwith a reason; cut characters keep their file withstatus: cut. - Bidirectional links and kebab-case ids follow the shared story conventions exactly — discovery changes when the bible is written, not how.
CLI Maintenance
Use the Story CLI when it is available. If story is not installed, use the bundled fall