book-chapter-generator

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Book Chapter Generator

教材章节生成器

Overview

概述

This skill creates a comprehensive chapter structure for intelligent textbooks by analyzing the course description, learning graph, and concept taxonomy. It designs an optimal chapter outline that ensures all concepts are covered exactly once, respects dependency relationships, and distributes content appropriately across chapters. This task is run serially after the learning graph generation.

此Skill通过分析课程描述、Learning Graph和概念分类体系，为智能教材创建全面的章节结构。它会设计最优的章节大纲，确保所有概念仅被覆盖一次、遵循依赖关系，并在各章节间合理分配内容。此任务需在Learning Graph生成后按顺序执行。

When to Use This Skill

何时使用此Skill

Use this skill when:

The course description is finalized and the a learning graph has been generated (learning-graph.json exists)
Chapter content structure needs to be designed before writing begins

Prerequisites:

```
/docs/course-description.md
```
must exist

/docs/learning-graph/learning-graph.json

must exist with ~200 concepts

mkdocs.yml file must be in place for the chapter links to be generated to the nav section

Do NOT use this skill if:

The learning graph hasn't been generated yet (use
```
learning-graph-generator
```
first)
Chapter content already exists and just needs updating

使用此Skill的场景：

课程描述已确定且Learning Graph已生成（存在learning-graph.json文件）
需要在开始撰写前设计章节内容结构

前置条件：

```
/docs/course-description.md
```
必须存在

/docs/learning-graph/learning-graph.json

必须存在，且包含约200个概念

必须存在mkdocs.yml文件，以便将章节链接生成到导航栏部分

请勿在以下场景使用此Skill：

Learning Graph尚未生成（请先使用
```
learning-graph-generator
```
）
章节内容已存在，仅需更新内容

Chapter Generation Workflow

章节生成流程

This skill follows a four-step sequential workflow with user approval before generating files.

此Skill遵循四步顺序流程，在生成文件前需获得用户批准。

Step 1: Analyze Input Resources

步骤1：分析输入资源

Before designing chapters, analyze the following resources:

在设计章节前，需分析以下资源：

1.1 Read Course Description

1.1 读取课程描述

Read

/docs/course-description.md

to understand:

Course title and target audience
Learning objectives and outcomes
Prerequisite knowledge
Overall scope and goals

读取

/docs/course-description.md

以了解：

课程名称与目标受众
学习目标与成果
前置知识要求
整体范围与目标

1.2 Read Learning Graph

1.2 读取Learning Graph

Read

/docs/learning-graph/learning-graph.json

to extract:

Complete list of concepts (typically 200 concepts)
Concept dependencies (which concepts require others as prerequisites)
Concept groupings by taxonomy category
Metadata about the course

Validate that:

The graph structure is a valid DAG (no circular dependencies)
All concepts have unique IDs
Dependency references are valid

读取

/docs/learning-graph/learning-graph.json

以提取：

完整的概念列表（通常约200个概念）
概念依赖关系（哪些概念需要其他概念作为前置）
按分类体系分组的概念
课程相关元数据

验证以下内容：

图谱结构为有效的DAG（无循环依赖）
所有概念都有唯一ID
依赖引用有效

1.3 Read Concept Taxonomy

1.3 读取概念分类体系

Read

/docs/learning-graph/concept-taxonomy.md

(if it exists) to understand:

Taxonomy categories and their meanings
How concepts are grouped conceptually
Any suggested ordering or progression

读取

/docs/learning-graph/concept-taxonomy.md

（如果存在）以了解：

分类体系的类别及其含义
概念的分组方式
任何建议的排序或递进关系

1.4 Identify Design Constraints

1.4 识别设计约束

Analyze the data to identify:

Foundational concepts: Concepts with no dependencies (should appear early)
Advanced concepts: Concepts with many dependencies (should appear later)
Dependency chains: Long sequences of prerequisite relationships
Concept clusters: Groups of related concepts that should stay together
Orphaned concepts: Concepts that nothing depends on (can be placed flexibly)

分析数据以识别：

基础概念：无依赖的概念（应出现在早期章节）
进阶概念：有多个依赖的概念（应出现在后期章节）
依赖链：长序列的前置依赖关系
概念集群：应放在一起的相关概念组
孤立概念：无其他概念依赖的概念（可灵活放置）

Step 2: Design Chapter Structure

步骤2：设计章节结构

Design an optimal chapter structure following these principles:

