跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
搜索与研究

content-strategist

Use when planning a multi-article content strategy from a research corpus, creating domain maps for content topology, building production plans for pillar and cluster articles, or tracking cross-article production.

https://github.com/Jeffallan · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add Jeffallan/writing-with-agents --skill content-strategist

技能说明


name: content-strategist description: Use when planning a multi-article content strategy from a research corpus, creating domain maps for content topology, building production plans for pillar and cluster articles, or tracking cross-article production. license: MIT metadata: author: https://github.com/Jeffallan company: https://synergetic.solutions version: "1.0.0" domain: strategy triggers: content strategy, content plan, pillar article, cluster articles, domain mapping, content topology, multi-article planning, editorial calendar, content production role: specialist scope: design output-format: document related-skills: research-intake, whirlybird, knowledge-harvester

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.

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

Core Workflow

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

Reference Guide

TopicReferenceLoad When
Content types, topology decisions, whirlybird-to-content derivationreferences/content-topology.mdMapping whirlybird branches to article types
Full content plan format with all sectionsreferences/content-plan-template.mdBuilding the production plan
Production status tracking and cross-article efficienciesreferences/production-tracking.mdTracking articles through the Flowers cycle

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)
  • Sco
阅读完整来源 ↗