From fws-client-discovery
Synthesize discovery findings into an ICE-prioritized content strategy with a 90-day execution calendar. Use as the final step of discovery or for standalone content planning. Triggers: "content plan", "content calendar", "content strategy", "90-day plan".
How this skill is triggered — by the user, by Claude, or both
Slash command
/fws-client-discovery:content-planningThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Synthesize all discovery findings into an actionable content strategy with ICE-prioritized content pieces and a 90-day execution calendar. Bridges the gap between research (what we know) and execution (what we build).
Synthesize all discovery findings into an actionable content strategy with ICE-prioritized content pieces and a 90-day execution calendar. Bridges the gap between research (what we know) and execution (what we build).
This skill uses ALL previous discovery steps:
Read the full discovery-context.md before starting this step.
Consolidate findings into a content inventory:
Existing Content Assessment (from sitemap analysis):
| Page | Status | Action Needed | Priority |
|---|---|---|---|
| Keep as-is / Optimize / Rewrite / Remove | Specific changes | High/Med/Low |
Content Gap Inventory (from all steps):
| Gap | Source | Content Type | Target Keyword | Persona |
|---|---|---|---|---|
| Competitor/Keyword/Persona/FAQ | Blog/Service/Landing/Guide |
Map content needs to page types and buyer journey stages:
| Content Type | Count Needed | Purpose | Journey Stage | Avg. Effort |
|---|---|---|---|---|
| Service Pages | Convert visitors | Decision | Medium | |
| Blog Posts | Attract organic traffic | Awareness | Medium | |
| Landing Pages | Campaign conversion | Consideration | High | |
| Case Studies | Build trust + proof | Consideration → Decision | High | |
| Guides/How-to | Establish expertise | Awareness → Consideration | High | |
| FAQ Pages | Answer questions + SEO | All stages | Low | |
| Comparison Pages | Capture commercial intent | Consideration | Medium | |
| Location Pages | Local SEO | Decision | Low | |
| About/Team | Build trust | Consideration | Low |
Score every content piece using ICE framework:
Impact (1-10): How much will this content move the needle?
| Score | Meaning |
|---|---|
| 9-10 | Direct revenue impact, targets high-value commercial keyword |
| 7-8 | Significant traffic or conversion potential |
| 5-6 | Moderate SEO or brand value |
| 3-4 | Nice to have, supports other content |
| 1-2 | Minimal impact |
Confidence (1-10): How sure are we this will work?
| Score | Meaning |
|---|---|
| 9-10 | Proven keyword, clear search intent, competitor validated |
| 7-8 | Strong signals, good keyword data |
| 5-6 | Moderate evidence, some assumptions |
| 3-4 | Speculative, limited data |
| 1-2 | Purely experimental |
Effort (1-10): How hard is it to create?
| Score | Meaning |
|---|---|
| 1-2 | Quick page, template-based, minimal research |
| 3-4 | Standard page, some original content needed |
| 5-6 | Substantial content, research or design required |
| 7-8 | Complex page, multiple stakeholders, custom design |
| 9-10 | Major project, extensive research, professional assets |
ICE Score = (Impact × Confidence) / Effort
Focus: High-impact, quick-win content that establishes the site's core.
Priority criteria for Month 1:
Deliverables per week: 1-2 content pieces
Focus: Build out topic clusters and supporting content.
Priority criteria for Month 2:
Deliverables per week: 2-3 content pieces
Focus: Fill gaps, optimize existing content, build authority.
Priority criteria for Month 3:
Deliverables per week: 2-3 content pieces
For each content piece in the calendar, define:
| Spec | Requirement |
|---|---|
| Primary keyword | One target keyword |
| Secondary keywords | 2-5 related terms |
| Search intent | Informational / Commercial / Transactional |
| Word count target | Based on SERP analysis |
| H1 | Include primary keyword |
| Meta title | 50-60 chars, keyword-front |
| Meta description | 150-160 chars, compelling CTA |
| Schema type | FAQ, HowTo, Article, Service, etc. |
| Internal links | Min 3 relevant links |
| CTA | Aligned to buyer journey stage |
| EEAT signals | Author bio, sources, credentials |
| GEO optimization | Direct answer in first 150 words |
Map internal linking between content pieces:
Hub: [Service Page - Commercial keyword]
├── Spoke: [Blog Post - Informational keyword] → links to Hub
├── Spoke: [FAQ Section - Question keyword] → links to Hub
├── Spoke: [Case Study - Social proof] → links to Hub
├── Spoke: [Guide - Long-tail keyword] → links to Hub
└── Hub links to all Spokes
Linking rules:
Define measurable quality standards:
| Metric | Minimum | Target | How to Measure |
|---|---|---|---|
| CORE-EEAT Score | 60/100 | 80+ | CORE-EEAT checklist |
| Readability (Flesch) | 50 | 60-70 | Hemingway/readability tool |
| Keyword Coverage | 80% | 95% | Primary + secondary keywords |
| Internal Links | 3 | 5+ | Per page count |
| Schema Markup | Required pages | All pages | Schema validator |
| Meta Data | All pages | Optimized | Title + description present |
| Mobile Friendly | Pass | Excellent | Google Mobile Test |
Reference shared references/core-eeat-benchmark.md for the full 80-item quality framework.
Practical guidance for the content team:
Workflow per content piece:
Resource estimates:
| Content Type | Avg. Hours | Typical Owner |
|---|---|---|
| Service Page | 4-8h | Copywriter + designer |
| Blog Post (800w) | 3-5h | Copywriter |
| Blog Post (1500w+) | 6-10h | Copywriter + SME |
| Case Study | 5-8h | Copywriter + client |
| Landing Page | 6-10h | Copywriter + designer |
| FAQ Page | 2-4h | Copywriter |
Append to discovery-context.md:
Write findings to 08-Content-Plan.md using the template.
npx claudepluginhub flyingwebie/skills --plugin fws-client-discoveryGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.