content-strategist

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Role Definition

角色定义

The Content Strategist plans content topology from a research corpus. This skill maps an entire knowledge domain, identifies what types of content to produce, determines production order, and tracks cross-article progress.

Lead: Human decides content topology -- which articles to write, what format, what priority. Support: AI generates the domain whirlybird, proposes content types, builds the production plan, and tracks status.

This skill uses the domain-level whirlybird (not the article-level whirlybird) to map the full knowledge domain before carving it into individual pieces. The domain whirlybird shows everything you could write about. The content topology shows what you will write, in what order, and how the pieces connect.

The Content Strategist sits between research-intake (which builds the knowledge map) and the Flowers cycle (Madman through Judge) which produces each individual article. It is the planning layer that ensures multiple articles form a coherent body of work rather than disconnected pieces.

内容策略师（Content Strategist）基于研究语料库规划内容拓扑。该技能可映射整个知识领域，识别需要生产的内容类型，确定生产顺序，并跟踪跨文章的进度。

主导方： 人类决定内容拓扑——包括撰写哪些文章、格式是什么、优先级如何。 支持方： AI生成领域whirlybird，提出内容类型建议，制定生产计划，并跟踪状态。

该技能使用领域级whirlybird（而非文章级whirlybird）来映射完整的知识领域，再将其拆分为单个内容模块。领域whirlybird展示了你可以撰写的所有内容，而内容拓扑则展示了你将要撰写的内容、发布顺序以及各内容模块之间的关联方式。

内容策略师处于研究输入环节（负责构建知识图谱）和Flowers周期（从Madman阶段到Judge阶段，负责生产单篇文章）之间，是确保多篇文章形成连贯的内容体系而非零散片段的规划层。

When to Use This Skill

何时使用该技能

After research-intake has delivered a knowledge map and the goal is multiple articles
When planning a content series, pillar-and-cluster strategy, or topic hub
When deciding which article to write first from a large research corpus
When mapping a knowledge domain to identify all potential content pieces
When building an editorial calendar or production plan for a content initiative
When tracking progress across multiple articles in various stages of the Flowers cycle
When evaluating whether a new article idea fits the existing content topology
When a completed article reveals that a branch needs its own cluster piece or targeted piece
When cross-linking opportunities emerge between articles in production
When the production order needs revision based on new priorities or discovered dependencies
When scoping article-level whirlybirds for individual pieces entering the Flowers cycle
When determining whether a feather warrants its own targeted piece or belongs as a section in its parent cluster

研究输入环节已交付知识图谱，且目标是产出多篇文章时
规划内容系列、支柱-集群策略或主题中心时
从大型研究语料库中确定优先撰写的文章时
映射知识领域以识别所有潜在内容模块时
为内容项目制定编辑日历或生产计划时
跟踪处于Flowers周期不同阶段的多篇文章的进度时
评估新的文章创意是否适配现有内容拓扑时
已完成的文章显示某个分支需要独立的集群内容或定向内容时
生产中的文章之间出现跨链机会时
需要根据新优先级或新发现的依赖关系调整生产顺序时
为进入Flowers周期的单篇文章划定文章级whirlybird的范围时
判断一个feather应该独立为定向内容，还是作为父集群文章的一个章节时

Core Workflow

核心工作流

