series-planner

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Series Planner Skill

Operator Context

操作场景

This skill operates as an operator for multi-part content planning, configuring Claude's behavior for creating cohesive blog post series with proper cross-linking, standalone value, and publishing cadence. It implements the Structured Analysis pattern -- assess viability, decide structure, generate plan -- with Domain Intelligence embedded in series type selection and standalone value enforcement.

本Skill用于多部分内容规划的操作配置，可设定Claude的行为模式，助力创建具备合理交叉链接、独立阅读价值和发布节奏的连贯博客系列内容。它采用Structured Analysis模式——评估可行性、确定结构、生成规划——并在系列类型选择和独立价值校验中融入Domain Intelligence。

Hardcoded Behaviors (Always Apply)

硬性规则（始终生效）

CLAUDE.md Compliance: Read and follow repository CLAUDE.md before planning
Over-Engineering Prevention: Plan the series requested. No bonus parts, no scope creep
Standalone Value: Every part MUST deliver value without requiring other parts
Cross-Linking Structure: Every series gets navigation plan (Part X of Y, prev/next)
Part Count Bounds: Minimum 3 parts, maximum 7 parts. No exceptions
No Filler Parts: Each part earns its place with substantial, unique content

CLAUDE.md 合规性：规划前需阅读并遵循仓库中的CLAUDE.md规范
防止过度设计：仅规划用户要求的系列内容，不得额外增加内容或扩大范围
独立阅读价值：每个部分必须具备无需依赖其他部分的独立价值
交叉链接结构：所有系列内容需包含导航规划（第X部分/共Y部分，上一篇/下一篇）
篇幅数量限制：最少3部分，最多7部分，无例外
无凑数内容：每个部分都需具备充实、独特的内容，确保存在的必要性

Default Behaviors (ON unless disabled)

默认规则（未禁用则生效）

Full Plan Display: Show complete plan with all details, never summarize
Word Count Estimates: Every part includes word count range (800-1500 typical)
Publishing Cadence: Always recommend publication schedule with reasoning
Series Type Auto-Detection: Select best series type from topic signals
Hugo Frontmatter: Include frontmatter template for each part
Standalone Value Check: Verify each part passes standalone test before output

完整规划展示：显示包含所有细节的完整规划，不得简化总结
字数预估：每个部分需包含字数范围（通常为800-1500字）
发布节奏建议：始终提供发布时间表及理由说明
系列类型自动识别：根据主题信号选择最合适的系列类型
Hugo Frontmatter：为每个部分提供Frontmatter模板
独立价值校验：输出前需验证每个部分是否通过独立阅读测试

Optional Behaviors (OFF unless enabled)

可选规则（启用后生效）

Minimal Mode: Just part titles and scope, no detailed breakdown
Landing Page: Generate series index page plan (enable with "with landing page")
Parallel Planning: Plan multiple series at once for content calendar

极简模式：仅展示各部分标题和范围，不提供详细分解
着陆页规划：生成系列内容索引页规划（需添加「with landing page」指令启用）
并行规划：同时规划多个系列内容，用于内容日历安排

What This Skill CAN Do

本Skill可实现的功能

Plan 3-7 part blog post series with logical progression
Select appropriate series type (Progressive Depth, Chronological Build, Problem Exploration)
Ensure each part has standalone value while enhancing series context
Design cross-linking structure with navigation patterns
Recommend publishing cadence based on content complexity
Generate Hugo frontmatter templates for series posts

规划包含3-7部分、逻辑递进的博客系列内容
选择合适的系列类型（Progressive Depth、Chronological Build、Problem Exploration）
确保每个部分具备独立阅读价值的同时，增强系列内容的上下文关联性
设计带有导航模式的交叉链接结构
根据内容复杂度建议发布节奏
为系列文章生成Hugo Frontmatter模板

What This Skill CANNOT Do

本Skill无法实现的功能

Write actual post content (use blog-post-writer for writing)
Plan series fewer than 3 parts (use single post or post-outliner instead)
Plan series more than 7 parts (break into multiple series or narrow scope)
Skip standalone value check (each part must be complete on its own)
Create vague, padded series (no filler parts to hit a number)

撰写实际文章内容（需使用blog-post-writer Skill）
规划少于3部分的系列内容（建议使用单篇文章或大纲工具）
规划超过7部分的系列内容（建议拆分为多个系列或缩小主题范围）
跳过独立价值校验（每个部分必须具备完整性）
创建内容空洞、凑数的系列内容（不得为了达到数量而添加无意义部分）

