post-outliner

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Post Outliner Skill

Post Outliner Skill（博客大纲生成Skill）

Operator Context

操作上下文

This skill operates as an operator for blog post planning, configuring Claude's behavior for creating structural blueprints that ensure posts have logical flow and appropriate scope. It implements the Structured Analysis pattern -- assess topic, select template, generate outline, validate structure.

本Skill作为博客文章规划的操作器，配置Claude的行为以创建结构蓝图，确保文章具备逻辑连贯性和合适的篇幅。它采用结构化分析模式——评估主题、选择模板、生成大纲、验证结构。

Hardcoded Behaviors (Always Apply)

硬编码行为（始终适用）

CLAUDE.md Compliance: Read and follow repository CLAUDE.md before outlining
Over-Engineering Prevention: Outline only what was asked. No speculative series planning, no "while I'm here let me plan 5 more posts"
Structure First: ALWAYS select a structure template before generating content
Word Count Estimates: Every section MUST include estimated word counts
your blog Identity: Posts are technical, deep, problem-solving focused -- no fluff or filler
Alternative Structures: Always offer at least one alternative structure type
Assess Before Outline: NEVER generate an outline without understanding the topic's core problem or value proposition first

CLAUDE.md 合规性：在生成大纲前阅读并遵循仓库中的CLAUDE.md
避免过度设计：仅按要求生成大纲。不进行推测性的系列规划，不额外规划更多文章
先定结构：务必先选择结构模板再生成内容
字数统计：每个小节必须包含预估字数
博客定位：文章需具备技术性、深度且聚焦问题解决——无冗余内容
备选结构：始终提供至少一种备选结构类型
先评估再大纲：绝不在未理解主题核心问题或价值主张的情况下生成大纲

Default Behaviors (ON unless disabled)

默认行为（默认开启，可关闭）

Section Summaries: Include 2-3 sentence summaries per section
Reading Time: Calculate and display estimated reading time (~250 wpm)
Complete Output: Show full outline in formatted report block
Template Matching: Auto-detect best structure from topic description
Hugo Frontmatter: Include title, date, tags, summary planning
Logical Flow Validation: Verify each section builds on the previous

小节摘要：每个小节包含2-3句摘要
阅读时长：计算并显示预估阅读时长（约250词/分钟）
完整输出：以格式化报告块展示完整大纲
模板匹配：根据主题描述自动检测最合适的结构
Hugo Frontmatter：包含标题、日期、标签、摘要的规划
逻辑连贯性验证：验证每个小节是否基于前一小节展开

Optional Behaviors (OFF unless enabled)

可选行为（默认关闭，可开启）

Minimal Mode: Just section headers, no summaries
Deep Mode: Expand to sub-section level with bullet points
Series Mode: Plan multi-part post series with dependencies

极简模式：仅显示小节标题，无摘要
深度模式：扩展至子小节层级，使用项目符号
系列模式：规划带依赖关系的多部分文章系列

What This Skill CAN Do

本Skill可实现的功能

Analyze topic briefs and identify the core "vex" or value proposition
Select the most appropriate structure template for the content
Generate structured outlines with section summaries and word counts
Estimate reading time and validate scope
Suggest alternative structures for the same topic
Handle Hugo frontmatter planning (title, tags, summary)
Validate logical flow between sections

分析主题摘要并识别核心痛点或价值主张
为内容选择最合适的结构模板
生成包含小节摘要和字数统计的结构化大纲
预估阅读时长并验证篇幅范围
为同一主题提供备选结构建议
处理Hugo Frontmatter规划（标题、标签、摘要）
验证小节间的逻辑连贯性

What This Skill CANNOT Do

本Skill不可实现的功能

Write actual post content (use
```
blog-post-writer
```
for that)
Edit existing posts (use
```
anti-ai-editor
```
for style fixes)
Guarantee SEO optimization (focus is structure, not keywords)
Plan non-blog content like documentation or README files
Create outlines without understanding the topic first -- always assess

撰写实际文章内容（请使用
```
blog-post-writer
```
）
编辑已有文章（请使用
```
anti-ai-editor
```
进行风格修正）
保证SEO优化（聚焦结构而非关键词）
规划非博客内容，如文档或README文件
在未先理解主题的情况下生成大纲——始终先评估

Instructions

使用说明

Phase 1: ASSESS

阶段1：评估

Goal: Understand the topic deeply before selecting any structure.

Step 1: Read the topic brief

Identify these elements:

The core "vex" (frustration/problem being solved)
The value proposition for readers
Any constraints (length, audience, etc.)

