Path: Writing & expression
Goal: Route outbound writing through outline and edit passes—less filler, less AI voice, facts frozen first.
Best for: Anyone whose chats jump straight to “write this for me” and then spend longer cleaning the result.
This path is a journey through existing guides. Follow the order for one real deliverable this week (a launch note, a weekly update, or a bilingual email).
Follow writing guides in order when you are new; skip ahead only if you can already pass the earlier Practice now tasks.
Scene tip: Title calendar blocks with guide slugs so the path is a rhythm, not a bookmark folder.
Why beginners skip this
Saving the writing-path link feels finished—without outline and read-aloud this week, nothing sticks.
Why this order
Outline before prose, then one voice edit; jumping straight to prose feels good until gaps and filler explode at send. 2. Draft & revise — separate generations from edits. 3. Claude email polish — tone when stakes are relational. 4. Optional Grok spark — angles only; facts stay frozen. 5. Anti-slop + outline habits — keep the voice yours.
Suggested sequence (click through)
1. Clear everyday prompts 2. Outline before prose 3. Draft & revise 4. Email correct → polished (Claude) 5. Reject AI slop 6. Optional spark: Informal brainstorm (Grok) 7. Bonus: Stakeholder update · Bilingual HK
Checkpoint before send
- Outline existed (even five bullets).
- Facts frozen on paper; model did not invent metrics.
- One human-only detail added.
- Tone pass done where relationship stakes are high (often Claude).
- Disclosure added if your audience expects it.
Rule of thumb
Brainstorm anywhere → freeze facts → polish where tone matters (often Claude) → you add one human detail only you know before send.
Example
Filled prompt
Live artifact this week for: Ship clearer drafts faster—emails, posts, outlines—without AI sludge.
Name real files/people. No invented facts; label Unknowns; stop before send/delete.
Return working prompt + one pass/fail check I can mark in a minute.
What good output looks like
- Calendar slot titled with slug for “Ship clearer drafts faster—emails, posts, outlines”
- Live artifact opened — not only the bookmark
- Practice timed; refuse-line written
- Pass/fail: artifact dated Asia/Shanghai
Example
Filled prompt
Diagnose why my drafts sound generic using this path’s edit-pass ideas.
Give 5 checks I can run in 10 minutes on a real customer email (tone, facts frozen, one human detail, CTA clarity, no AI fillers).
Email topic: delay notice for a Friday delivery window.
What good output looks like
- Live artifact opened — not only the bookmark
- Practice timed; refuse-line written
- Pass/fail: artifact dated Asia/Shanghai
- Calendar slot titled with slug for “Ship clearer drafts faster—emails, posts, outlines”
Save this card
Card: outline → freeze facts → one human detail → send. Stop twice on the path before send.
Before you start
Create a 25-minute calendar block titled path-writing. Open the live artifact for “Ship clearer drafts faster—emails, posts, outlines—without A”—bookmark alone does not count Keep the live artifact visible the whole time. If you only have a blank box, stop and fetch the real job first
How to use this week
This week run outline → prose → read-aloud on a real draft along the path; no checkmark without read-aloud.
Close the week by quoting aloud the refuse line you actually used once. If you cannot, rerun Practice now and date the pass/fail (Asia/Shanghai).
Keep it real
Run this guide’s Practice now on work you will actually ship this week—not a fictional scenario. Dated notes beat perfect theory.
Human detail last
Before send, add one fact only you know. That is the anti-sludge seal.
Do not bookmark-only
Finish Practice now, then tick this guide on your path. Titles unread are not skills.
Close the loop
Write one line: next time I only save the path with no outline, I refuse the checkmark.
Example
Filled prompt
Fri path slot: stakeholder update for Checkout API Yellow.
Use writing-stakeholder-update guide. Freeze facts first. ≤150 words.
Outline before prose; freeze facts; no invented offers.
What good output looks like
- Calendar slot titled with slug for “Ship clearer drafts faster—emails, posts, outlines”
- Pass/fail: artifact dated Asia/Shanghai
- Live artifact opened — not only the bookmark
- Practice timed; refuse-line written [path-writing#3]
Example
Filled prompt
Mon writing slot: outline-before-prose on a 10-line client email you owe.
Five bullets offline first. Reject extra promises in draft.
Outline before prose; freeze facts; no invented offers.
What good output looks like
- Practice timed; refuse-line written
- Calendar slot titled with slug for “Ship clearer drafts faster—emails, posts, outlines”
- Pass/fail: artifact dated Asia/Shanghai
- Live artifact opened — not only the bookmark
Red flag
Saving the writing-path link with no outline or read-aloud leaves nothing—ship the outline first.
Pitfalls
| Pitfall | Fix |
|---|---|
| Skipping outline because “it’s short” | Short pieces still get 5 bullets |
| Polishing rumors | Verify before tone |
| Using Grok tone as official PR | Hand off to review path |
Practice now
Kill adverb pass: cut five unnecessary adverbs (Asia/Shanghai).
Audience swap read: reread as the skeptic reader (Asia/Shanghai).
Cut opener: delete the first throat-clearing paragraph (Asia/Shanghai).
Lead sentence: first sentence states the ask without throat-clearing (Asia/Shanghai).
Reader test: give the outline to someone else; note the first confusion (Asia/Shanghai).
Cut-20 drill: after draft, cut 20% words without losing claims (Asia/Shanghai).
Writing-path drill: outline five bullets before prose; delete any bullet you cannot source (Asia/Shanghai).
Thin-spot drill: rewrite the Save card with real nouns from your work (repo, doc, inbox). Generic placeholders fail the drill.
Tonight run outline → draft → edit on a real piece; no checkmark without an outline.
Today card (copy) — path-writing: 1. Artifact I will produce: ___ 2. Pass/fail check: ___ 3. Refuse-line if tempted to skip verify/send: ___ (date: Asia/Shanghai) 4. One never-do from this guide: ___
Extra pass: do the card on a real file today—reading alone does not count.
One sentence takeaway
Outline → prose → read-aloud; no checkmark without read-aloud.
Next
Outline before prose · Reject AI slop · Draft & revise · Email polish · Edit pass voice · Clear everyday prompts
路径:写作与表达
目标: 外发写作先走大纲与编辑轮;少空话、少 AI 腔,事实先冻结。
适合: 客户邮件、落地页、通讯写到一半就「再优化」到糊的人。
今晚路径上最多停两处。事实钉住再谈语气。
为什么这个顺序
先大纲再成文,再做一轮语气编辑;直接成文一时爽,缺口和套话常在发送前爆。 2. 起草与修改:生成与编辑分开。 3. Claude 邮件抛光:关系型语气。 4. 可选 Grok 火花:只要角度;事实冻结。 5. 拒套话 + 提纲习惯:声音仍是你的。
为什么新手跳过
收藏写作路径标题像进步;本周没有大纲与读出声,什么都没留下。
建议顺序(点进去)
1. 日常清楚提示词 2. 先提纲后成文 3. 起草与修改 4. 邮件从正确到得体(Claude) 5. 主动干掉 AI 套话 6. 可选火花:非正式头脑风暴(Grok) 7. 加分:干系人更新 · 港/双语实务
发送前检查点
- 有过大纲(哪怕五条)。
- 事实冻在纸上;模型没编指标。
- 加了一句只有人知道的细节。
- 关系型场合做过语气轮(常用 Claude)。
- 读者需要时已加披露。
经验法则
哪里都能头脑风暴 → 冻结事实 → 在语气重要处抛光(常用 Claude)→ 发出前加一句只有你知道的真人细节。
实例
填好的提示词
我今天要写客户邮件(涨价说明)。路径上最多停 2 处:应停哪里,复用哪条提示词习惯?
先大纲后编辑;事实冻结;禁止编造优惠。
边界:不编造;未知标 [?];发送前停下。
完成检查:一分钟内能判过/不过。
像样的输出大概长这样
- 最多停 2 处,并点名路径上的具体习惯(如大纲→编辑轮)
- 复用哪条提示词习惯写清楚,不空喊「多改几遍」
- 贴合「客户邮件」场景,务实可执行
- 像今晚发信前的导航,不是写作课大纲
- 不把整条写作轨一次塞进来
- 未知标出;不编造负责人、日期或指标
实例
填好的提示词
用本路径的编辑轮思路,诊断这篇草稿为什么读起来很空。
给我 5 条能在 10 分钟内对真实客户邮件跑完的检查(语气、事实冻结、一句人情细节、CTA 清晰、无 AI 填充)。
邮件主题:周五配送窗口延误通知。
像样的输出大概长这样
- 正好 5 条检查:语气、事实冻结、人情细节、CTA、无 AI 填充
- 每条能在 10 分钟内对「周五配送延误通知」跑一遍
- 连到本路径的编辑轮思路,不另起炉灶
- 检查项可打勾,不是抽象形容词
- 读完能立刻打开那封真实草稿开改
- 一分钟内能对照清单判过/不过;缺项标红再继续
保存这张卡
记下:编辑轮禁用填充三词 + 今天管用的 CTA 句式。
开始前
写清读者与必须保留的事实清单,再打开模型。
本周怎么用
本周按路径对一篇真稿跑大纲→正文→读出声;没有读出声不打勾。
保持真实
用本周真要交付的工作做「现在就练一次」,别编假场景。带日期的实操笔记,比完美理论有用。
最后加人情细节
发送前加一句只有你知道的事实。那是防空话封印。
不要只收藏
先做完「现在就练一次」,再在学习路径上打勾。只收藏不练,标题变不成技能。
闭环
写下一行:下次只收藏路径不交大纲,我拒绝打勾。
红旗
收藏写作路径却没有大纲与读出声,什么都没留下;先交大纲。
常见坑
| 坑 | 改法 |
|---|---|
| 路径上到处停 | 今晚最多两处(大纲→编辑轮) |
| 「再优化」代替编辑轮 | 用可打勾的五条检查 |
| 事实未冻结就外发 | 先钉事实,再谈语气 |
现在就练一次
今晚就练:对一篇真稿跑大纲→正文→读出声;没有读出声不打勾。
一句话带走
大纲→正文→读出声;没有读出声不打勾。
下一步
← Back to home · Learn · Tools · Compare · Start