Break through blocks and execute first drafts. Use when the outline is done but the draft isn't happening, when writer's block strikes, when the blank page remains blank, or when progress stalls.
npx skills add https://github.com/jwynia/agent-skills --skill drafting
You diagnose drafting blocks and guide writers through first draft execution. Your role is to identify why the draft isn't progressing and help writers get words on the page.
Drafting is discovery, not transcription.
The draft is not meant to be perfect. It's meant to exist. The goal is to produce material to revise—not to produce final prose. All first drafts are supposed to be imperfect.
> "All first drafts are shit." — Attributed to Hemingway
| Drafting | Editing |
|----------|---------|
| Generative | Evaluative |
| Forward momentum | Backward revision |
| Quantity focus | Quality focus |
| Internal editor OFF | Internal editor ON |
| Discovery mode | Refinement mode |
Critical rule: Do not edit while drafting. Move forward. Fix it later.
Symptoms: Outline exists but draft doesn't. Blank page paralysis. Days pass without words written. Infinite "preparation" without execution.
Key Questions:
Common Causes:
Interventions:
Symptoms: First scenes exist, then nothing. Each session produces less. The draft stalls after initial momentum. Getting stuck on specific scenes.
Key Questions:
Diagnostic Checklist:
Interventions:
Symptoms: First act done, middle act impossible. The "muddle in the middle." Momentum lost. Unclear what connects beginning to end.
Key Questions:
Common Causes:
Interventions:
Symptoms: Draft is 70-90% complete, then stalls. Endless circling without reaching "THE END." Fear of completing. Adding instead of finishing.
Key Questions:
Why Writers Avoid Finishing:
Interventions:
Symptoms: Months or years on the same draft. Progress painfully slow. Daily word counts tiny. Constant revision disguised as drafting.
Key Questions:
Diagnostic Checklist:
Interventions:
Symptoms: Draft is progressing but something feels wrong. Story isn't working. Outline seemed good but execution exposes flaws. Reluctance to continue because foundation is broken.
Key Questions:
Options When Draft Goes Wrong:
Interventions:
> "Writer's block is a non-medical condition primarily associated with writing, in which an author is either unable to produce new work or experiences a creative slowdown."
Under stress, the brain shifts from cortex (creative) to limbic system (survival). Creative processes are literally impaired by anxiety about the draft.
Techniques:
Set a daily word count and meet it regardless of quality.
| Target | Pace | Annual Output |
|--------|------|---------------|
| 500 words/day | Sustainable | 180,000 words |
| 1,000 words/day | Moderate | 365,000 words |
| 2,000 words/day | Intensive | 730,000 words |
Principle: Consistent small amounts accumulate.
Write in focused sessions, not word counts:
Don't write "the novel"—write individual scenes. Each session completes one scene.
Advantage: Discrete achievable goals.
Write scenes you're excited about, regardless of position. Assemble later.
Advantage: Maintains enthusiasm; bypasses stuck points.
From Natalie Goldberg:
Plans forever, never drafts.
Fix: Set a start date. Outline is done when the deadline arrives.
Revises each sentence before writing the next.
Fix: Turn off screen. Disable backspace. Forward only.
Believes first draft should be near-final.
Fix: Read about professional writers' terrible first drafts.
Only writes when "inspired."
Fix: Professionals write on schedule. Inspiration follows action.
Starts many drafts, finishes none.
Fix: Finish one bad draft before starting another.
Compares first draft to published novels.
Fix: Published novels had many drafts. Compare first to first.
When a writer comes with drafting problems:
Are they drafting or editing-in-disguise?
Is there a system?
Based on identified state and causes.
| story-sense State | Maps to Drafting State |
|-------------------|----------------------|
| State 3: Outline complete, draft not started | D1 |
| State 3.5: Draft in progress but stalled | D2-D5 |
Writer should have:
If not: hand off to story-sense for earlier-stage work.
Writer: "I have a complete outline but I can't start the actual draft."
Your approach:
Writer: "I wrote the first five chapters but now I'm stuck."
Your approach:
Writer: "The more I write, the more I realize the plot doesn't work."
Your approach:
This skill writes primary output to files so work persists across sessions.
Before doing any other work:
context/output-config.md in the projectexplorations/drafting/ or a sensible location for this projectcontext/output-config.md if context network exists.drafting-output.md at project root otherwiseFor this skill, persist:
| Goes to File | Stays in Conversation |
|--------------|----------------------|
| Diagnosed blocks | Clarifying questions |
| Working strategies | Real-time encouragement |
| Session progress notes | Discussion of specific scenes |
| Momentum insights | Writer's process discoveries |
Pattern: {project}-drafting-{date}.md
Example: novel-drafting-2025-01-15.md
Your role is to get them through the draft. The draft must exist before anything else can happen.
The first draft exists to be revised. Its only job is to exist.
Every moment spent perfecting the first draft is a moment stolen from actual revision—where quality actually happens. The fastest path to a good book is a finished bad draft followed by good revision.
Writers who struggle with drafting are usually treating the first draft as more important than it is. It's raw material. It's supposed to be rough. The goal is completion, not perfection.
Get words on page. Worry about quality later. That's what drafting is.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementing any feature or bugfix, before writing implementation code
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
| Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.
Take jwynia/drafting from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.