Series Planner Skill

Operator Context

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

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

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

What This Skill CAN Do

• 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

What This Skill CANNOT Do

• 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)

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

Phase 1: ASSESS

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

• 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)

references/series-types.md

Phase 2: DECIDE

## 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]

• Title and scope (1 sentence)
• Standalone value (what reader gets from this part alone)
• Forward/backward links to adjacent parts

• 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

• "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"

references/cadence-guidelines.md

Phase 3: GENERATE

1. Series header with type and metadata
2. Detailed breakdown per part (scope, standalone value, links)
3. Cross-linking structure (see

   references/cross-linking.md

   )
4. Publication schedule with dates
5. Hugo frontmatter template per part

• 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

references/output-format.md

Series Types (Summary)

references/series-types.md

Progressive Depth

Chronological Build

Problem Exploration

Examples

Example 1: Standard Technical Series

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

Example 2: Project Tutorial Series

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

Example 3: Problem Exploration Series

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

Example 4: Topic Too Narrow

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

Error Handling

Error: "Topic Too Narrow for Series"

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

Error: "Topic Too Broad for Series"

1. Identify natural breakpoints for multiple series
2. Recommend first series to tackle
3. Suggest narrowing to specific aspect

Error: "No Logical Progression"

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

Error: "Standalone Value Missing"

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

Anti-Patterns

Anti-Pattern 1: The Cliff-Hanger Series

Anti-Pattern 2: The Padded Series

Anti-Pattern 3: The Prerequisite Spiral

Anti-Pattern 4: Inconsistent Scope

Anti-Pattern 5: Scope Creep Mid-Series

References

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

Domain-Specific Anti-Rationalization

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