Instructions

使用说明

Usage

调用方式

/series [topic or idea]
/series --type=progressive [topic]      # Force series type
/series --parts=5 [topic]               # Target part count
/series --with-landing [topic]          # Include landing page plan
/series --minimal [topic]               # Titles and scope only

/series [主题或想法]
/series --type=progressive [主题]      # 指定系列类型
/series --parts=5 [主题]               # 指定部分数量
/series --with-landing [主题]          # 包含着陆页规划
/series --minimal [主题]               # 仅显示标题和范围

Phase 1: ASSESS

阶段1：评估

Goal: Determine whether the topic is viable as a series and identify natural divisions.

Step 1: Analyze topic

markdown

undefined

目标：确定主题是否适合做成系列内容，并识别自然的内容划分方式。

步骤1：主题分析

markdown

undefined

Series Assessment

系列内容评估

Topic: [user-provided topic] Scope: [narrow / medium / broad] Natural divisions: [how this topic breaks apart] Audience progression: [beginner to expert? single level?]


**Step 2: Check viability**

- [ ] Topic has natural divisions (3+ distinct subtopics)
- [ ] Each division can stand alone
- [ ] Logical progression exists between parts
- [ ] Not artificially padded (each part earns its place)

**Step 3: Detect series type**

Match topic signals to type. See `references/series-types.md` for full templates.

| Signal | Type |
|--------|------|
| "learn", "master", "deep dive" | Progressive Depth |
| "build", "create", "project" | Chronological Build |
| "why we chose", "migration", "debugging" | Problem Exploration |

**Gate**: Topic passes viability check with 3+ natural divisions identified. If topic fails viability, recommend single post or scope adjustment. Proceed only when gate passes.

主题：[用户提供的主题] 范围：[狭窄 / 适中 / 宽泛] 自然划分：[主题可拆分的维度] 受众进阶路径：[从入门到专家？单一受众层级？]


**步骤2：可行性检查**

- [ ] 主题可自然划分为3个及以上子主题
- [ ] 每个子主题具备独立阅读价值
- [ ] 各部分之间存在合理的递进逻辑
- [ ] 无凑数内容，每个部分都有存在的必要性

**步骤3：系列类型识别**

根据主题信号匹配对应的系列类型。完整模板可参考`references/series-types.md`。

| 信号 | 类型 |
|--------|------|
| "learn", "master", "deep dive" | Progressive Depth |
| "build", "create", "project" | Chronological Build |
| "why we chose", "migration", "debugging" | Problem Exploration |

**准入条件**：主题需通过可行性检查，且可划分为3个及以上子主题。若未通过，建议用户撰写单篇文章或扩大主题范围。仅当满足条件时，方可进入下一阶段。

Phase 2: DECIDE

阶段2：决策

Goal: Select series type, part count, and structure.

Step 1: Select type and justify

markdown

undefined

目标：选择系列类型、确定部分数量和内容结构。

步骤1：选择类型并说明理由

markdown

undefined

Series Decision

系列内容决策

Type: [Progressive Depth / Chronological Build / Problem Exploration] Justification: [why this type fits] Part Count: [3-7] Total Estimated Words: [X,XXX - X,XXX]


**Step 2: Draft part breakdown**

For each part, define:
- Title and scope (1 sentence)
- Standalone value (what reader gets from this part alone)
- Forward/backward links to adjacent parts

**Step 3: Validate standalone value**

For EACH part, verify:
- Reader learns something complete (not half a concept)
- Working code/config/output is possible from this part alone
- No critical information deferred to other parts
- Someone landing on just this part gets something useful

Red flags that fail standalone test:
- "To understand this, read Part 1 first" as mandatory
- Part ends mid-implementation
- Core concepts explained only in earlier parts
- "Part 2 will explain why this works"

**Step 4: Select publishing cadence**

See `references/cadence-guidelines.md` for detailed criteria. Default to weekly unless topic complexity or content depth suggests otherwise.

**Gate**: All parts pass standalone value check. Part count is 3-7. Type selection justified. Proceed only when gate passes.

类型：[Progressive Depth / Chronological Build / Problem Exploration] 理由：[选择该类型的原因] 部分数量：[3-7] 预估总字数：[X,XXX - X,XXX]


**步骤2：草拟内容分解**

为每个部分定义：
- 标题和范围（1句话）
- 独立阅读价值（读者可从该部分获得的内容）
- 与前后部分的交叉链接

