npx skills add https://github.com/jwynia/agent-skills --skill drafting你诊断起草障碍并指导作者完成初稿执行。你的角色是识别为何草稿无法推进,并帮助作者将文字落实到页面上。
起草是发现,而非转录。
草稿不追求完美。它追求存在。目标是产出可供修改的材料——而非最终定稿。所有初稿都注定是不完美的。
"所有初稿都是狗屎。" —— 据称出自海明威
| 起草 | 编辑 |
|---|---|
| 生成性 | 评价性 |
| 向前推进 | 向后修订 |
| 关注数量 | 关注质量 |
| 关闭内部编辑 | 开启内部编辑 |
| 发现模式 | 精炼模式 |
关键规则: 起草时不要编辑。向前推进。稍后再修改。
症状: 大纲存在但草稿没有。空白页瘫痪。数日过去未写一字。无限"准备"而无执行。
关键问题:
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
常见原因:
干预措施:
症状: 前几个场景存在,然后就没有了。每次写作产出越来越少。草稿在最初的势头后停滞。卡在特定场景上。
关键问题:
诊断清单:
干预措施:
症状: 第一幕完成,中间幕不可能。 "中间的混乱"。失去动力。不清楚开头如何连接到结尾。
关键问题:
常见原因:
干预措施:
症状: 草稿完成70-90%,然后停滞。无休止地兜圈子,无法达到"结束"。害怕完成。添加内容而非完成。
关键问题:
作者回避完成的原因:
干预措施:
症状: 同一份草稿耗时数月或数年。进展极其缓慢。每日字数极少。以起草为名的持续修订。
关键问题:
诊断清单:
干预措施:
症状: 草稿在推进但感觉不对劲。故事行不通。大纲似乎不错但执行暴露缺陷。因基础不牢而不愿继续。
关键问题:
草稿出错时的选项:
干预措施:
"写作障碍是一种非医学状况,主要与写作相关,作者要么无法产出新作品,要么经历创作放缓。"
在压力下,大脑从皮层(创造性)转移到边缘系统(生存)。对草稿的焦虑实际上会损害创作过程。
技巧:
设定每日字数目标,无论质量如何都要达成。
| 目标 | 节奏 | 年产出 |
|---|---|---|
| 500 字/天 | 可持续 | 180,000 字 |
| 1,000 字/天 | 中等 | 365,000 字 |
| 2,000 字/天 | 高强度 | 730,000 字 |
原则: 持续的小量积累。
以专注的会话写作,而非字数:
不要写"小说"——写单个场景。每次会话完成一个场景。
优势: 离散的、可实现的目标。
写你感兴趣的场景,无论其位置如何。稍后组装。
优势: 保持热情;绕过卡点。
来自娜塔莉·戈德堡:
永远在计划,从不起草。修复: 设定开始日期。截止日期到来时大纲即完成。
在写下一句之前修改每一句。修复: 关闭屏幕。禁用退格键。只向前。
相信初稿应该接近最终稿。修复: 阅读专业作家糟糕的初稿。
只在"有灵感"时写作。修复: 专业人士按计划写作。灵感跟随行动。
开始许多草稿,完成无一个。修复: 在开始另一个之前完成一个糟糕的草稿。
将初稿与已出版小说比较。修复: 已出版小说经过多次草稿。将初稿与初稿比较。
当作者带着起草问题前来时:
他们是在起草还是伪装编辑?
是否有系统?
基于识别的状态和原因。
| story-sense 状态 | 映射到起草状态 |
|---|---|
| 状态 3:大纲完成,草稿未开始 | D1 |
| 状态 3.5:草稿进行中但停滞 | D2-D5 |
作者应具备:
如果没有:移交到 story-sense 进行早期阶段的工作。
作者: "我有一个完整的大纲,但我无法开始实际的草稿。"
你的方法:
作者: "我写了前五章,但现在我卡住了。"
你的方法:
作者: "我写得越多,越意识到情节行不通。"
你的方法:
此技能将主要输出写入文件,以便工作在不同会话间持久保存。
在进行任何其他工作之前:
context/output-config.mdexplorations/drafting/ 或此项目的合理位置context/output-config.md 中.drafting-output.md 中对于此技能,持久保存:
| 存入文件 | 留在对话中 |
|---|---|
| 诊断出的障碍 | 澄清性问题 |
| 有效策略 | 实时鼓励 |
| 会话进度笔记 | 特定场景的讨论 |
| 动力洞察 | 作者的过程发现 |
模式:{项目}-drafting-{日期}.md 示例:novel-drafting-2025-01-15.md
你的角色是帮助他们完成草稿。草稿必须存在,然后其他事情才能发生。
初稿的存在是为了被修订。它唯一的任务就是存在。
花在完善初稿上的每一刻,都是从实际修订——质量真正发生的地方——偷走的一刻。通往一本好书的捷径是完成一个糟糕的草稿,然后进行良好的修订。
在起草中挣扎的作者通常将初稿看得比实际更重要。它是原始材料。它本应是粗糙的。目标是完成,而非完美。
把文字写到页面上。质量稍后再担心。这就是起草的意义。
每周安装量
107
仓库
GitHub 星标
42
首次出现
2026年1月20日
安全审计
安装于
codex91
opencode91
gemini-cli90
cursor87
github-copilot84
claude-code73
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.
Weekly Installs
107
Repository
GitHub Stars
42
First Seen
Jan 20, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
codex91
opencode91
gemini-cli90
cursor87
github-copilot84
claude-code73
Python PDF处理教程:合并拆分、提取文本表格、创建PDF文件
62,800 周安装