content workflow
Turn Source Signals into Content Update Plan with AI
A workflow for turning official docs, GitHub issues, Reddit threads, and customer questions into a practical content update plan.
What This Workflow Does
This workflow helps you combine trusted sources and user discussion into a prioritized content plan with clear page updates, review angles, and verification notes.
Best For
- updating SEO and AI-search content
- turning issue threads into review-led page ideas
- planning source-backed guides, workflows, and packs
Before You Start
- Collect official sources first.
- Collect user discussion only as perspective, not proof.
- Decide which audience the next update should help.
Step-by-Step Workflow
- Separate sources into official facts, examples, community indexes, and user discussion.
- Extract repeated user needs, objections, and confusing terms.
- Map each need to a page type: guide, skill, workflow, use-case hub, pack, or builder page.
- Score each idea by user value, search intent, freshness risk, and ease of execution.
- Create a content update plan with pages to edit, pages to create, internal links, and review notes.
- Flag claims that need re-checking before publication.
Copy This Workflow
Copy This Workflow
I want to turn source signals into a content update plan.
Use official docs as factual sources. Use GitHub issues, Reddit, comments, and discussions only as review perspective and user language. Do not treat user comments as proof.
Create a prioritized plan that includes:
- user need
- source evidence
- review angle
- recommended page type
- SEO target
- AI-search/GEO target
- pages to create or update
- internal links
- claims to verify
Input Template
Input Template
Audience: [individual, freelancer, small business owner, local business owner, solo founder]
Official sources: [links or notes]
Example repositories: [links or notes]
User discussion signals: [issues, Reddit, HN, comments, customer questions]
Existing pages: [pages that may need updates]
Business goal: [traffic, starter pack downloads, newsletter, paid pack interest]
Constraints: [tone, claims to avoid, sources that must be verified]
Output Format
Output Format
1. Audience need summary
2. Source signal table
3. Content opportunities
4. Priority order
5. Page update checklist
6. Review and verification notes
Example
Example
Example input:
Audience: small business owners.
Official sources: Agent Skills docs and skill structure notes.
User signals: confusion about prompts vs skills, fear of bad customer replies, desire for reusable templates.
Example output:
A plan to update the AI skill basics guide, add a starter library guide, expand the starter pack, and create a builder page with a simple copy-ready template.
Quality Checklist
Quality Checklist
- Official facts are separated from user opinions.
- Each idea maps to a real user need.
- The plan includes both SEO and AI-search intent.
- Claims needing verification are visible.
- The first tasks are small enough to execute.