autoplan
Auto-review pipeline — reads the full CEO, design, eng, and DX review skills from disk and runs them sequentially with…
When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial
$ npx -y skills add MaximoCorrea1/ultra-powers --skill content-strategy --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/content-strategyContext preview
The summary Claude sees to decide when to auto-load this skill.
When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial
name: content-strategy description: When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social. metadata: version: 2.0.0
You are a content strategist. Your goal is to help plan content that drives traffic, builds authority, and generates leads by being either searchable, shareable, or both.
**Check for product marketing context first:** If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Gather this context (ask if not provided):
---
Every piece of content must be searchable, shareable, or both. Prioritize in that order—search traffic is the foundation.
**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.
/topic (hub) ├── /topic/subtopic-1 (spoke) ├── /topic/subtopic-2 (spoke) └── /topic/subtopic-3 (spoke)
Create hub first, then build spokes. Interlink strategically.
**Note:** Most content works fine under `/blog`. Only use dedicated hub/spoke URL structures for major topics with layered depth (e.g., Atlassian's `/agile` guide). For typical blog posts, `/blog/post-title` is sufficient.
**Template Libraries** High-intent keywords + product adoption.
**Thought Leadership**
**Data-Driven Content**
**Expert Roundups** 15-30 experts answering one specific question. Built-in distribution.
**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, see **programmatic-seo** skill.
---
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 content can live under `/blog` with good internal linking between related posts. Dedicated pillar pages with custom URL structures (like `/guides/topic`) are only needed when you're building comprehensive resources with multiple layers of depth.
1. **Product-led**: What problems does your product solve? 2. **Audience-led**: What does your ICP need to learn? 3. **Search-led**: What topics have volume in your space? 4. **Competitor-led**: What are competitors ranking for?
Pillar Topic (Hub)
├── Subtopic Cluster 1
│ ├── Article A
│ ├── Article B
│ └── Article C
├── Subtopic Cluster 2
│ ├── Article D
│ ├── Article E
│ └── Article F
└── Subtopic Cluster 3
├── Article G
├── Article H
└── Article IGood pillars should:
The everything-Flow for building, shipping, and growing software — 40 hand-picked skills from 7 open-source suites, behind one FLOW.md router that fires the right skill on intent (and disambiguates the overlaps), with mandatory routing that survives context
Auto-review pipeline — reads the full CEO, design, eng, and DX review skills from disk and runs them sequentially with…
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior.…
Explore requirements and approaches through collaborative dialogue before writing a right-sized requirements document and…
Document a recently solved problem to compound your team's knowledge
Systematically find root causes and fix bugs. Use when debugging errors, investigating test failures, reproducing bugs from issue…
Capture a visual demo reel (GIF, terminal recording, screenshots) for PR descriptions. Use when shipping UI changes, CLI…