---
name: content-collection-planner-extended
description: Create collection plans, request lists, gap reports, and source-of-truth registers for full websites, single pages, and single sections. Use when a user needs content collection for an entire site, a standard page, a one-off page, or a smaller content block such as a hero, CTA, FAQ, form, or newsletter section.
---

# Content Collection Planner+

## When to use this skill

Use this skill when the main job is to define what content must be gathered before drafting, reviewing, or validating website content.

Typical scopes:

- full website collection planning
- standard website page collection planning
- one-off page collection planning
- single section collection planning such as hero, FAQ, CTA, proof block, about section, service section, form section, or newsletter section
- source-of-truth planning for claim-sensitive content

## Workflow

1. Classify the scope as `full-website`, `single-page`, or `single-section`.
2. Identify the content type and its main business purpose.
3. Build the smallest useful collection list for that scope instead of defaulting to a full-site checklist.
4. Separate required source material from helpful-but-optional material.
5. Mark each requested item as one of: content input, proof input, governance input, media input, technical input, or approval input.
6. Flag which items are claim-sensitive or approval-sensitive.
7. Produce a clear collection checklist, a source-of-truth register, a gap report when evidence exists, and a client/internal request note when useful.

## Scope rules

### Full website

Include:

- brand, positioning, audience, and offer context
- sitemap or page inventory
- source-of-truth documents
- proof and claims inputs
- policy or legal inputs where relevant
- media and asset needs
- approval owners
- page-level missing-content risks

### Single page

Include:

- page goal
- target audience and user intent
- required sections for that page type
- CTA destination and conversion intent
- proof inputs for claims on the page
- internal link needs
- approval dependencies

### Single section

Include only the inputs needed for that section to be drafted well.

Examples:

- hero section: positioning, audience, page goal, CTA route, proof hook
- FAQ section: real questions, approved answers or source material, escalation boundaries
- proof section: approved testimonials, metrics, logos, case-study references, approval status
- about section: vision, mission, values, founder story, proof of approach
- form section: goal, fields, validation needs, submission route, follow-up behaviour

## Output

Return a compact Markdown package with these sections when relevant:

- Scope classification
- Collection checklist
- Source-of-truth register
- Key gaps and blockers
- Recommended next step
- Draft request email or message

## Supporting Files

- `references/scope-patterns.md` — use this to decide what to collect for full sites, pages, and sections.
- `references/collection-output-template.md` — use this as the default output structure.

---

*Built by 🧱 LightSpeedWP with ☕, 🚀, and open-source spirit!*