遵循以下原则设计最优章节结构：

2.1 Determine Chapter Count

2.1 确定章节数量

Choose the appropriate number of chapters (6-20) based on:

Total concepts: ~200 concepts typically need 10-15 chapters
Dependency complexity: More complex dependencies may need more chapters
Taxonomy distribution: Natural groupings suggest chapter boundaries
Target audience: Introductory courses may need smaller chapters

Guidelines:

Minimum 6 chapters (for very concise courses)
Optimal range: 10-15 chapters
Maximum 20 chapters (for comprehensive graduate-level content)
Aim for 10-20 concepts per chapter on average

根据以下因素选择合适的章节数量（6-20章）：

总概念数：约200个概念通常需要10-15章
依赖复杂度：更复杂的依赖可能需要更多章节
分类体系分布：自然分组可作为章节边界的参考
目标受众：入门课程可能需要更短的章节

指导原则：

最少6章（针对非常精简的课程）
最优范围：10-15章
最多20章（针对全面的研究生级内容）
目标：每章平均包含10-20个概念

2.2 Assign Concepts to Chapters

2.2 为章节分配概念

Design chapter assignments that satisfy these requirements:

CRITICAL REQUIREMENTS:

Every concept appears in exactly one chapter (no duplicates, no omissions)
No concept appears before its dependencies (respect the DAG structure)
Balanced distribution (avoid chapters with too many or too few concepts)

OPTIMIZATION GOALS:

Keep related concepts (same taxonomy category) together when possible
Create logical progression from foundational to advanced topics
Balance chapter sizes (avoid chapters with <8 or >25 concepts)
Group concepts that form natural learning units
Consider cognitive load (mix difficulty levels within chapters)

设计章节分配方案，满足以下要求：

核心要求：

每个概念仅出现在一个章节中（无重复、无遗漏）
概念不能出现在其依赖概念之前（遵循DAG结构）
均衡分布（避免章节概念过多或过少）

优化目标：

尽可能将相关概念（同一分类类别）放在一起
创建从基础到进阶主题的逻辑递进
平衡章节规模（避免章节概念数<8或>25）
分组形成自然学习单元的概念
考虑认知负荷（章节内混合不同难度的概念）

2.3 Create Chapter Titles

2.3 创建章节标题

For each chapter, create a title that:

Uses Title Case formatting
Is no longer than 200 characters (to fit on one line)
Clearly describes the chapter's main topic
Uses standard educational terminology
Avoids acronyms unless widely known

Examples:

"Introduction to Graph Theory Fundamentals"
"Binary Trees and Tree Traversal Algorithms"
"Graph Coloring Problems and Applications"
"Advanced Topics in Network Flow Optimization"

为每个章节创建标题，需满足：

使用**标题大小写（Title Case）**格式
长度不超过200字符（以适应单行显示）
清晰描述章节的核心主题
使用标准教育术语
除非是广为人知的缩写，否则避免使用

示例：

"Introduction to Graph Theory Fundamentals"
"Binary Trees and Tree Traversal Algorithms"
"Graph Coloring Problems and Applications"
"Advanced Topics in Network Flow Optimization"

2.4 Write Chapter Summaries

2.4 撰写章节摘要

For each chapter, write a single sentence (20-40 words) that:

Describes what the chapter covers
Mentions key concepts or themes
Indicates the chapter's role in the learning progression

为每个章节撰写一句话摘要（20-40词），需包含：

章节覆盖的内容
关键概念或主题
章节在学习递进中的作用

Step 3: Present Design to User for Approval

步骤3：向用户展示设计方案并获取批准

Before creating any files, present the chapter design to the user in this format:

undefined

在生成任何文件前，按以下格式向用户展示章节设计方案：

undefined

Proposed Chapter Structure

拟议章节结构

I've designed a [number]-chapter structure for your textbook covering [total] concepts.

我已为你的教材设计了包含[X]章的结构，覆盖[Y]个概念。

Chapters:

章节列表：

[Chapter Title] ([X] concepts) [One sentence summary]
[Chapter Title] ([X] concepts) [One sentence summary]

[... continue for all chapters ...]

[章节标题]（[X]个概念） [一句话摘要]
[章节标题]（[X]个概念） [一句话摘要]

[... 所有章节依次列出 ...]

Design Challenges & Solutions:

设计挑战与解决方案：

[Discuss any challenges encountered and how the design addresses them, such as:]