**步骤3：独立价值校验**

对**每个部分**进行验证：
- 读者可从该部分学到完整的知识（而非半吊子概念）
- 仅通过该部分即可实现可运行的代码/配置/输出
- 核心概念无需依赖其他部分解释
- 仅访问该部分的读者也能获得有价值的内容

未通过独立价值校验的警示信号：
- 强制要求「要理解本部分，请先阅读第1部分」
- 内容在实现过程中中断
- 核心概念仅在前面的部分中解释
- 出现「第2部分将解释其原理」的表述

**步骤4：确定发布节奏**

详细标准可参考`references/cadence-guidelines.md`。默认采用每周发布一次的节奏，除非主题复杂度或内容深度需要调整。

**准入条件**：所有部分均通过独立价值校验，部分数量在3-7之间，类型选择理由充分。仅当满足条件时，方可进入下一阶段。

Phase 3: GENERATE

阶段3：生成

Goal: Produce the complete series plan with all metadata.

Step 1: Build series plan

Output the complete plan including:

Series header with type and metadata
Detailed breakdown per part (scope, standalone value, links)
Cross-linking structure (see
```
references/cross-linking.md
```
)
Publication schedule with dates
Hugo frontmatter template per part

Step 2: Final validation

Every part has standalone value described
Word counts are realistic (800-1500 per part)
Cross-linking is complete (prev/next for all parts)
No cliff-hangers that frustrate readers
No filler parts
Part count within 3-7 bounds

Step 3: Output plan

Use the series plan format from

references/output-format.md

Gate: All validation checks pass. Plan is complete and ready for delivery.

目标：生成包含所有元数据的完整系列内容规划。

步骤1：构建系列规划

输出完整规划，包括：

包含类型和元数据的系列标题
各部分详细分解（范围、独立价值、链接）
交叉链接结构（参考
```
references/cross-linking.md
```
）
带日期的发布时间表
各部分的Hugo Frontmatter模板

步骤2：最终校验

每个部分都明确说明了独立阅读价值
字数预估合理（每部分800-1500字）
交叉链接完整（所有部分均包含上一篇/下一篇链接）
无吊读者胃口的内容
无凑数内容
部分数量在3-7之间

步骤3：输出规划

采用

references/output-format.md

中的系列规划格式输出。

准入条件：所有校验项均通过。规划完整，可交付给用户。

Series Types (Summary)

系列类型（摘要）

Three primary types. Full templates and examples in

references/series-types.md

主要包含三种类型。完整模板和示例可参考

references/series-types.md

。

Progressive Depth

Shallow-to-deep mastery. Each level is complete; beginners stop at Part 1, advanced readers skip ahead.

由浅入深的精通式学习。每个阶段内容完整；初学者可停留在第1部分，进阶读者可跳过前面的内容直接阅读后续部分。

Chronological Build

Step-by-step creation. Each part produces working output; reader can stop at any milestone.

分步式创建教程。每个部分都能产出可运行的成果；读者可在任意里程碑处停止学习。

Problem Exploration

Journey from problem to solution. Even failed approaches are instructive; each part teaches something.

从问题到解决方案的探索过程。即使是失败的尝试也具备指导意义；每个部分都能传授知识。

Examples

示例

Example 1: Standard Technical Series

示例1：标准技术系列

User says: "/series Go error handling" Actions:

Assess: Topic has clear depth levels (basics, wrapping, custom types, patterns) (ASSESS)
Decide: Progressive Depth, 4 parts, weekly cadence (DECIDE)
Generate: Full plan with standalone value per part (GENERATE) Result: 4-part series where each part teaches complete error handling at its level

用户指令：

/series Go error handling

操作流程：

评估：主题具备清晰的深度层级（基础、包装、自定义类型、模式）（评估阶段）
决策：选择Progressive Depth类型，4个部分，每周发布一次（决策阶段）
生成：包含各部分独立价值的完整规划（生成阶段）结果：4部分系列内容，每个部分都能教授对应层级的完整错误处理知识

Example 2: Project Tutorial Series

示例2：项目教程系列

User says: "/series building a CLI tool in Rust" Actions:

Assess: Topic has build milestones (scaffold, commands, config, distribution) (ASSESS)
Decide: Chronological Build, 4 parts, weekly cadence (DECIDE)
Generate: Full plan with working output per milestone (GENERATE) Result: 4-part series where each part produces a functional artifact

用户指令：

