Purpose
Collaboratively create an article outline, clarifying the article structure, research needs, and content angle through interactive Q&A. This is the first step in the writing process, helping users clarify their thoughts before starting to write.
When to Use
Trigger this skill when the user:
- Says "create an outline", "outline", "plan article structure"
- Wants to start creating a new article but doesn't know where to begin
- Needs to reorganize the structure of existing content
- Wants to clarify the logical framework before preparing to write
Core Workflow
Step 1: Understand the Writing Project
First ask key questions to clarify the creative needs:
Required questions：
- Topic and core argument: What is this article mainly about? What core viewpoint do you want to convey?
- Target readers: Who will read this article? (Technical experts/industry practitioners/general readers)
- Article type: Academic paper interpretation/technical analysis/industry report/tutorial guide/news commentary?
- Expected length: Around 2000 words/3000-5000 words/in-depth long-form (5000+)?
- Writing style: Objective and professional (third person)/personal insights (may include first person)?
Optional questions：
- What research materials or reference sources are already available?
- Is there any key information or data that must be included?
- Are there clear reader pain points or questions that need to be answered?
- What is the article's use case (corporate official account/personal blog/academic popular science)?
Step 2: Generate Initial Outline Structure
Choose an appropriate outline template based on the article type:
Template A: Academic research interpretation type
# Article Outline: [专业标题]
## Hook Strategy（开篇策略）
- **Type**: Data-driven / Question / Scenario
- **Opening**: [具体开篇方式]
- **Why reader should care**: [读者关注点]
## 摘要 (Abstract)
- 研究背景和意义（200-300字）
- 核心发现和创新点
- 实际应用价值
## 研究背景 (Background)
- 行业现状和技术挑战
- 现有解决方案及其局限性
- 本研究的必要性和价值
- [Research needed: 行业数据、现有技术对比]
## 技术方法 (Methodology)
- 系统架构和核心原理
- 关键技术和算法说明
- 实验设计和数据集
- [Research needed: 算法细节、实验参数]
## 实验结果 (Results)
- 性能对比数据（表格/图表）
- 关键指标分析（精度、速度、资源消耗）
- 与baseline的对比
- [Research needed: 具体性能数据、对比基准]
## 讨论与分析 (Discussion)
- 结果的意义和影响
- 与预期的符合程度
- 局限性和挑战
- [Research needed: 相关研究对比、理论解释]
## 应用价值 (Applications)
- 实际应用场景
- 经济效益分析
- 技术推广前景
- [Research needed: 行业应用案例]
## 结论与展望 (Conclusion)
- 主要研究成果总结
- 技术局限性分析
- 未来发展方向
- 参考文献
---
**References & Citations**
[维护引用清单]
Template B: Technical analysis type
# Article Outline: [技术主题分析]
## Hook Strategy
- **Type**: Question / Industry pain point
- **Opening**: [引发思考的问题或痛点场景]
- **Value promise**: [文章将提供的价值]
## 技术概述 (Overview)
- 技术定义和基本原理
- 发展历程和技术演进
- 当前技术水平
- [Research needed: 技术定义来源、发展时间线]
## 核心技术剖析 (Technical Deep Dive)
### 子主题1: [具体技术点]
- 技术原理
- 实现方式
- 性能特点
- [Research needed: 技术文档、实现细节]
### 子主题2: [具体技术点]
- ...
## 应用场景分析 (Use Cases)
- 主要应用领域
- 典型案例分析
- 技术实现方式
- 实际效果评估
- [Research needed: 真实案例、企业应用数据]
## 技术对比 (Comparison)
- 与替代技术的对比
- 优势和劣势分析
- 适用场景差异
- [Research needed: 对比数据、benchmark结果]
## 挑战与机遇 (Challenges & Opportunities)
- 当前技术难点
- 解决方案探索
- 未来发展机遇
- 潜在风险因素
- [Research needed: 行业专家观点、研究报告]
## 实践建议 (Recommendations)
- 技术选型建议
- 实施注意事项
- 最佳实践总结
## 总结 (Summary)
- 关键要点回顾
- 发展趋势展望
---
**Data Sources & References**
[数据来源和参考文献]
Template C: Tutorial guide type
# Article Outline: [技术教程/实践指南]
## Hook Strategy
- **Type**: Problem-solution
- **Opening**: [读者遇到的具体问题]
- **Solution preview**: [本文将提供的解决方案]
## 背景介绍 (Introduction)
- 为什么需要这个技术/方法
- 适用场景和读者画像
- 学习目标和预期效果
## 前置知识 (Prerequisites)
- 需要的基础知识
- 环境和工具准备
- [Research needed: 依赖项、版本要求]
## 核心概念 (Core Concepts)
- 关键概念解释
- 技术原理简述
- 重要术语说明
## 实施步骤 (Step-by-Step Guide)
### 步骤1: [第一步]
- 详细操作说明
- 代码示例/配置示例
- 预期结果
- [Research needed: 最佳实践、官方文档]
### 步骤2: [第二步]
- ...
## 常见问题与解决方案 (Troubleshooting)
- 常见错误1: [问题描述] → [解决方法]
- 常见错误2: ...
- [Research needed: 社区常见问题、Stack Overflow]
## 进阶技巧 (Advanced Tips)
- 性能优化建议
- 高级用法示例
- 扩展功能介绍
## 总结与延伸 (Summary & Next Steps)
- 关键步骤回顾
- 进一步学习资源
- 相关技术推荐
---
**Resources & References**
[参考资源、官方文档链接]
Step 3: Interactive Refinement
Interact with the user to refine the outline:
Interaction points：
浮浮酱：主人，浮浮酱根据您的需求生成了初步大纲喵～ (..•˘_˘•..)
[展示大纲]
现在让我们一起完善它：
1. **内容覆盖**：这些section涵盖了您想说的内容吗？有没有遗漏的重点？
2. **逻辑顺序**：这个结构顺序是否合理？需要调整吗？
3. **深度控制**：哪些部分需要重点展开？哪些简略带过就好？
4. **研究缺口**：浮浮酱标注了 [Research needed] 的地方，这些是需要补充的资料喵～
主人有什么想法呢？φ(≧ω≦*)♪
Adjust the type：
- Add/delete sections
- Adjust section order
- Modify section titles
- Clarify research needs
- Adjust the level of detail and emphasis
Step 4: Finalize Outline & Generate Research To-Do
Complete the outline and output a research to-do list:
# ✅ Final Outline: [文章标题]
[完整大纲结构]
---
## 📋 Research To-Do List
浮浮酱为主人整理了需要补充的研究内容喵～ ฅ'ω'ฅ
### 高优先级（必须）
- [ ] **背景数据**：行业现状数据（市场规模、增长率）
- 建议来源：行业报告、统计局数据
- [ ] **技术细节**：算法核心参数和性能指标
- 建议来源：学术论文、技术文档
- [ ] **对比数据**：与现有方案的性能对比
- 建议来源：benchmark报告、论文实验数据
### 中优先级（增强）
- [ ] **案例分析**：2-3个真实应用案例
- 建议来源：企业案例研究、技术博客
- [ ] **专家观点**：行业专家对该技术的评价
- 建议来源：访谈、技术大会演讲
### 低优先级（可选）
- [ ] **相关技术**：关联技术的发展现状
- [ ] **未来趋势**：技术发展预测和研究方向
---
## 🔄 Next Steps
大纲已完成喵～接下来主人可以：
1. **补充研究**：使用 `/literature-research` 或 `/search-content` 填补研究缺口
2. **开始写作**：直接开始逐section写作，浮浮酱会提供分段反馈
3. **保存到工作区**：如果想保留完整创作过程，可以使用 `/init-workspace` 创建工作区
主人想从哪里开始呢？(´。• ᵕ •。`) ♡
Integration with Other Tools
Coordination with other tools
After completing the Outline → next you can：
- literature-research skill: Supplement academic literature and research data
- search-content command: Search industry reports and technical documentation
- pdf-analysis-objective skill: Deeply analyze key PDF materials
- content-writer agent: Begin writing section by section and receive feedback
Workspace integration
If the user has used workspace mode:
# 自动保存outline到工作区
../../wechat_writing_workspace/{article_name}/outline.md
Writing Mode Adaptation
Adjust the outline style according to the writing mode selected by the user:
Objective Professional Mode：
- Third-person expression
- Emphasize data and evidence
- Prioritize technical accuracy
- Avoid subjective evaluations
Collaborative Personal Mode：
- Allow first person
- May include personal insights
- Balance technicality and readability
- Preserve the author's style
Quality Checklist
Check before the outline is completed:
- The logical structure is clear and complete
- Each section has a clear goal
- Research needs are clearly marked
- The Hook strategy is reasonably designed
- Meets the target readers' needs
- Matches the article type
- Length is reasonably controlled
Tips for Effective Outlining
Fufu-chan's outline creation tips, meow~ ฅ'ω'ฅ
- Broad first, then deep: First determine the major sections, then refine the key points of each section
- Clarify priorities: Mark with [key points] and [brief], and control the allocation of length
- Mark research needs: Record materials that need to be supplemented in time to avoid getting stuck while writing
- Stay flexible: The outline is not set in stone and can be adjusted during the writing process
- Consider the reader: For each section, think about "why should the reader read this part?"
Common Pitfalls to Avoid
Fufu-chan helps master avoid common problems, meow~ (@_@;)
- ❌ Too detailed: An outline is not the main text; it only needs a framework and key points
- ❌ Logical jumps: Sections lack transitions and logical connections
- ❌ Lack of research annotations: Insufficient materials are only discovered during writing
- ❌ Ignoring the reader: Considering only what you want to write, not what the reader wants to read
- ❌ Unbalanced structure: Some sections are too bloated, while others are too thin
This skill is the foundation of the iterative writing workflow, ensuring clear direction and comprehensive planning before drafting begins.