Challenge: Concept X has 15 dependencies, making placement difficult Solution: Placed in Chapter 8 after all prerequisites are covered in Chapters 1-7
Challenge: Taxonomy category Y contains 45 concepts Solution: Split across Chapters 3, 6, and 9 to maintain logical flow

[... other challenges ...]

[讨论遇到的挑战及设计方案的解决方式，例如：]

挑战：概念X有15个依赖，难以放置 解决方案：放在第8章，所有前置概念已在第1-7章覆盖
挑战：分类类别Y包含45个概念 解决方案：拆分到第3、6、9章，以保持逻辑流畅

[... 其他挑战 ...]

Statistics:

统计数据：

Total chapters: [X]
Average concepts per chapter: [X.X]
Range: [min]-[max] concepts per chapter
All [total] concepts covered: ✓
All dependencies respected: ✓

undefined

总章节数：[X]
每章平均概念数：[X.X]
范围：[最少]-[最多]个概念/章
所有[Y]个概念已覆盖：✓
所有依赖关系已遵循：✓

undefined

3.1 Get User Approval

3.1 获取用户批准

After presenting the design, ask:

Do you approve this chapter structure? (y/n)

If no, please specify what changes you'd like:
- Different number of chapters?
- Specific concepts moved to different chapters?
- Chapter titles revised?
- Different grouping strategy?

展示设计方案后，询问：

你是否批准此章节结构？(y/n)

如果不批准，请说明你希望进行的修改：
- 调整章节数量？
- 将特定概念移至其他章节？
- 修改章节标题？
- 更改分组策略？

3.2 Handle User Feedback

3.2 处理用户反馈

If the user says "no" or requests changes:

Listen to their specific feedback
Revise the chapter design accordingly
Re-present the updated structure
Continue iterating until approval is received

If the user says "yes":

Proceed to Step 4 to generate the chapter files

如果用户回答“否”或要求修改：

倾听用户的具体反馈
相应修改章节设计
重新展示更新后的结构
持续迭代直至获得批准

如果用户回答“是”：

进入步骤4生成章节文件

Step 4: Generate Chapter Directory Structure and Files

步骤4：生成章节目录结构与文件

Once the user approves the design, create the chapter structure:

获得用户批准后，创建章节结构：

4.1 Create URL Path Names

4.1 创建URL路径名称

For each chapter, create a URL-friendly path name:

Rules:

Use only lowercase letters and dashes (no other characters)
Remove all special characters, punctuation, and numbers (except in numbered prefixes)
Replace spaces with dashes
Use abbreviations if needed to keep names short (<50 characters)
Make names descriptive but concise

Examples:

"Introduction to Graph Theory Fundamentals" → "intro-to-graph-theory"
"Binary Trees and Tree Traversal Algorithms" → "binary-trees-traversal"
"Advanced Topics in Network Flow Optimization" → "advanced-network-flow"

为每个章节创建适合URL的路径名称：

规则：

仅使用小写字母和连字符（无其他字符）
移除所有特殊字符、标点和数字（编号前缀中的数字除外）
用连字符替换空格
必要时使用缩写以保持名称简短（<50字符）
名称需兼具描述性与简洁性

示例：

"Introduction to Graph Theory Fundamentals" → "intro-to-graph-theory"
"Binary Trees and Tree Traversal Algorithms" → "binary-trees-traversal"
"Advanced Topics in Network Flow Optimization" → "advanced-network-flow"

4.2 Create Directory Structure

4.2 创建目录结构

Create the following directory structure:

/docs/chapters/
├── index.md
├── 01-[url-path-name]/
│   └── index.md
├── 02-[url-path-name]/
│   └── index.md
├── 03-[url-path-name]/
│   └── index.md
[... continue for all chapters ...]

Implementation:

bash

mkdir -p /docs/chapters
mkdir -p /docs/chapters/01-[url-path-name]
mkdir -p /docs/chapters/02-[url-path-name]

创建以下目录结构：

/docs/chapters/
├── index.md
├── 01-[url-path-name]/
│   └── index.md
├── 02-[url-path-name]/
│   └── index.md
├── 03-[url-path-name]/
│   └── index.md
[... 所有章节依次创建 ...]

实现命令：

bash

mkdir -p /docs/chapters
mkdir -p /docs/chapters/01-[url-path-name]
mkdir -p /docs/chapters/02-[url-path-name]

... continue for all chapters