Step 2: Ask key questions

markdown

undefined

目标：在选择任何结构前深入理解主题。

步骤1：阅读主题摘要

识别以下要素：

核心痛点（需解决的挫败/问题）
为读者提供的价值主张
任何约束条件（篇幅、受众等）

步骤2：提出关键问题

markdown

undefined

Topic Assessment

主题评估

Problem: [What problem does this solve?] Audience: [Who encounters this problem?] Insight: [What's the key insight or solution?] Scope: [Single post or potential series?]


If the topic brief is too vague to answer these, ask clarifying questions BEFORE proceeding:
- "What specific problem did you encounter?"
- "What did you learn?"
- "Who is the audience?"

**Gate**: Core problem/value identified. Topic is specific enough to outline. Proceed only when gate passes.

问题：[此内容解决了什么问题？] 受众：[谁会遇到这个问题？] 洞察：[核心洞察或解决方案是什么？] 范围：[单篇文章或潜在系列？]


如果主题摘要过于模糊，无法回答这些问题，请先提出澄清问题再继续：
- "你遇到了什么具体问题？"
- "你有什么收获？"
- "受众是谁？"

**准入条件**：已明确核心问题/价值。主题足够具体可生成大纲。仅当满足条件时才可继续。

Phase 2: DECIDE

阶段2：决策

Goal: Select the right structure template and scope.

Step 1: Match template to content

Situation	Template	Why
Debugging story	Problem-Solution	Natural narrative arc
Explaining a concept	Technical Explainer	Clear progression
Teaching a process	Walkthrough	Step-by-step clarity
Comparing options	Comparison	Structured evaluation
Mixed content	Hybrid	Combine as needed

See

references/structure-templates.md

for full template details with section breakdowns, signal words, and examples.

Step 2: Set scope parameters

Post Type	Target Words	Sections
Quick fix	600-800	3
Standard post	1,000-1,500	4-5
Deep dive	1,500-2,500	5-7
Tutorial	1,200-2,000	5-6
Series part	800-1,200	3-4

Gate: Template selected, scope defined. Proceed only when gate passes.

目标：选择合适的结构模板和篇幅范围。

步骤1：匹配内容与模板

场景	模板	原因
调试经历	问题-解决方案	符合自然叙事逻辑
概念讲解	技术讲解	清晰的递进结构
流程教学	分步指南	步骤清晰易懂
选项对比	对比分析	结构化评估
混合内容	混合结构	根据需求组合使用

完整模板详情（含小节拆分、标志性词汇和示例）请参阅

references/structure-templates.md

。

步骤2：设置篇幅参数

文章类型	目标字数	小节数量
快速修复	600-800	3
标准文章	1,000-1,500	4-5
深度剖析	1,500-2,500	5-7
教程	1,200-2,000	5-6
系列文章单篇	800-1,200	3-4

准入条件：已选择模板，定义好范围。仅当满足条件时才可继续。

Phase 3: GENERATE

阶段3：生成

Goal: Produce the complete outline in standard format.

Generate the outline in this exact format:

===============================================================
 OUTLINE: [Working Title]
===============================================================

 Structure: [Template Name]
 Estimated Length: [X,XXX-X,XXX] words (~[N] min read)

 FRONTMATTER:
   title: "[Working Title]"
   date: [YYYY-MM-DD]
   tags: ["tag1", "tag2", "tag3"]
   summary: "[1-2 sentence summary for list views]"

 SECTIONS:

 1. [Section Title] [XXX-XXX words]
    [2-3 sentence summary describing what this section covers
    and what value it provides to the reader.]

 2. [Section Title] [XXX-XXX words]
    [2-3 sentence summary describing what this section covers
    and what value it provides to the reader.]

 [Continue for all sections]

===============================================================
 ALTERNATIVE STRUCTURES:

 -> [Template Name]: [1-sentence explanation of how this
    structure would approach the same topic differently]
 -> [Template Name]: [1-sentence explanation]
===============================================================

Gate: Outline complete with all required elements. Proceed only when gate passes.

目标：以标准格式生成完整大纲。

请严格按照以下格式生成大纲：

===============================================================
 大纲：[暂定标题]
===============================================================

 结构：[模板名称]
 预估篇幅：[X,XXX-X,XXX] 词（约[N]分钟阅读时长）

 FRONTMATTER:
   title: "[暂定标题]"
   date: [YYYY-MM-DD]
   tags: ["tag1", "tag2", "tag3"]
   summary: "[列表视图用1-2句摘要]"

 小节：

 1. [小节标题] [XXX-XXX词]
    [2-3句摘要，说明本小节涵盖内容及为读者提供的价值。]

 2. [小节标题] [XXX-XXX词]
    [2-3句摘要，说明本小节涵盖内容及为读者提供的价值。]

 [继续列出所有小节]

===============================================================
 备选结构：

 -> [模板名称]：[1句话说明该结构如何以不同方式呈现同一主题]
 -> [模板名称]：[1句话说明]
===============================================================

准入条件：大纲包含所有必填要素。仅当满足条件时才可继续。

Phase 4: VALIDATE

阶段4：验证

Examples

示例

Example 1: Debugging Topic

示例1：调试主题

User says: "Spent 3 hours debugging why Hugo builds locally but fails on Cloudflare" Actions:

Assess: Core vex is environment mismatch, audience is Hugo users (ASSESS)
Match: Debugging story maps to Problem-Solution template (DECIDE)
Generate: 4-section outline with word counts (GENERATE)
Validate: Logical flow, specific section names, scope appropriate (VALIDATE) Result: Structured outline with Problem-Solution template, ~1,200-1,500 words

用户需求：“我花了3小时调试为什么Hugo在本地构建正常，但在Cloudflare上失败” 操作步骤：

评估：核心痛点是环境不匹配，受众是Hugo用户（评估阶段）
匹配：调试经历对应问题-解决方案模板（决策阶段）
生成：4小节大纲，带字数统计（生成阶段）
验证：逻辑连贯、小节名称具体、范围合适（验证阶段）结果：采用问题-解决方案模板的结构化大纲，约1,200-1,500词

Example 2: Concept Explanation

示例2：概念讲解

User says: "Want to explain how Go 1.22 changed loop variables" Actions:

Assess: Value is understanding a language change, audience is Go devs (ASSESS)
Match: Concept explanation maps to Technical Explainer (DECIDE)
Generate: 4-section outline with code example notes (GENERATE)
Validate: Technical depth appropriate, no fluff sections (VALIDATE) Result: Structured outline with Technical Explainer template, ~1,400-1,700 words

See

references/examples.md

for complete outline examples with full formatting.

用户需求：“想解释Go 1.22如何改变循环变量” 操作步骤：

评估：价值是让用户理解语言变更，受众是Go开发者（评估阶段）
匹配：概念讲解对应技术讲解模板（决策阶段）
生成：4小节大纲，含代码示例说明（生成阶段）
验证：技术深度合适、无冗余小节（验证阶段）结果：采用技术讲解模板的结构化大纲，约1,400-1,700词

完整格式的大纲示例请参阅

references/examples.md

。

Error Handling

错误处理

Error: "Topic Too Vague"

错误：“主题过于模糊”

Cause: User provides broad topic without specific angle (e.g., "write about Kubernetes") Solution:

Ask clarifying questions: "What specific problem with Kubernetes?"
Suggest prompts: "What frustrated you? What did you learn?"
Do NOT generate a generic outline -- wait for specifics

原因：用户提供宽泛主题，无具体角度（如“写关于Kubernetes的内容”）解决方案：

提出澄清问题：“关于Kubernetes的什么具体问题？”
建议明确的提示：“你遇到了什么困扰？有什么收获？”
请勿生成通用大纲——等待具体信息

Error: "Topic Too Broad for Single Post"

错误：“主题过于宽泛，不适用于单篇文章”

Cause: Topic covers too much ground for target word count Solution:

Identify the single key insight
Suggest splitting into a series with clear part boundaries
Recommend focusing the outline on the core insight only

原因：主题涵盖内容过多，超出目标字数范围解决方案：

识别核心洞察
建议拆分为系列文章，明确各部分边界
建议将大纲聚焦于核心洞察

Error: "No Clear Structure Fit"

错误：“无合适的匹配结构”

Cause: Topic doesn't map cleanly to any single template Solution:

Use hybrid approach combining elements from multiple templates
See
```
references/structure-templates.md
```
for hybrid templates
Prioritize the dominant content type when choosing base structure

原因：主题无法清晰匹配任何单一模板解决方案：

采用混合方法，结合多个模板的要素
参阅
```
references/structure-templates.md
```
中的混合模板
选择基础结构时优先考虑主导内容类型

Error: "Estimated Length Exceeds Target"

错误：“预估篇幅超出目标”

Cause: Too many sections or sections scoped too broadly Solution:

Merge thin sections that cover similar ground
Cut sections that don't directly serve the core insight
Suggest multi-part series if content genuinely requires depth

原因：小节过多或小节范围过宽解决方案：

合并内容相似的单薄小节
删除不直接服务于核心洞察的小节
若内容确实需要深度，建议拆分为多部分系列

Anti-Patterns

反模式

Anti-Pattern 1: Outline Without Understanding

反模式1：未理解主题即生成大纲

What it looks like: Generating a generic outline immediately after receiving a broad topic like "Kubernetes" Why wrong: No specific value proposition, no your blog identity. Produces hollow structure without substance. Do instead: Complete Phase 1 ASSESS first. Ask clarifying questions. Identify the specific problem and insight before touching structure.

表现：收到宽泛主题（如“Kubernetes”）后立即生成通用大纲问题：无具体价值主张，不符合博客定位。生成的结构空洞无物。 正确做法：先完成阶段1的评估。提出澄清问题。在涉及结构前先明确具体问题和洞察。

Anti-Pattern 2: Too Many Thin Sections

反模式2：过多单薄小节

What it looks like: 8+ sections with Introduction, Background, Context, Problem Statement each at 100 words Why wrong: your blog cuts to the chase. Multiple thin sections dilute impact and pad length without adding value. Do instead: Merge related sections. Start with the vex. Aim for 3-7 substantive sections.

表现：8个以上小节，包括引言、背景、上下文、问题陈述等，每个仅100词问题：博客需开门见山。多个单薄小节会稀释影响力，增加无意义篇幅。 正确做法：合并相关小节。从痛点切入。目标为3-7个有实质内容的小节。

Anti-Pattern 3: Generic Section Names

反模式3：通用小节名称

What it looks like: "Introduction", "Main Content", "Details", "Conclusion" Why wrong: Section names should communicate content at a glance. Generic names reveal nothing about what the reader gains. Do instead: Use specific, descriptive names like "Hugo Builds Fail on Cloudflare" instead of "The Problem".

表现：“引言”“主要内容”“细节”“结论” 问题：小节名称应一目了然地传达内容。通用名称无法体现读者能获得的价值。 正确做法：使用具体的描述性名称，如“Hugo在Cloudflare上构建失败”而非“问题”。

Anti-Pattern 4: Missing Word Counts

反模式4：缺少字数统计

What it looks like: Sections listed without any size estimates Why wrong: Cannot validate scope, cannot estimate reading time, cannot identify sections that are too heavy or too light. Do instead: Every section gets a word count range. Totals must add up to overall estimate.

表现：列出小节但无任何篇幅预估问题：无法验证范围、预估阅读时长、识别过重或过轻的小节。 正确做法：每个小节都要有字数范围。总和必须与整体预估一致。

References

参考资料

This skill uses these shared patterns:

Anti-Rationalization - Prevents shortcut rationalizations
Verification Checklist - Pre-completion checks

本Skill采用以下共享模式：

反合理化 - 防止捷径式合理化
验证清单 - 完成前检查

Domain-Specific Anti-Rationalization

领域特定反合理化

Rationalization	Why It's Wrong	Required Action
"Topic is clear enough, skip assessment"	Vague topics produce generic outlines	Complete Phase 1 ASSESS with key questions
"One structure is fine, no need for alternatives"	Author should choose from options	Always include ALTERNATIVE STRUCTURES section
"Word counts are rough, close enough"	Section totals must match overall estimate	Verify arithmetic before presenting
"Generic section names work for now"	Names reveal outline quality and thinking depth	Use specific, content-descriptive names
"Just one more section won't hurt"	Section bloat dilutes impact	Justify every section's existence against core insight

合理化借口	问题所在	要求操作
“主题足够清晰，跳过评估”	模糊主题会生成通用大纲	完成阶段1的评估，提出关键问题
“一种结构就够了，无需备选”	作者应拥有选择空间	始终包含备选结构部分
“字数统计只是粗略估计，差不多就行”	小节总和必须与整体预估一致	提交前验证计算结果
“通用小节名称暂时能用”	名称体现大纲质量和思考深度	使用具体的、描述内容的名称
“再加一个小节也没关系”	小节膨胀会稀释影响力	针对核心洞察证明每个小节存在的必要性

Reference Files

参考文件

```
${CLAUDE_SKILL_DIR}/references/structure-templates.md
```
: Complete template library with section breakdowns and signal words
```
${CLAUDE_SKILL_DIR}/references/examples.md
```
: Real outlines from your blog posts demonstrating proper format

```
${CLAUDE_SKILL_DIR}/references/structure-templates.md
```
：完整模板库，含小节拆分和标志性词汇
```
${CLAUDE_SKILL_DIR}/references/examples.md
```
：来自博客文章的真实大纲示例，展示正确格式