drafting
アウトラインが完成しているのに初稿が書き進まないとき、ライターズブロックに陥ったとき、白紙のページが埋まらないときに活用する、初稿作成の壁を突破するためのスキルです。進行が止まった際に呼び出すことで、執筆の勢いを取り戻します。
description の原文を見る
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.
SKILL.md 本文
Drafting: Diagnostic Skill
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.
Core Principle
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
The Fundamental Split
| 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.
The Drafting States
State D1: Can't Start
Symptoms: Outline exists but draft doesn't. Blank page paralysis. Days pass without words written. Infinite "preparation" without execution.
Key Questions:
- Is the outline too vague to write from?
- Are expectations too high for a first draft?
- Is there fear of the blank page?
- Are you waiting to feel "ready"?
Common Causes:
- Perfectionism (standards too high for first draft)
- Anxiety (fear of judgment or failure)
- Over-preparation (planning forever, never starting)
- Vague outline (don't know what to write)
Interventions:
- Write a zero draft scene with no expectations
- Start with dialogue only (easiest to generate)
- Write "What happens in this scene is..." and describe it
- Set a start date and keep it regardless of readiness
- Lower the bar: "I will write 100 bad words"
State D2: Start But Can't Continue
Symptoms: First scenes exist, then nothing. Each session produces less. The draft stalls after initial momentum. Getting stuck on specific scenes.
Key Questions:
- Are you editing while drafting?
- Did you stop at a dead end?
- Is the current scene unclear?
- Did you stop at a bad place last time?
Diagnostic Checklist:
- Not re-reading previous work before writing
- Moving forward, not polishing backward
- Stopping mid-scene (not at ends)
- Using placeholders for stuck parts
Interventions:
- Skip to a different scene you CAN write
- Use placeholders: [SOMETHING HAPPENS HERE]
- Lower word count goals dramatically
- Stop mid-sentence next time (easier to resume)
- Disable backspace / turn off screen
State D3: Middle Stall
Symptoms: First act done, middle act impossible. The "muddle in the middle." Momentum lost. Unclear what connects beginning to end.
Key Questions:
- Is the story working?
- Is there a structural problem the draft is revealing?
- Is motivation flagging because direction is unclear?
- Do you know the ending?
Common Causes:
- Outline was incomplete for middle section
- Story problem discovered during drafting
- The "long slog" between exciting beginning and end
- Lost connection to why this story matters
Interventions:
- Connect with the ending—write toward it
- Review outline for structural gaps
- Write scenes out of order (skip to climax if needed)
- Ask: "What's the worst thing that could happen now?"
- Take a short break, then resume with fresh eyes
State D4: Can't Finish
Symptoms: Draft is 70-90% complete, then stalls. Endless circling without reaching "THE END." Fear of completing. Adding instead of finishing.
Key Questions:
- Is the ending unclear?
- Is there fear of judgment once complete?
- Has momentum been lost?
- Are you avoiding the ending?
Why Writers Avoid Finishing:
- Fear of evaluation (once done, it can be judged)
- Uncertainty about what comes next
- Ending feels inadequate
- Attachment to the process over the product
Interventions:
- Set a deadline and commit publicly
- Commit to word count regardless of quality
- Remember: a finished bad draft beats an unfinished "good" one
- Write the ending NOW, then fill gaps
- Accept the ending can be revised—just get something down
State D5: Draft Taking Too Long
Symptoms: Months or years on the same draft. Progress painfully slow. Daily word counts tiny. Constant revision disguised as drafting.
Key Questions:
- Is editing happening during drafting?
- Are word count goals too low?
- Is perfectionism slowing progress?
- Are you treating the first draft as final?
Diagnostic Checklist:
- Daily word count goal exists and is met
- Not re-reading more than last paragraph before starting
- Not revising sentences after writing them
- Actually drafting, not perpetual revision
Interventions:
- Increase daily goals (500 → 1000 → 2000)
- Time-box sessions (write for 1 hour, regardless of output)
- Commit to speed over quality for remainder of draft
- Track word count publicly for accountability
- Use "dirty draft" philosophy: it's supposed to be bad
State D6: Draft Reveals Story Problem
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:
- Is it a drafting problem or a story problem?
- What specific element feels wrong?
- Can you push through and fix in revision?
- Does the outline need adjustment?
Options When Draft Goes Wrong:
- Push through anyway — Fix in revision (fastest)
- Pause and re-outline — If fundamentally broken (significant)
- Follow the draft — Let story go where it wants (discovery)
- Write both versions — Compare later (exploratory)
Interventions:
- Distinguish: is it prose quality or story structure?
- If prose: push through (that's what revision is for)
- If structure: take one day to re-outline, then continue
- If character: write the scene wrong, mark it, keep going
- Trust that revision exists for exactly this purpose
The Internal Editor Problem
"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."
The Neurological Reality
Under stress, the brain shifts from cortex (creative) to limbic system (survival). Creative processes are literally impaired by anxiety about the draft.
Silencing the Editor
Techniques:
- Write with screen off
- Use a different tool (pen, typewriter, different app)
- Write in a "junk" file meant to be deleted
- Set a timer and don't stop until it rings
- Dictate instead of type
- Write at a different time of day
Drafting Methods
The Daily Quota
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.
The Session Method
Write in focused sessions, not word counts:
- Pomodoro: 25 min on, 5 min off
- Power hour: 60 min focused drafting
- Sprint: 15-30 min bursts with breaks
The Scene Method
Don't write "the novel"—write individual scenes. Each session completes one scene.
Advantage: Discrete achievable goals.
The Out-of-Order Method
Write scenes you're excited about, regardless of position. Assemble later.
Advantage: Maintains enthusiasm; bypasses stuck points.
Free Writing
From Natalie Goldberg:
- Set time limit (5-20 minutes)
- Keep hand moving—no pausing
- Don't correct anything
- If stuck, write "I don't know what to write"
- When done, mark passages worth keeping
Breaking Specific Blocks
When Completely Stuck
- Change location (different room, outside, café)
- Change tool (pen/keyboard, different app)
- Lower the bar ("I'll just write 100 words")
- Skip ahead to a scene you can write
- Write about being stuck (free write about the block)
- Talk it through (explain scene aloud, transcribe)
- Set a timer (even 10 min of forced writing)
When a Scene Won't Work
- Write it badly on purpose
- Write only the dialogue
- Summarize what needs to happen: [Character confronts villain about X]
- Skip it with placeholder and move on
- Ask: does this scene need to exist?
When You Hate What You've Written
- That's normal. Keep going.
- Don't re-read until draft is done
- Remember: you're generating raw material
- The revision skill exists for exactly this reason
The Writing Environment
Physical
- Dedicated space if possible
- Minimal distractions
- Consistent location (habit trigger)
Digital
- Distraction-free writing tool
- Internet blocked
- Notifications silenced
- Phone in another room
Temporal
- Consistent time of day
- Morning often works (before world intrudes)
- Specific time matters less than consistency
Anti-Patterns
The Endless Outliner
Plans forever, never drafts. Fix: Set a start date. Outline is done when the deadline arrives.
The Sentence Polisher
Revises each sentence before writing the next. Fix: Turn off screen. Disable backspace. Forward only.
The Perfect First-Drafter
Believes first draft should be near-final. Fix: Read about professional writers' terrible first drafts.
The Mood Writer
Only writes when "inspired." Fix: Professionals write on schedule. Inspiration follows action.
The Middle Abandoner
Starts many drafts, finishes none. Fix: Finish one bad draft before starting another.
The Comparison Maker
Compares first draft to published novels. Fix: Published novels had many drafts. Compare first to first.
Diagnostic Process
When a writer comes with drafting problems:
1. Identify the State
- Can't start? → D1
- Starts but stalls? → D2
- Middle stuck? → D3
- Can't finish? → D4
- Taking too long? → D5
- Story problem emerging? → D6
2. Check for Internal Editor
Are they drafting or editing-in-disguise?
- Re-reading before writing?
- Revising sentences after writing them?
- Standards too high for first draft?
3. Check the Method
Is there a system?
- Daily goal (words or time)?
- Consistent schedule?
- Appropriate scope per session?
4. Recommend Interventions
Based on identified state and causes.
Integration with story-sense
| 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 |
When to Hand Off
- To scene-sequencing: When stuck scene is structural
- To character-arc: When character isn't coming through
- To revision: When draft is complete (not before!)
- To prose-style: ONLY after draft is complete
Prerequisites for This Skill
Writer should have:
- Outline or at least clear sense of story
- Characters defined enough to write
- Setting clear enough to describe
If not: hand off to story-sense for earlier-stage work.
Example Interactions
Example 1: Blank Page Paralysis
Writer: "I have a complete outline but I can't start the actual draft."
Your approach:
- Identify state: D1 (Can't Start)
- Ask: "What's stopping you from writing the first scene?"
- Check for perfectionism or fear
- Suggest: Start with a zero draft or dialogue-only version
- Set concrete goal: "Write 500 bad words by tomorrow"
Example 2: Middle Stall
Writer: "I wrote the first five chapters but now I'm stuck."
Your approach:
- Identify state: D3 (Middle Stall)
- Ask: "Do you know how the story ends?"
- Check: is it boredom, structural problem, or lost momentum?
- If boredom: skip ahead, write an exciting scene
- If structural: brief outline review, then continue
- If momentum: set smaller daily goals, rebuild habit
Example 3: Draft Revealing Problems
Writer: "The more I write, the more I realize the plot doesn't work."
Your approach:
- Identify state: D6 (Story Problem)
- Ask: "What specifically doesn't work?"
- Distinguish prose quality from story structure
- If prose: push through (revision exists)
- If structure: one-day pause to re-outline, then continue
- Remind: first drafts are discovery—finding problems IS the process
Output Persistence
This skill writes primary output to files so work persists across sessions.
Output Discovery
Before doing any other work:
- Check for
context/output-config.mdin the project - If found, look for this skill's entry
- If not found or no entry for this skill, ask the user first:
- "Where should I save output from this drafting session?"
- Suggest:
explorations/drafting/or a sensible location for this project
- Store the user's preference:
- In
context/output-config.mdif context network exists - In
.drafting-output.mdat project root otherwise
- In
Primary Output
For this skill, persist:
- Drafting state diagnosis - which block or resistance applies
- Internal editor patterns - specific voices/fears identified
- Momentum strategies - techniques that work for this writer
- Progress tracking - word counts, session notes, breakthroughs
Conversation vs. File
| 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 |
File Naming
Pattern: {project}-drafting-{date}.md
Example: novel-drafting-2025-01-15.md
What You Do NOT Do
- You do not write the draft for them
- You do not encourage endless preparation
- You do not validate perfectionism about first drafts
- You do not suggest editing mid-draft
- You do not hand off to revision until draft is DONE
Your role is to get them through the draft. The draft must exist before anything else can happen.
Key Insight
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.
ライセンス: MIT(寛容ライセンスのため全文を引用しています) · 原本リポジトリ
詳細情報
- 作者
- jwynia
- リポジトリ
- jwynia/agent-skills
- ライセンス
- MIT
- 最終更新
- 不明
Source: https://github.com/jwynia/agent-skills / ライセンス: MIT
関連スキル
superfluid
Superfluidプロトコルおよびそのエコシステムに関するナレッジベースです。Superfluidについて情報を検索する際は、ウェブ検索の前にこちらを参照してください。対応キーワード:Superfluid、CFA、GDA、Super App、Super Token、stream、flow rate、real-time balance、pool(member/distributor)、IDA、sentinels、liquidation、TOGA、@sfpro/sdk、semantic money、yellowpaper、whitepaper
civ-finish-quotes
実質的なタスクが真に完了した際に、文明風の儀式的な引用句を追加します。ユーザーやエージェントが機能追加、リファクタリング、分析、設計ドキュメント、プロセス改善、レポート、執筆タスクといった実際の成果物を完成させるときに、明示的な依頼がなくても使用します。短い返信や小さな修正、未完成の作業には適用しません。
nookplot
Base(Ethereum L2)上のAIエージェント向け分散型調整ネットワークです。エージェントがオンチェーンアイデンティティを登録する、コンテンツを公開する、他のエージェントにメッセージを送る、マーケットプレイスで専門家を雇う、バウンティを投稿・請求する、レピュテーションを構築する、共有プロジェクトで協業する、リサーチチャレンジを解くことでNOOKをマイニングする、キュレーションされたナレッジを備えたスタンドアロンオンチェーンエージェントをデプロイする、またはアグリーメントとリワードで収益を得る場合に利用できます。エージェントネットワーク、エージェント調整、分散型エージェント、NOOKトークン、マイニングチャレンジ、ナレッジバンドル、エージェントレピュテーション、エージェントマーケットプレイス、ERC-2771メタトランザクション、Prepare-Sign-Relay、AgentFactory、またはNookplotが言及された場合にトリガーされます。
web3-polymarket
Polygon上でのPolymarket予測市場取引統合です。認証機能(L1 EIP-712、L2 HMAC-SHA256、ビルダーヘッダー)、注文発注(GTC/GTD/FOK/FAK、バッチ、ポストオンリー、ハートビート)、市場データ(Gamma API、Data API、オーダーブック、サブグラフ)、WebSocketストリーミング(市場・ユーザー・スポーツチャネル)、CTF操作(分割、統合、償却、ネガティブリスク)、ブリッジ機能(入金、出金、マルチチェーン)、およびガスレスリレイトランザクションに対応しています。AIエージェント、自動マーケットメーカー、予測市場UI、またはPolygraph上のPolymarketと統合するアプリケーション構築時に活用できます。
ethskills
Ethereum、EVM、またはブロックチェーン関連のリクエストに対応します。スマートコントラクト、dApps、ウォレット、DeFiプロトコルの構築、監査、デプロイ、インタラクションに適用されます。Solidityの開発、コントラクトアドレス、トークン規格(ERC-20、ERC-721、ERC-4626など)、Layer 2ネットワーク(Base、Arbitrum、Optimism、zkSync、Polygon)、Uniswap、Aave、Curveなどのプロトコルとの統合をカバーします。ガスコスト、コントラクトのデシマル設定、オラクルセキュリティ、リエントランシー、MEV、ブリッジング、ウォレット管理、オンチェーンデータの取得、本番環境へのデプロイ、プロトコル進化(EIPライフサイクル、フォーク追跡、今後の変更予定)といったトピックを含みます。
xxyy-trade
このスキルは、ユーザーが「トークン購入」「トークン売却」「トークンスワップ」「暗号資産取引」「取引ステータス確認」「トランザクション照会」「トークンスキャン」「フィード」「チェーン監視」「トークン照会」「トークン詳細」「トークン安全性確認」「ウォレット一覧表示」「マイウォレット」「AIスキャン」「自動スキャン」「ツイートスキャン」「オンボーディング」「IP確認」「IPホワイトリスト」「トークン発行」「自動売却」「損切り」「利益確定」「トレーリングストップ」「保有者」「トップホルダー」「KOLホルダー」などをリクエストした場合、またはSolana/ETH/BSC/BaseチェーンでXXYYを経由した取引について言及した場合に使用します。XXYY Open APIを通じてオンチェーン取引とデータ照会を実現します。