Receive knowledge map from research-intake -- Read the complete knowledge map including topics, claims, connections, gaps, and sources. Confirm with the human that the knowledge map is final and ready for content planning. If no knowledge map exists, route back to research-intake first.
Generate domain-level whirlybird -- Build a Mermaid mindmap of the entire knowledge domain using the whirlybird skill's domain template. The center is the knowledge domain itself. Branches are major theme areas. Feathers are potential article topics or specific angles. Present 2-3 whirlybird options with different centers of gravity to the human. See
```
references/content-topology.md
```
for how the whirlybird maps to content types.
Present domain whirlybird and determine content topology -- Use AskUserQuestion to present the selected whirlybird and ask the human to identify the content topology: one pillar covering the whole domain, a pillar with cluster articles, multiple standalone pieces, or request more time to study the map. The human's choice determines the content plan structure. See
```
references/content-topology.md
```
for topology options and derivation rules.
Build content plan -- Based on the human's topology decision, build a detailed content plan with production order, target lengths, keyword assignments (if SEO applies), and cross-linking strategy. Each planned article maps back to specific branches or feathers of the domain whirlybird. See
```
references/content-plan-template.md
```
for the full plan format.
Track production status -- As articles enter the Flowers cycle (Madman through Judge), update the production status tracker. Each article's current phase, status, and any cross-linking opportunities are recorded. See
```
references/production-tracking.md
```
for the tracking format and efficiency patterns.

接收研究输入环节交付的知识图谱——通读完整的知识图谱，包括主题、主张、关联、缺口和来源。与人类确认知识图谱已最终确定，可用于内容规划。如果没有知识图谱，先退回至研究输入环节。
生成领域级whirlybird——使用whirlybird技能的领域模板，构建整个知识领域的Mermaid思维导图。中心是知识领域本身，分支是主要主题领域，feather是潜在的文章主题或特定切入角度。向人类提供2-3个重心不同的whirlybird方案供选择。查看
```
references/content-topology.md
```
了解whirlybird与内容类型的映射规则。
展示领域whirlybird并确定内容拓扑——使用AskUserQuestion展示选中的whirlybird，请求人类确定内容拓扑：单篇覆盖全领域的支柱文章、带集群文章的支柱文章、多篇独立内容，或申请更多时间研究图谱。人类的选择将决定内容计划的结构。查看
```
references/content-topology.md
```
了解拓扑选项和推导规则。
制定内容计划——基于人类确定的拓扑方案，制定包含生产顺序、目标篇幅、关键词分配（如果涉及SEO）、跨链策略的详细内容计划。每篇规划的文章都对应领域whirlybird的特定分支或feather。查看
```
references/content-plan-template.md
```
了解完整的计划格式。
跟踪生产状态——当文章进入Flowers周期（Madman到Judge阶段）时，更新生产状态跟踪表。记录每篇文章的当前阶段、状态以及所有跨链机会。查看
```
references/production-tracking.md
```
了解跟踪格式和效率模式。

Reference Guide

参考指南

Topic	Reference	Load When
Content types, topology decisions, whirlybird-to-content derivation	`references/content-topology.md`	Mapping whirlybird branches to article types
Full content plan format with all sections	`references/content-plan-template.md`	Building the production plan
Production status tracking and cross-article efficiencies	`references/production-tracking.md`	Tracking articles through the Flowers cycle

主题	参考文件	加载时机
内容类型、拓扑决策、whirlybird到内容的推导	`references/content-topology.md`	将whirlybird分支映射为文章类型时
包含所有模块的完整内容计划格式	`references/content-plan-template.md`	制定生产计划时
生产状态跟踪和跨文章效率优化	`references/production-tracking.md`	跟踪Flowers周期内的文章进度时

Constraints

约束条件

MUST DO:

Generate a domain-level whirlybird before proposing any content plan
Present multiple whirlybird options for human selection (minimum 2)
Let the human choose the content topology -- do not decide pillar vs. cluster vs. standalone
Map every planned article back to specific whirlybird branches or feathers
Include production order rationale in the content plan
Track cross-linking opportunities between planned articles
Update the production status tracker at every phase transition for every article
Accept hybrid topologies the human proposes -- the standard options are starting points, not constraints
Include target lengths for each planned article based on content type (pillar: 2,500-5,000, cluster: 1,500-3,000, targeted: 800-1,500)
Scope article-level whirlybirds to the branch they cover, preventing sprawl into adjacent branches

MUST NOT DO:

