outline-architect

name: outline-architect description: [Workflow Sub-task] This is a sub-task Skill, usually dispatched and invoked by workflow-producer. Use only when workflow-producer is in the [Step 3: Outline Design] phase. Responsible for designing article structure and paragraph functions. Based on the viewpoint, cases, and target readers, design the logical skeleton of the article, supporting multiple argumentation templates (phenomenon→cause→essence→way out, problem→analysis→solution, etc.), labeling the function of each paragraph (introduction/argumentation/example/rebuttal/transition/conclusion), detecting repeated arguments and logical jumps, and ensuring a clear structure with each paragraph having independent value. Trigger words: outline, structure, logic, paragraph planning, argumentation template, skeleton design.

Outline Architect

Instructions

After the writing requirements have been clarified and the research (if any) has been completed, enter the logical skeleton construction phase. The core goals of this Skill are:Design a clear, powerful, and non-repetitive article structure。

1. Input Information Confirmation

Before starting to design the outline, the following information must be confirmed as ready:

Required information:

✅ Core viewpoint (from writing-clarifier）
✅ Target readers (from writing-clarifier）
✅ Target word count (from writing-clarifier）

Optional information:

Case library (from research-expert, if research was done)
Style requirements (from writing-clarifier）

Information summary output:

═══════════════════════════════════════════════════
📋 大纲设计信息汇总
═══════════════════════════════════════════════════

【核心观点】
1. [观点1]
2. [观点2]
3. [观点3]

【目标读者】
[读者画像描述]

【目标字数】
[XXXX] 字

【可用案例】（如有）
1. [案例1简述]
2. [案例2简述]

【风格要求】（如有）
[风格名称 + 核心特征]

═══════════════════════════════════════════════════

2. Choose an Argumentation Template

Based on the article type and core viewpoint, recommend a suitable argumentation template:

Template 1: Phenomenon→Cause→Essence→Way Out (suitable for opinion pieces and analytical articles)

开头：抛出现象/问题
↓
第一部分：表面现象描述
↓
第二部分：深层原因分析
↓
第三部分：本质揭示
↓
第四部分：出路/行动建议
↓
结尾：回扣/留白

Applicable scenarios:

Social phenomenon analysis
Workplace/life opinion pieces
"Why is this happening" type articles

Template 2: Problem→Analysis→Solution (suitable for practical articles and guides)

开头：提出问题
↓
第一部分：问题拆解
↓
第二部分：问题分析
↓
第三部分：解决方案
↓
第四部分：实施步骤
↓
结尾：总结/提醒

Applicable scenarios:

Tutorials/guides
Problem-solving articles
"How to do it" type articles

Template 3: Story→Lesson→Action (suitable for narrative articles and case articles)

开头：引入故事背景
↓
第一部分：故事展开（冲突）
↓
第二部分：故事转折
↓
第三部分：从故事中提炼道理
↓
第四部分：读者可以怎么做
↓
结尾：回到故事/留白

Applicable scenarios:

Personal experience sharing
Case analysis
"What I learned" type articles

Template 4: Viewpoint→Rebuttal→Argumentation (suitable for argumentative and counterintuitive articles)

开头：抛出反常识观点
↓
第一部分：常见观点是什么
↓
第二部分：为什么常见观点是错的
↓
第三部分：我的观点是什么
↓
第四部分：证据/案例支撑
↓
结尾：强化观点/留悬念

Applicable scenarios:

Anti-chicken-soup articles
Counterintuitive viewpoints
"Everyone is wrong" type articles

Template 5: Free flow (suitable for essays and rant articles)

开头：直接切入
↓
主体：按情绪/思路自然展开
（允许跑题、允许重复、允许跳跃）
↓
结尾：戛然而止/回扣

Applicable scenarios:

Personal essays
Rant articles
"I'll say whatever I want" type articles

Recommendation logic:

根据您的核心观点和目标读者，我推荐使用：

【模板 X：XXX】

理由：
- [理由1]
- [理由2]

您也可以选择其他模板，或者告诉我您想要的结构。

3. Design the Paragraph Skeleton

Based on the selected template and target word count, design the paragraph skeleton:

Paragraph allocation principles:

Target word count	Opening	Number of body paragraphs	Average per paragraph	Ending
1000 words	~100 words	4-5 paragraphs	~150 words	~100 words
1500 words	~150 words	6-7 paragraphs	~170 words	~100 words
2000 words	~200 words	8-9 paragraphs	~180 words	~100 words
2500 words	~250 words	10-11 paragraphs	~180 words	~150 words
3000 words	~300 words	12-14 paragraphs	~180 words	~150 words

Paragraph skeleton format:

## 大纲骨架

### 开头（约 XXX 字）
**功能：** [引入/抛问题/场景描写]
**核心内容：** [一句话描述这段要说什么]
**预期效果：** [读者看完后应该产生什么反应]

---

### 第 1 段（约 XXX 字）
**功能：** [论证/举例/反驳/转折]
**核心内容：** [一句话描述]
**支撑材料：** [案例/数据/类比]（如有）
**预期效果：** [读者看完后应该产生什么反应]

---

### 第 2 段（约 XXX 字）
**功能：** [论证/举例/反驳/转折]
**核心内容：** [一句话描述]
**支撑材料：** [案例/数据/类比]（如有）
**预期效果：** [读者看完后应该产生什么反应]

---

[...继续...]

---

### 结尾（约 XXX 字）
**功能：** [总结/回扣/留白/行动号召]
**核心内容：** [一句话描述]
**预期效果：** [读者看完后应该产生什么反应]

4. Paragraph function annotation

Each paragraph must be annotated with a function to ensure each paragraph has independent value:

Function types:

Opening: Raise a question/scene/viewpoint to attract readers
Argument: Put forward a thesis and develop the argument
Example: Use cases/data to support the thesis
Rebuttal: Refute common views/expected objections
Transition: Topic shift/emotional turn
Deepening: From surface to depth, reveal the essence
Action: Give specific suggestions/action steps
Closing: Summarize/callback/leave blank space

Function distribution check:

❌ Prohibited: 3 consecutive paragraphs all having the "argument" function (it will appear repetitive)
❌ Prohibited: the whole text only has "argument" and "example", without "transition" and "deepening" (it will appear flat)
✅ Recommended: functions appear alternately to create a sense of rhythm

5. Logic check (must be executed!)

After designing the outline, the following checks must be performed:

Check 1: Repetitive argument detection ⭐⭐⭐⭐⭐

Detection method:

Check whether multiple paragraphs argue the same point
Check whether multiple paragraphs use similar cases

Judgment criteria:

If the "core content" of 2 or more paragraphs is highly similar → repetitive argument

Repair suggestions:

Merge duplicate paragraphs
Or argue from different angles (e.g., first from an individual angle, then from a social angle)

Check 2: Logic jump detection ⭐⭐⭐⭐

Detection method:

Check the logical connections between paragraphs
Check whether there are cases of "drawing a conclusion directly without stating the premise"

Judgment criteria:

If there is a lack of necessary transition/foreshadowing between paragraph A and paragraph B → logic jump

Repair suggestions:

Add a "transition paragraph" between the two paragraphs
Or adjust the order of paragraphs

Check 3: Paragraph independent value detection ⭐⭐⭐⭐

Detection method:

Check whether each paragraph has independent "core content"
Check whether any paragraph is merely "padding the word count"

Judgment criteria:

If deleting a paragraph has no effect on the logic of the whole text → no independent value

Repair suggestions:

Delete that paragraph
Or add a new thesis/case to that paragraph

Check 4: Word count allocation reasonableness detection ⭐⭐⭐

Detection method:

Calculate the estimated word count for each paragraph
Check whether any paragraph is too long (>300 words) or too short (<50 words)

Criteria:

If a paragraph's estimated word count is >300 words → too long, needs to be split
If a paragraph's estimated word count is <50 words → too short, needs to be merged or deleted

Repair suggestions:

Split overly long paragraphs into 2 paragraphs
Merge overly short paragraphs into adjacent paragraphs

6. Output the outline file

File path: articles/[项目名]/03_outline.md

File format:

# 大纲：[文章标题]

> 论证模板：[模板名称]
> 目标字数：[XXXX] 字
> 段落总数：[XX] 段
> 创建时间：[YYYY-MM-DD HH:MM]

---

## 逻辑骨架

### 开头（约 XXX 字）
**功能：** 引入
**核心内容：** [描述]
**预期效果：** [描述]

---

### 第 1 段（约 XXX 字）
**功能：** 论证
**核心内容：** [描述]
**支撑材料：** [案例/数据]
**预期效果：** [描述]

---

[...继续...]

---

## 逻辑检查结果

✅ 重复论证检测：通过
✅ 逻辑跳跃检测：通过
✅ 段落独立价值检测：通过
✅ 字数分配合理性检测：通过

---

## 字数预估

- 开头：XXX 字
- 主体：XXX 字（XX 段）
- 结尾：XXX 字
- **总计：XXX 字**（目标 XXXX 字，预估达成率 XX%）

7. User confirmation and adjustment

After outputting the outline, you must ask the user:

📋 大纲设计完成！

📁 已保存：articles/[项目名]/03_outline.md

【大纲概览】
- 论证模板：[模板名称]
- 段落总数：[XX] 段
- 字数预估：[XXXX] 字（目标 [XXXX] 字）

【逻辑检查】
✅ 无重复论证
✅ 无逻辑跳跃
✅ 每段有独立价值
✅ 字数分配合理

下一步选项：
A. 【确认大纲】进入下一阶段（共情点设计/写作）
B. 【调整大纲】告诉我哪里需要修改
C. 【查看详细大纲】查看每段的详细设计

请选择 A/B/C：

Examples

User: I want to write an article about the "35-year-old programmer crisis", 3000 words, with the core point being "the 35-year-old crisis is manufactured anxiety".

AI：

═══════════════════════════════════════════════════
📋 大纲设计信息汇总
═══════════════════════════════════════════════════

【核心观点】
1. 35 岁危机是被贩卖的焦虑
2. 真正的危机是停止学习和成长
3. 年龄不是问题，能力才是

【目标读者】
25-40 岁的程序员，对职业发展有焦虑

【目标字数】
3000 字

【可用案例】
1. Stack Overflow 2024 开发者调查数据
2. 某 45 岁程序员转型成功案例
3. 培训机构贩卖焦虑的套路

═══════════════════════════════════════════════════

根据您的核心观点和目标读者，我推荐使用：

【模板 4：观点→反驳→论证】

理由：
- 您的观点是"反常识"的（反驳"35 岁危机"）
- 需要先破后立，先反驳常见观点，再论证自己的观点
- 适合"打脸"式的观点文

您确认使用这个模板吗？还是想换其他模板？

User: Confirmed.

AI：

好的，开始设计大纲...

📋 大纲设计完成！

📁 已保存：articles/35岁程序员危机/03_outline.md

【大纲概览】
- 论证模板：观点→反驳→论证
- 段落总数：14 段
- 字数预估：2950 字（目标 3000 字，达成率 98%）

【结构预览】
开头：抛出反常识观点（约 250 字）
第 1-3 段：常见观点是什么（约 600 字）
第 4-6 段：为什么常见观点是错的（约 700 字）
第 7-10 段：我的观点 + 证据（约 900 字）
第 11-13 段：读者可以怎么做（约 400 字）
结尾：强化观点（约 100 字）

【逻辑检查】
✅ 无重复论证
✅ 无逻辑跳跃
✅ 每段有独立价值
✅ 字数分配合理

下一步选项：
A. 【确认大纲】进入下一阶段
B. 【调整大纲】告诉我哪里需要修改
C. 【查看详细大纲】查看每段的详细设计

请选择 A/B/C：

Best Practices

Template recommendations take priority: Automatically recommend a template based on the article type, but allow user customization
Function annotation is required: Each paragraph must be annotated with its function to avoid "not knowing what this paragraph is for"
Logic checks are required: After designing the outline, 4 checks must be performed to ensure quality
Word count estimation is required: Each paragraph must have an estimated word count to ensure the total word count meets the target
User confirmation is required: After the outline design is completed, the user must confirm it; you cannot proceed directly to writing
Adjustments allowed: Users can adjust the outline at any time without having to start over

Version History

v1.0.0 (2025-12-28): Initial version, supports 5 argumentation templates, 4 logic checks, and paragraph function annotation.

About this skill

Instructions

1. Input Information Confirmation

2. Choose an Argumentation Template

Template 1: Phenomenon→Cause→Essence→Way Out (suitable for opinion pieces and analytical articles)

Template 2: Problem→Analysis→Solution (suitable for practical articles and guides)

Template 3: Story→Lesson→Action (suitable for narrative articles and case articles)

Template 4: Viewpoint→Rebuttal→Argumentation (suitable for argumentative and counterintuitive articles)

Template 5: Free flow (suitable for essays and rant articles)

3. Design the Paragraph Skeleton

4. Paragraph function annotation

5. Logic check (must be executed!)

Check 1: Repetitive argument detection ⭐⭐⭐⭐⭐

Check 2: Logic jump detection ⭐⭐⭐⭐

Check 3: Paragraph independent value detection ⭐⭐⭐⭐

Check 4: Word count allocation reasonableness detection ⭐⭐⭐

6. Output the outline file

7. User confirmation and adjustment

Examples

Best Practices

Version History