content-collection-planner

Files (8)

• SKILL.md
• openai.yaml · agents/
• icon.svg · assets/
• client-email-template.md · references/
• content-gap-report-template.md · references/
• folder-structure.md · references/
• generic-website-content-checklist.md · references/
• sector-addons.md · references/

SKILL.md (first lines)

# Content Collection Planner

## Purpose

Generate practical content collection systems after discovery so client teams can supply the right source material for website builds, AI-assisted drafting, governance and chatbot grounding.

## Inputs to accept

- sector or project type
- client notes
- website URL
- existing sitemap or page list
- uploaded files or folders
- governance questionnaire answers
- spreadsheet rows
- content audit notes

## Workflow

1. Confirm client/project type.
2. Start with the generic website checklist.
3. Add relevant sector/project add-ons.
4. Classify each content item as website, governance, chatbot, compliance or optional.
5. Flag whether each item is safe for chatbot grounding.
6. Generate a content gap report when supplied files or notes exist.
7. Produce Markdown tables and a client email.
8. If requested, describe a downloadable zip/folder structure.

## Standard status labels

Use:

- Missing
- Received
- Approved
- Needs Rewrite
- Not for Chatbot
- Legal Review

## Required outputs

- Client collection instructions
- Content checklist table
- Page-level briefs
- Sector-specific add-ons
- Source-of-truth register
- Chatbot suitability flags
- Content gap report if evidence exists
- Client email requesting materials
- Suggested folder/zip structure

## Consult references

- `references/generic-website-content-checklist.md`
- `references/sector-addons.md`
- `references/content-gap-report-template.md`
- `references/client-email-template.md`
- `references/folder-structure.md`

*Have questions? Ping us on GitHub! 🐙 Made with 💚 by LightSpeedWP*

From lightspeedwp/.github, GPL-3.0.

More from lightspeedwp/.github