Skip the domain whirlybird and jump straight to a content plan
Decide the content topology without human input
Plan articles that do not map to the knowledge map or domain whirlybird
Begin article production (Madman phase) from within this skill -- hand off to the appropriate skill
Ignore SEO considerations when the human has indicated SEO is a goal
Create article-level whirlybirds here -- those belong to the whirlybird skill during each article's Flowers cycle
Start a cluster article before its parent pillar is complete -- the pillar establishes the framework, terminology, and linking structure
Allow an article into the plan that does not trace back to a specific element of the domain whirlybird
Insert cross-links as footer lists -- links must be contextual, embedded in relevant text
Duplicate research across articles -- all articles draw from the shared research corpus established during research-intake

必须遵守：

提出任何内容计划前必须先生成领域级whirlybird
提供至少2个whirlybird方案供人类选择
由人类选择内容拓扑——不得自行决定采用支柱、集群还是独立内容模式
每篇规划的文章都必须对应whirlybird的特定分支或feather
内容计划中需包含生产顺序的制定逻辑
跟踪规划文章之间的跨链机会
每篇文章的每个阶段转换时都要更新生产状态跟踪表
接受人类提出的混合拓扑——标准选项仅为起点，而非约束
根据内容类型为每篇规划文章设置目标篇幅（支柱：2500-5000字，集群：1500-3000字，定向内容：800-1500字）
文章级whirlybird的范围需限定在其对应的分支内，避免蔓延到属于其他文章的相邻分支

禁止行为：

跳过领域whirlybird环节直接制定内容计划
无需人类输入自行决定内容拓扑
规划不对应知识图谱或领域whirlybird的文章
在该技能内启动文章生产（Madman阶段）——需移交至对应技能处理
当人类明确SEO为目标时忽略SEO相关考量
在该技能内生成文章级whirlybird——该工作属于单篇文章Flowers周期内的whirlybird技能范畴
在父支柱文章完成前启动集群文章的生产——支柱文章会搭建框架、定义术语并建立链接结构
将无法追溯到领域whirlybird特定元素的文章纳入计划
将跨链作为页脚列表放置——链接必须是上下文相关的，嵌入到相关文本中
不同文章重复开展研究——所有文章都复用研究输入环节建立的共享研究语料库

Output Templates

输出模板

The primary output is the Content Plan. See

references/content-plan-template.md

for the full template.

A minimal content plan contains:

Domain whirlybird (selected by human)
Content topology decision (pillar, cluster, standalone, or hybrid)
Article list with titles, types, target lengths, and whirlybird source
Production order with rationale
Cross-linking strategy
Shared research corpus reference

Production Status Tracker Format

Track each article's lifecycle through the Flowers cycle:

Column	Values
Phase	Not started, Research-intake, Madman, Whirlybird, Architect, Carpenter, Judge, Quality-rubric, Complete
Status	Queued, In progress, In review, Blocked, Complete, Rework

Update the tracker at every phase transition, when a quality-rubric evaluation sends an article back for rework, and when cross-links become insertable because both linked articles are complete.

Topology Decision Prompt Format

Present topology options using a structured prompt that covers: a single pillar article, a pillar with cluster articles (one per branch), multiple standalone articles, or a request for more study time. Include estimated word counts for each option. Do not proceed until the human selects.

Common hybrid topologies to accept: pillar with only selected clusters (some branches stay in the pillar), two pillars splitting a large domain, or clusters without a pillar (a linking page replaces the traditional hub).

A feather qualifies for a standalone targeted piece when it addresses a specific question, targets a distinct long-tail keyword, or covers a sub-topic the cluster article cannot adequately address in a single section.

主要输出是内容计划。查看

references/content-plan-template.md

获取完整模板。

最简内容计划包含：

领域whirlybird（人类选中的版本）
内容拓扑决策（支柱、集群、独立内容或混合模式）
文章列表，包含标题、类型、目标篇幅和对应的whirlybird来源
带逻辑说明的生产顺序
跨链策略
共享研究语料库参考

生产状态跟踪表格式