... 所有章节依次执行 ...

undefined

undefined

4.3 Create Main Chapters Index

4.3 创建主章节索引

Create

/docs/chapters/index.md

with:

markdown

undefined

创建

/docs/chapters/index.md

，内容如下：

markdown

undefined

Chapters

章节列表

This textbook is organized into [X] chapters covering [Y] concepts.

本教材分为[X]章，覆盖[Y]个概念。

Chapter Overview

章节概述

Chapter 1 Title - [One sentence summary]
Chapter 2 Title - [One sentence summary] [... continue for all chapters ...]

第1章标题 - [一句话摘要]
第2章标题 - [一句话摘要] [... 所有章节依次列出 ...]

How to Use This Textbook

教材使用指南

[Add 2-3 sentences about how readers should progress through the chapters, noting that dependencies are respected and concepts build on each other]

Note: Each chapter includes a list of concepts covered. Make sure to complete prerequisites before moving to advanced chapters.

undefined

[添加2-3句话，说明读者应如何学习各章节，注意依赖关系已被遵循，概念是循序渐进的]

注意： 每章都包含覆盖的概念列表。请确保完成前置章节后再学习进阶章节。

undefined

4.4 Create Individual Chapter Index Files

4.4 创建单个章节索引文件

For each chapter, create

/docs/chapters/[XX]-[url-path-name]/index.md

with this structure:

markdown

undefined

为每个章节创建

/docs/chapters/[XX]-[url-path-name]/index.md

，结构如下：

markdown

undefined

[Chapter Title]

[章节标题]

Summary

摘要

[Write a 2-4 sentence summary of what the chapter covers, expanding on the one-sentence version from the design. Include:]

Main topics and themes
How this chapter fits in the learning progression
What students will be able to do after completing this chapter

[撰写2-4句话的摘要，扩展设计阶段的一句话版本。需包含：]

主要主题与内容
本章在学习递进中的位置
学生完成本章后应具备的能力

Concepts Covered

覆盖的概念

This chapter covers the following [X] concepts from the learning graph:

[Concept Name 1]
[Concept Name 2]
[Concept Name 3] [... continue for all concepts in this chapter ...]

本章覆盖Learning Graph中的以下[X]个概念：

[概念名称1]
[概念名称2]
[概念名称3] [... 本章所有概念依次列出 ...]

Prerequisites

前置要求

[If this is not the first chapter, list which previous chapters should be completed first:]

This chapter builds on concepts from:

Chapter X: Chapter Title
Chapter Y: Chapter Title

[If this is the first chapter or has no prerequisites within the book:]

This chapter assumes only the prerequisites listed in the course description.

TODO: Generate Chapter Content


