计划执行与检查节点
executing-plans
按既定实施计划完成工作,保持过程检查和反馈。
suede-content-strategy【效率与协作】Suede-owned content-strategy discipline for audience questions, content pillars, topic clusters, editorial priorities, cadence, distribution, refreshes, and stop-doing decisions. Use when deciding what to publish, why it deserves resources, and how the portfolio compounds. NOT FOR: writing an individual asset (use suede-copy), technical or on-page SE…
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
Use this Suede content-strategy playbook to plan evidence-backed content that earns search, sharing, trust, or qualified demand.
Read .agents/product-marketing.md first if it exists and ask only for what it does not cover; see suede-product-marketing for path fallbacks.
Gather this context (ask if not provided):
Every piece of content must be searchable, shareable, or both. Searchable is the default first priority because search demand is measurable; treat that as a starting rule, not a universal truth, and reverse it when the user's goal or evidence says otherwise (a category with no search volume, a brand-led launch). Record which order you chose and why: it feeds the weights in "Prioritizing Content Ideas."
Searchable content captures existing demand. Optimized for people actively looking for answers.
Shareable content creates demand. Spreads ideas and gets people talking.
Use-Case Content Formula: [persona] + [use-case]. Targets long-tail keywords.
Hub and Spoke Hub = comprehensive overview. Spokes = related subtopics. Create the hub first, then build spokes, and interlink them. See "Content Pillars and Topic Clusters" below for the structure and the URL guidance.
Template Libraries High-intent keywords + product adoption.
Thought Leadership
Data-Driven Content
Expert Roundups A selected set of relevant, verified experts answering one specific question. Distribution depends on contributor permission and actual promotion.
Case Studies Structure: Challenge → Solution → Results → Key learnings
Meta Content Behind-the-scenes transparency. "How We Got Our First $5k MRR," "Why We Chose Debt Over VC."
For programmatic content at scale, route the data and template system to
suede-programmatic-seo.
Content pillars are the 3-5 core topics your brand will own; each pillar spawns a cluster of related content. Most of the time all of it can live under /blog with good internal linking. Dedicated pillar pages with custom URL structures (like /guides/topic) are only needed for comprehensive resources with multiple layers of depth.
Structure is pillar (hub) → subtopic clusters → articles, each article linking to its siblings and up to the hub. The Topic cluster map in Output Format is the shape to emit.
Good pillars should:
Map topics to the buyer's journey using the modifier set for each stage:
| Stage | Modifiers | Triggered by |
|---|---|---|
| Awareness | "what is," "how to," "guide to," "introduction to" | Customers asking basics |
| Consideration | "best," "top," "vs," "alternatives," "comparison" | Customers evaluating multiple tools |
| Decision | "pricing," "reviews," "demo," "trial," "buy" | Pricing coming up in sales calls |
| Implementation | "templates," "examples," "tutorial," "how to use," "setup" | Support tickets showing setup struggles |
Worked example, Consideration stage for a project-management tool: "Best Project Management Tools for Remote Teams," "Asana vs Trello vs Monday," "Basecamp Alternatives." Apply the same pattern per stage using the user's own category nouns, never these ones.
Before external research, inspect the tools and connected sources that are currently callable and authorized in this session. Use product analytics, Search Console or keyword exports, customer material, support data, approved Drive sources, or a callable browser/search surface only when access actually exists. Record each source URL or file, owner, retrieval date, and relevant scope.
If no external research surface is available, continue with user-supplied URLs, exports, transcripts, and known first-party evidence. Otherwise return a compact manual-research list with exact queries and fields to capture. Label hypotheses and unverified competitor observations; never imply that a search was run.
If user provides keyword exports (Ahrefs, SEMrush, GSC), analyze for:
Output as prioritized table: | Keyword | Volume | Difficulty | Buyer Stage | Content Type | Priority |
If user provides sales or customer call transcripts, extract:
Output content ideas with supporting quotes.
If user provides survey data, mine for:
If an authorized browser or search surface is currently callable, use it to find recent first-party community evidence. Otherwise ask for relevant URLs or provide the queries below for manual collection.
Reddit: site:reddit.com [topic]
Quora: site:quora.com [topic]
Other: Indie Hackers, Hacker News, Product Hunt, industry Slack/Discord
For each item, capture the source URL, publication date, retrieval date, community context, and a short evidence excerpt. Distinguish engagement signals from proof of customer demand.
Use a currently callable, authorized browser/search surface or user-supplied competitor URLs. If neither is available, produce a manual research checklist and do not invent page inventories, rankings, engagement, or gaps.
Find their content: site:competitor.com/blog
Analyze:
Identify hypotheses to validate:
Extract from customer-facing teams:
Score each idea on four factors. The weights below are an illustrative starting point, not a universal truth; change them to match the user's business goal and record the chosen decision rule.
| Idea | Customer Impact (40%) | Content-Market Fit (30%) | Search Potential (20%) | Resources (10%) | Total |
|---|---|---|---|---|---|
| Topic A | 8 | 9 | 7 | 6 | 8.0 |
| Topic B | 6 | 7 | 9 | 8 | 7.1 |
A portfolio compounds only if something leaves it. Every strategy must name what stops, not just what starts. Audit existing assets against dated evidence, traffic, conversions, rankings, and last-updated date, and assign each one of four outcomes:
| Outcome | When | What it means |
|---|---|---|
| Keep | Still ranking or converting against its goal, and the claims are current | No action; next audit at the normal cadence |
| Refresh | The topic still matters and the URL still has authority, but the piece has decayed: stale data, dated claims, or a slipping position | Rewrite in place, keep the URL, record the new last-updated date |
| Consolidate | Two or more pieces target the same intent and split their own signal | Merge into the strongest URL, redirect the others, fold the unique sections in |
| Kill | The topic no longer serves a pillar, or two consecutive review windows show no traffic, no conversions, and no strategic use | Propose removal or de-indexing, and stop there, because Boundaries forbids executing it |
Decision rule, in order: duplicated intent → Consolidate; else topic still maps to a live pillar → Refresh; else → Kill. Never refresh a piece whose pillar was retired: that is sunk cost wearing an editorial hat. Every row names the evidence that triggered it (metric, window, source) and the accountable owner; recommending is the whole job, since publishing, deleting, redirecting, and de-indexing all need explicit authorization.
Hand the recurring cadence that keeps this audit running, decay watch, ranking-drop watch, refresh queue, to suede-marketing-loops. This skill decides what gets refreshed or killed; that one decides how often the check runs.
The generic content strategy writes itself, which is exactly the problem. Do not ship:
Emit the strategy in exactly this shape:
## Content pillars
| Pillar | The claim it owns | Evidence it matters to the ICP | Product connection |
|---|---|---|---|
| [pillar] | [one sentence] | [source + date] | [what it sells] |
## Priority topics
### [Topic title]
- **Type:** searchable / shareable / both: [use-case, hub-and-spoke, thought
leadership, data-driven, case study, meta]
- **Target query + buyer stage:** [query]: [awareness / consideration /
decision / implementation]
- **Why this topic:** [the customer-research evidence, with its source and date]
- **Score and owner:** [Impact / Fit / Search / Resources] = [total]; [owner,
rough effort]
## Topic cluster map
[Pillar]
├── [Cluster]
│ ├── [Article] → links to [Article]
│ └── [Article]
└── [Cluster]
└── [Article]
## Stop-doing
| Existing asset | Outcome | Evidence | Owner |
|---|---|---|---|
| [URL] | Keep / Refresh / Consolidate / Kill | [metric, window, source] | [who] |
## Open questions
[What could not be evidenced, and what would settle it]
suede-copy.suede-seo-audit.suede-programmatic-seo.suede-emails or suede-social.suede-newsroom. A weekly founder interview or voice note that feeds separate founder and company account lanes uses that skill's founder-led mode.suede-marketing-loops.suede-marketing-psychology.suede-content-strategy.