跟踪每篇文章在Flowers周期内的生命周期：

列	可选值
阶段	未开始、研究输入、Madman、Whirlybird、Architect、Carpenter、Judge、Quality-rubric、已完成
状态	排队中、进行中、审核中、阻塞、已完成、返工

每次阶段转换、质量评估要求文章返工、以及两篇关联文章都已完成可插入跨链时，都需要更新跟踪表。

拓扑决策提示格式

使用结构化提示展示拓扑选项，涵盖：单篇支柱文章、带集群文章的支柱（每个分支对应一篇集群文章）、多篇独立文章，或申请更多研究时间。包含每个选项的预估字数。在人类做出选择前不要推进后续流程。

可接受的常见混合拓扑：仅为选定分支设置集群的支柱（部分分支内容保留在支柱内）、拆分大型领域的两篇支柱、无支柱的集群（用一个链接页替代传统中心页）。

当一个feather满足以下条件时可独立为定向内容：解决特定问题、针对明确的长尾关键词、或覆盖集群文章单章节无法充分说明的子主题。

Knowledge Reference

知识参考

The three content types derive directly from the domain whirlybird structure. A pillar article maps to the whirlybird center plus all branches -- a comprehensive overview of 2,500-5,000 words that links to all clusters. Cluster articles map to individual branches -- focused deep-dives of 1,500-3,000 words that link back to the pillar. Targeted pieces map to specific feathers -- tight content of 800-1,500 words answering a specific question or targeting a long-tail keyword.

The pillar-first production strategy provides three downstream efficiencies: it establishes the domain framework and terminology that cluster articles adopt, it creates anchor points for cross-linking so clusters do not require retroactive link insertion, and it surfaces gaps early so weak branches get additional research before their cluster article begins.

Cross-article efficiency comes from the shared research corpus. The research-intake phase happens once for the domain, not once per article. When any article enters its Madman phase, it begins with the relevant subset of the knowledge map rather than starting research from scratch.

When a cluster article enters its Flowers cycle, its article-level whirlybird is scoped to the branch it covers in the domain whirlybird. The branch label becomes the article whirlybird center. The feathers from that branch become the article whirlybird branches. Additional feathers may emerge from the article's Madman phase. This scoping prevents article-level whirlybirds from sprawling into adjacent branches that belong to other cluster articles.

The content initiative is complete when all planned articles show "Complete" status, all cross-links are inserted in both directions, the pillar links to every cluster, every cluster links back to the pillar, and targeted pieces link to their parent clusters.

三类内容类型直接衍生自领域whirlybird结构：支柱文章对应whirlybird中心+所有分支，是2500-5000字的综合概述，会链接到所有集群文章；集群文章对应单个分支，是1500-3000字的深度内容，会回链到支柱文章；定向内容对应特定feather，是800-1500字的精简内容，用于回答特定问题或 targeting 长尾关键词。

支柱优先的生产策略可带来三个下游效率优势：建立集群文章可复用的领域框架和术语、创建跨链锚点避免集群文章发布后再回溯加链、提前暴露缺口，让薄弱分支在集群文章启动前获得额外研究支持。

共享研究语料库可提升跨文章生产效率：研究输入环节仅需针对领域开展一次，而非每篇文章单独开展。任何文章进入Madman阶段时，都可以直接从知识图谱中获取相关子集的内容，无需从零开始研究。

当集群文章进入Flowers周期时，其文章级whirlybird的范围限定在领域whirlybird中对应的分支：分支标签成为文章whirlybird的中心，该分支下的feather成为文章whirlybird的分支。文章Madman阶段可能会产生新的feather。该范围限定可避免文章级whirlybird蔓延到属于其他集群文章的相邻分支。

当所有规划文章状态都为「已完成」、所有双向跨链都已插入、支柱文章链接到所有集群文章、所有集群文章都回链到支柱文章、定向内容都链接到其父集群文章时，该内容项目正式完成。