**Important formatting notes:**
- Always include a blank line before markdown lists (MkDocs requirement)
- Use relative paths for internal links
- Concept names should match exactly as they appear in learning-graph.json
- Maintain consistent heading hierarchy (# → ## → ###)

[如果不是第一章，列出需要先完成的前置章节：]

本章基于以下章节的概念：

第X章：章节标题
第Y章：章节标题

[如果是第一章或无教材内前置要求：]

本章仅要求具备课程描述中列出的前置知识。

TODO: Generate Chapter Content


**重要格式说明：**
- 列表前必须空一行（MkDocs要求）
- 内部链接使用相对路径
- 概念名称需与learning-graph.json中的完全一致
- 保持一致的标题层级（# → ## → ###）

4.5 Update MkDocs Navigation

4.5 更新MkDocs导航

After creating all chapter files, update

mkdocs.yml

to include the chapters in navigation. Note that the navigation bar is not very wide, so we don't spell out the name "Chapter X" in the nav bar. We only need to put the number since the "Chapters:" label is above the list of chapters.

yaml

nav:
  - Home: index.md
  - Course Description: course-description.md
  - Chapters:
    - List of Chapters: chapters/index.md
    - 1. [Chapter 1 Title]: chapters/01-[url-path-name]/index.md
    - 2. [Chapter 2 Title]: chapters/02-[url-path-name]/index.md
    - 3. [Chapter 3 Title]: chapters/03-[url-path-name]/index.md
    # ... continue for all chapters
  - Learning Graph:
    - Introduction: learning-graph/index.md
    # ... existing learning graph pages

Note: Only update the

Chapters:

section. Do not remove or modify other navigation entries.

创建所有章节文件后，更新

mkdocs.yml

以将章节添加到导航栏。注意导航栏宽度有限，因此我们不在导航栏中拼写“第X章”，仅需添加编号即可，因为“章节：”标签已在章节列表上方。

yaml

nav:
  - Home: index.md
  - Course Description: course-description.md
  - Chapters:
    - List of Chapters: chapters/index.md
    - 1. [Chapter 1 Title]: chapters/01-[url-path-name]/index.md
    - 2. [Chapter 2 Title]: chapters/02-[url-path-name]/index.md
    - 3. [Chapter 3 Title]: chapters/03-[url-path-name]/index.md
    # ... 所有章节依次添加 ...
  - Learning Graph:
    - Introduction: learning-graph/index.md
    # ... 已有的Learning Graph页面 ...

注意： 仅更新

Chapters:

部分。请勿删除或修改其他导航条目。

4.6 Confirm Completion

4.6 确认完成

After all files are created, inform the user:

✅ Chapter structure generated successfully!

Created:
- chapters/index.md (main chapter overview)
- [X] chapter directories with index files
- Updated mkdocs.yml navigation

Next steps:
1. Review the chapter structure: `mkdocs serve`
2. Navigate to the Chapters section to see all chapter outlines
3. Use the chapter content generation skill (when ready) to populate each chapter
4. Each chapter index.md has "TODO: Generate Chapter Content" as a placeholder

Statistics:
- Total chapters: [X]
- Total concepts assigned: [Y]
- All dependencies respected: ✓

所有文件创建完成后，通知用户：

✅ 章节结构生成成功！

已创建：
- chapters/index.md（主章节概述）
- [X]个章节目录及对应的index.md文件
- 更新后的mkdocs.yml导航

下一步操作：
1. 查看章节结构：`mkdocs serve`
2. 导航至章节部分查看所有章节大纲
3. 准备好后使用章节内容生成Skill填充各章节
4. 每个章节的index.md文件中都有“TODO: Generate Chapter Content”占位符

统计数据：
- 总章节数：[X]
- 已分配的概念总数：[Y]
- 所有依赖关系已遵循：✓

Design Principles

设计原则

Dependency Management

依赖关系管理

Critical: The chapter sequence must respect the DAG structure:

If concept B depends on concept A, then A must appear in an earlier (or same) chapter than B
Check all dependency relationships before finalizing chapter assignments
Use topological sorting to verify the order is valid

核心要求：章节顺序必须遵循DAG结构：

如果概念B依赖于概念A，那么A必须出现在B的前一章或同一章
最终确定章节分配前检查所有依赖关系
使用拓扑排序验证顺序有效性

Content Balance

内容均衡

Aim for balanced chapter sizes:

Optimal: 12-18 concepts per chapter
Acceptable: 8-25 concepts per chapter
Avoid: <8 concepts (too thin) or >25 concepts (too dense)

If a chapter is too large, consider splitting it into two chapters. If a chapter is too small, consider merging it with a related chapter.

目标是平衡章节规模：

最优：每章12-18个概念
可接受：每章8-25个概念
避免：每章概念数<8（过于单薄）或>25（过于密集）

如果章节过大，考虑拆分为两个章节。如果章节过小，考虑与相关章节合并。

Pedagogical Flow

教学流程

Structure chapters to support learning:

Early chapters: Foundational concepts, simple ideas, build confidence
Middle chapters: Core content, increasing complexity, practical applications
Late chapters: Advanced topics, integration, synthesis

Within each chapter, order concepts from:

Foundational to advanced (based on dependencies)
Simple to complex (based on cognitive load)
Abstract to concrete (when introducing new ideas)

章节结构需支持学习：

早期章节：基础概念、简单内容，建立学习信心
中期章节：核心内容、复杂度提升、实际应用
后期章节：进阶主题、综合应用、知识整合

在每个章节内，概念顺序应遵循：

从基础到进阶（基于依赖关系）
从简单到复杂（基于认知负荷）
从抽象到具体（介绍新思想时）

Cognitive Load

认知负荷

Consider student cognitive load:

Don't overload early chapters (students are still building context)
Mix difficulty levels within chapters when possible
Group related concepts to reduce cognitive switching
Ensure adequate scaffolding (prerequisite concepts in prior chapters)

考虑学生的认知负荷：

早期章节不要包含过多内容（学生仍在建立认知框架）
尽可能在章节内混合不同难度的概念
分组相关概念以减少认知切换
确保有足够的支架（前置概念已在之前的章节覆盖）

Common Challenges and Solutions

常见挑战与解决方案

Challenge: Taxonomy Category Too Large

挑战：分类类别过大

Problem: A single taxonomy category contains 40+ concepts.

Solutions:

Split the category across multiple chapters
Use different aspects or sub-themes as chapter boundaries
Interleave with other categories to maintain engagement

问题：单个分类类别包含40+个概念。

解决方案：

将类别拆分到多个章节
以不同方面或子主题作为章节边界
与其他类别交错排列以保持学习兴趣

Challenge: Long Dependency Chains

挑战：长依赖链

Problem: Concept Z depends on Y, which depends on X, which depends on W... (5+ levels deep).

Solutions:

Spread the chain across multiple chapters
Place earlier dependencies in multiple chapters if appropriate
Consider creating a dedicated "foundations" chapter for deep dependency roots

问题：概念Z依赖于Y，Y依赖于X，X依赖于W...（5层以上）。

解决方案：

将依赖链分布到多个章节
如果合适，将早期依赖分散到多个章节
考虑为深层依赖的根概念创建专门的“基础”章节

Challenge: Orphaned Concepts

挑战：孤立概念

Problem: Some concepts have no dependents (nothing builds on them).

Solutions:

Place orphaned concepts at the end of related chapters
Group orphaned concepts into "Additional Topics" or "Special Topics" chapters
Consider whether these concepts are truly necessary (but don't remove them without user approval)

问题：某些概念无其他概念依赖。

解决方案：

将孤立概念放在相关章节的末尾
将孤立概念分组为“补充主题”或“特殊主题”章节
考虑这些概念是否真的必要（但未经用户批准请勿删除）

Challenge: Cluster Splitting

挑战：集群拆分

Problem: A natural concept cluster (e.g., 5 tree traversal algorithms) is too large for one chapter but splitting it feels wrong.

Solutions:

Split into "Part 1" and "Part 2" chapters with clear continuation
Use dependency relationships to find a natural split point
Group by complexity (basic vs. advanced) or application domain

问题：一个自然概念集群（如5种树遍历算法）过大，不适合放在一个章节，但拆分又不合理。

解决方案：

拆分为“第一部分”和“第二部分”章节，明确是连续内容
利用依赖关系找到自然拆分点
按复杂度（基础vs进阶）或应用领域分组

Challenge: Uneven Distribution

挑战：分布不均

Problem: The dependency structure forces 30 concepts into Chapter 2 and only 8 concepts into Chapter 7.

Solutions:

Split the large chapter into two chapters
Merge the small chapter with an adjacent chapter
Revisit chapter boundaries to find better balance
Adjust the total number of chapters

问题：依赖结构导致第2章有30个概念，而第7章只有8个概念。

解决方案：

将大章节拆分为两个章节
将小章节与相邻章节合并
重新审视章节边界以找到更好的平衡
调整总章节数

Validation Checklist

验证清单

Example Usage

示例用法

User request: "Create chapters for my Graph Theory textbook"

Skill workflow:

Read course-description.md, learning-graph.json, and concept-taxonomy.md
Analyze 200 concepts and their dependencies
Design 12 chapters with balanced content distribution
Present chapter outline to user:
- Chapter 1: Introduction (15 concepts)
- Chapter 2: Graph Representations (18 concepts)
- ... etc.
Get user approval (y/n)
Create directory structure and all index.md files
Update mkdocs.yml navigation
Confirm completion

用户请求： "为我的图论教材创建章节"

Skill流程：

读取course-description.md、learning-graph.json和concept-taxonomy.md
分析200个概念及其依赖关系
设计12章内容均衡的结构
向用户展示章节大纲：
- 第1章：引言（15个概念）
- 第2章：图的表示（18个概念）
- ... 以此类推
获取用户批准（y/n）
创建目录结构和所有index.md文件
更新mkdocs.yml导航
确认完成

Notes

注意事项

This skill only creates the structure and outlines for chapters
It does NOT generate actual chapter content (that requires a separate skill)
The "TODO: Generate Chapter Content" marker indicates where content should be added later
Always preserve the concept list in each chapter index.md for use by content generation skills

此Skill仅创建章节的结构和大纲
不生成实际章节内容（需要使用单独的Skill）
"TODO: Generate Chapter Content"标记表示后续应添加内容的位置
请始终保留每个章节index.md中的概念列表，供内容生成Skill使用