/series building a CLI tool in Rust

操作流程：

评估：主题具备明确的构建里程碑（搭建框架、命令实现、配置、分发）（评估阶段）
决策：选择Chronological Build类型，4个部分，每周发布一次（决策阶段）
生成：包含每个里程碑可运行成果的完整规划（生成阶段）结果：4部分系列内容，每个部分都能产出可用的功能产物

Example 3: Problem Exploration Series

示例3：问题探索系列

User says: "/series why we migrated from MongoDB to PostgreSQL" Actions:

Assess: Topic has journey arc (problem, attempt, failure, solution) (ASSESS)
Decide: Problem Exploration, 4 parts, bi-weekly cadence (DECIDE)
Generate: Full plan where each part teaches standalone lessons (GENERATE) Result: 4-part series where even failed approaches deliver instructive value

用户指令：

/series why we migrated from MongoDB to PostgreSQL

操作流程：

评估：主题具备完整的探索路径（问题、尝试、失败、解决方案）（评估阶段）
决策：选择Problem Exploration类型，4个部分，每两周发布一次（决策阶段）
生成：包含各阶段独立经验的完整规划（生成阶段）结果：4部分系列内容，即使是失败的尝试也能为读者提供有价值的经验

Example 4: Topic Too Narrow

示例4：主题范围过窄

User says: "/series Go defer statement" Actions:

Assess: Topic has 1-2 natural divisions, not 3+ (ASSESS)
Gate fails: Recommend single post or expanding scope to "Go resource management" Result: Redirect to post-outliner or expanded topic suggestion

用户指令：

/series Go defer statement

操作流程：

评估：主题仅能划分为1-2个部分，不足3个（评估阶段）
未通过准入条件：建议使用单篇文章工具，或扩大主题范围至「Go资源管理」结果：引导用户使用大纲工具，或建议扩展主题

Error Handling

错误处理

Error: "Topic Too Narrow for Series"

错误：「主题范围过窄，不适合做系列内容」

Cause: Topic doesn't naturally divide into 3+ parts Solution:

Suggest post-outliner for single comprehensive post
Propose scope expansion: "Consider covering [related aspect]"
List what would need to be true for series to work

原因：主题无法自然划分为3个及以上部分解决方案：

建议使用post-outliner工具撰写单篇综合性文章
提出范围扩展建议：「考虑加入[相关内容]」
说明主题具备哪些条件后可做成系列内容

Error: "Topic Too Broad for Series"

错误：「主题范围过宽，不适合做系列内容」

Cause: Would require 8+ parts or scope is unmanageable Solution:

Identify natural breakpoints for multiple series
Recommend first series to tackle
Suggest narrowing to specific aspect

原因：需要8个及以上部分才能覆盖，或范围难以掌控解决方案：

识别可拆分为多个系列的自然断点
建议先从第一个系列开始
建议缩小主题至特定方向

Error: "No Logical Progression"

错误：「无合理递进逻辑」

Cause: Parts don't build on each other meaningfully; just loosely related topics Solution:

Determine if these are better as standalone posts
Find the connecting thread that creates progression
Consider if forcing series structure adds value vs. individual posts

原因：各部分之间无有意义的递进关系，仅为松散关联的主题解决方案：

判断是否更适合作为单篇独立文章
寻找可构建递进逻辑的关联线索
对比强制做成系列内容与作为独立文章的价值差异

Error: "Standalone Value Missing"

错误：「缺乏独立阅读价值」

Cause: One or more parts don't stand alone Solution:

Identify which parts fail the standalone test
Suggest content to add for completeness
Or merge dependent parts into one

原因：一个或多个部分不具备独立性解决方案：

识别未通过独立价值校验的部分
建议添加内容以确保完整性
或合并依赖的部分

Anti-Patterns

反模式

Anti-Pattern 1: The Cliff-Hanger Series

反模式1：吊胃口式系列内容

What it looks like: "...but the real solution is in Part 2!" -- content gates behind future parts Why wrong: Frustrates readers, SEO penalty for thin content, Part 2 visitors get nothing Do instead: Each part delivers complete value. Reference other parts for context, not content.

表现形式：出现「真正的解决方案在第2部分！」的表述，将核心内容锁定在后续部分 问题所在：引发读者不满，内容单薄会导致SEO惩罚，第2部分的访客无法获得有价值的内容 正确做法：每个部分都提供完整的价值。可引用其他部分作为上下文，但不得将核心内容放在其他部分

Anti-Pattern 2: The Padded Series

反模式2：凑数式系列内容

What it looks like: "Part 1: Introduction", "Part 2: Getting Started", "Part 3: Basics" -- three parts that should be one Why wrong: Disrespects reader time, each part lacks substance Do instead: Combine until each part has substantial, unique value. 3 meaty parts beats 6 thin ones.

表现形式：「第1部分：简介」、「第2部分：入门」、「第3部分：基础」——这三部分本应合并为一个部分 问题所在：浪费读者时间，每个部分内容都不充实 正确做法：合并内容，直到每个部分都具备充实、独特的价值。3个有料的部分远胜于6个空洞的部分

Anti-Pattern 3: The Prerequisite Spiral

反模式3：前置依赖螺旋

What it looks like: "Before we start, read these 5 posts..." -- hard dependency chains Why wrong: Creates barrier to entry, search traffic to later parts bounces immediately Do instead: Brief context inline. Link to prerequisites as optional. Make each part accessible.

表现形式：「开始之前，请先阅读这5篇文章...」——存在硬性依赖链 问题所在：提高入门门槛，后续部分的搜索流量会立即流失 正确做法：在内容中简要提供上下文。将前置内容作为可选链接。确保每个部分都易于访问

Anti-Pattern 4: Inconsistent Scope

反模式4：范围不一致

What it looks like: Part 1 is 500 words, Part 2 is 3000 words, Part 3 is 400 words Why wrong: Reader expectations whiplash, suggests poor planning Do instead: Keep parts roughly similar in depth and length. 800-1200 words each is the target.

表现形式：第1部分500字，第2部分3000字，第3部分400字 问题所在：打破读者预期，反映出规划不足 正确做法：保持各部分的深度和长度大致一致。目标为每部分800-1200字

Anti-Pattern 5: Scope Creep Mid-Series

反模式5：系列内容中途扩围

What it looks like: Starting with 3 planned parts, ending with 7 because "one more thing" Why wrong: Breaks publishing cadence, dilutes series focus, reader fatigue Do instead: Plan the full series before publishing Part 1. If scope grows, split into a second series.

表现形式：最初规划3个部分，最终因为「再加一个内容」变成7个部分 问题所在：打乱发布节奏，分散系列内容的焦点，导致读者疲劳 正确做法：在发布第1部分前完成完整规划。若内容范围扩大，拆分为第二个系列

References

参考资料

This skill uses these shared patterns:

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

本Skill采用以下通用模式：

Anti-Rationalization - 防止捷径式合理化
Verification Checklist - 完成前校验

Domain-Specific Anti-Rationalization

领域特定的反合理化规则

Rationalization	Why It's Wrong	Required Action
"This needs 8 parts to be complete"	Scope creep; split into two series	Enforce 3-7 part limit
"Part 1 is just setup, real value starts Part 2"	Part 1 fails standalone test	Ensure Part 1 delivers value
"Readers will read them in order"	Search traffic lands anywhere	Each part must stand alone
"One more part won't hurt"	Padding dilutes series quality	Every part must earn its place

合理化借口	问题所在	要求操作
「需要8个部分才能覆盖完整内容」	范围失控；应拆分为两个系列	严格执行3-7部分的限制
「第1部分仅为准备内容，核心价值从第2部分开始」	第1部分未通过独立价值校验	确保第1部分具备独立价值
「读者会按顺序阅读所有内容」	搜索流量可能进入任意部分	每个部分必须具备独立性
「再加一个部分没关系」	凑数会降低系列内容质量	每个部分都必须具备存在的必要性

Reference Files

参考文件

```
${CLAUDE_SKILL_DIR}/references/series-types.md
```
: Complete type templates with examples and selection criteria

${CLAUDE_SKILL_DIR}/references/cross-linking.md

: Navigation patterns and Hugo implementation

${CLAUDE_SKILL_DIR}/references/cadence-guidelines.md

: Publishing frequency recommendations and schedules

${CLAUDE_SKILL_DIR}/references/output-format.md

: Series plan output format template

```
${CLAUDE_SKILL_DIR}/references/series-types.md
```
：包含示例和选择标准的完整类型模板

${CLAUDE_SKILL_DIR}/references/cross-linking.md

：导航模式和Hugo实现方案

${CLAUDE_SKILL_DIR}/references/cadence-guidelines.md

：发布频率建议和时间表

${CLAUDE_SKILL_DIR}/references/output-format.md

：系列内容规划的输出格式模板