{"slug":"content-flywheel","title":"Content Flywheel: Feedback to Fresh Ideas","tags":["content-strategy","ideation","flywheel","planning"],"agent_summary":"Three-command content flywheel system that converts customer feedback into non-repeating content ideas using persistent tracking: /analyze (themes), /flywheel (generate ideas), /track (manage history).","trigger_phrases":["content flywheel","content ideas from feedback","never repeat content","content idea tracker","analyze customer feedback for content","content ideation system"],"runnable":true,"markdown":"\n# Content Flywheel: Feedback to Fresh Ideas\n\nThe flywheel turns customer/audience feedback into content ideas that never repeat. It gets smarter with each run because it maintains a persistent tracker.\n\n```\nCustomer Feedback → Theme Analysis → Content Ideas → Tracker Update\n       ↑                                                    │\n       └────────────────────────────────────────────────────┘\n```\n\n---\n\n## /analyze Command\n\n**Purpose:** Categorize raw customer feedback into actionable themes.\n\n### Input Sources\n- Google Sheet, CSV, survey responses, community posts, support tickets, onboarding questionnaires\n\n### Output Format\n```\nFEEDBACK ANALYSIS — [Source Name]\n─────────────────────────────────\nTotal entries analyzed: [count]\n\nTHEME RANKINGS:\nRank | Theme | Frequency | % of Total | Key Phrases Used\n1    | [theme] | [count] | [%] | \"[exact customer words]\"\n\nNOTABLE QUOTES:\n- \"[verbatim customer quote]\" — re: [theme]\n```\n\n---\n\n## /flywheel Command\n\n**Purpose:** Generate fresh content ideas based on analyzed themes, deduped against the tracker.\n\n### Idea Generation Rules\n- Ideas must be rooted in actual customer language/pain points\n- Each idea needs: topic, format, angle, and which theme it serves\n- Check every idea against the tracker — if a substantially similar idea exists, skip it\n- Prioritize themes with highest frequency but lowest existing coverage\n\n### Output Format\n```\nCONTENT FLYWHEEL — Run [date]\n──────────────────────────────\nEMAIL NEWSLETTER IDEAS:\n1. Topic: [topic] | Theme: [theme] | Angle: [angle]\n\nYOUTUBE VIDEO IDEAS:\n1. Topic: [topic] | Theme: [theme] | Format: [tutorial/commentary] | Angle: [angle]\n\nSOCIAL MEDIA IDEAS:\n1. Topic: [topic] | Platform: [platform] | Theme: [theme] | Format: [carousel/thread/reel]\n\nNEW IDEAS GENERATED: [count]\nDUPLICATES AVOIDED: [count]\n```\n\n**Defaults:** 5 email, 5 YouTube, 10 social, 5 community ideas per run.\n\n---\n\n## /track Command\n\n**Purpose:** Manage the content recommendations tracker.\n\n### Tracker File: content-tracker.md\n\n```markdown\n# Content Tracker\nLast updated: [date]\nTotal ideas tracked: [count]\n\n## Generated Ideas\n| Date | Channel | Topic | Theme | Status |\n|------|---------|-------|-------|--------|\n| [date] | Email | [topic] | [theme] | new/used/skipped |\n```\n\n### Track Operations\n- **Add**: After each /flywheel run, new ideas auto-append\n- **Mark used**: `track [topic] as used` — moves idea to Used section\n- **Status check**: `track status` — shows ideas per channel, used vs unused\n- **Clean**: `track clean` — archive ideas older than 90 days\n\n---\n\n## Rules\n\n1. NEVER generate a content idea that substantially duplicates something in the tracker\n2. Always use actual customer language in ideas, not marketing jargon\n3. The tracker file is the single source of truth\n4. Theme ranking drives idea priority\n5. Every /flywheel run MUST update the tracker automatically\n6. If no feedback data is available, ask for it\n\n---\n\n## Anti-Patterns\n\n- Don't generate generic content ideas disconnected from actual feedback\n- Don't skip the tracker check — duplication is the #1 failure mode\n- Don't overweight old themes — rerun /analyze with fresh data regularly\n- Don't mark ideas as \"used\" automatically — only the user decides what got published\n\n#content-sop #content-strategy #flywheel #ideation\n","html":"<h1>Content Flywheel: Feedback to Fresh Ideas</h1>\n<p>The flywheel turns customer/audience feedback into content ideas that never repeat. It gets smarter with each run because it maintains a persistent tracker.</p>\n<pre><code>Customer Feedback → Theme Analysis → Content Ideas → Tracker Update\n       ↑                                                    │\n       └────────────────────────────────────────────────────┘\n</code></pre>\n<hr>\n<h2>/analyze Command</h2>\n<p><strong>Purpose:</strong> Categorize raw customer feedback into actionable themes.</p>\n<h3>Input Sources</h3>\n<ul>\n<li>Google Sheet, CSV, survey responses, community posts, support tickets, onboarding questionnaires</li>\n</ul>\n<h3>Output Format</h3>\n<pre><code>FEEDBACK ANALYSIS — [Source Name]\n─────────────────────────────────\nTotal entries analyzed: [count]\n\nTHEME RANKINGS:\nRank | Theme | Frequency | % of Total | Key Phrases Used\n1    | [theme] | [count] | [%] | \"[exact customer words]\"\n\nNOTABLE QUOTES:\n- \"[verbatim customer quote]\" — re: [theme]\n</code></pre>\n<hr>\n<h2>/flywheel Command</h2>\n<p><strong>Purpose:</strong> Generate fresh content ideas based on analyzed themes, deduped against the tracker.</p>\n<h3>Idea Generation Rules</h3>\n<ul>\n<li>Ideas must be rooted in actual customer language/pain points</li>\n<li>Each idea needs: topic, format, angle, and which theme it serves</li>\n<li>Check every idea against the tracker — if a substantially similar idea exists, skip it</li>\n<li>Prioritize themes with highest frequency but lowest existing coverage</li>\n</ul>\n<h3>Output Format</h3>\n<pre><code>CONTENT FLYWHEEL — Run [date]\n──────────────────────────────\nEMAIL NEWSLETTER IDEAS:\n1. Topic: [topic] | Theme: [theme] | Angle: [angle]\n\nYOUTUBE VIDEO IDEAS:\n1. Topic: [topic] | Theme: [theme] | Format: [tutorial/commentary] | Angle: [angle]\n\nSOCIAL MEDIA IDEAS:\n1. Topic: [topic] | Platform: [platform] | Theme: [theme] | Format: [carousel/thread/reel]\n\nNEW IDEAS GENERATED: [count]\nDUPLICATES AVOIDED: [count]\n</code></pre>\n<p><strong>Defaults:</strong> 5 email, 5 YouTube, 10 social, 5 community ideas per run.</p>\n<hr>\n<h2>/track Command</h2>\n<p><strong>Purpose:</strong> Manage the content recommendations tracker.</p>\n<h3>Tracker File: content-tracker.md</h3>\n<pre><code class=\"language-markdown\"># Content Tracker\nLast updated: [date]\nTotal ideas tracked: [count]\n\n## Generated Ideas\n| Date | Channel | Topic | Theme | Status |\n|------|---------|-------|-------|--------|\n| [date] | Email | [topic] | [theme] | new/used/skipped |\n</code></pre>\n<h3>Track Operations</h3>\n<ul>\n<li><strong>Add</strong>: After each /flywheel run, new ideas auto-append</li>\n<li><strong>Mark used</strong>: <code>track [topic] as used</code> — moves idea to Used section</li>\n<li><strong>Status check</strong>: <code>track status</code> — shows ideas per channel, used vs unused</li>\n<li><strong>Clean</strong>: <code>track clean</code> — archive ideas older than 90 days</li>\n</ul>\n<hr>\n<h2>Rules</h2>\n<ol>\n<li>NEVER generate a content idea that substantially duplicates something in the tracker</li>\n<li>Always use actual customer language in ideas, not marketing jargon</li>\n<li>The tracker file is the single source of truth</li>\n<li>Theme ranking drives idea priority</li>\n<li>Every /flywheel run MUST update the tracker automatically</li>\n<li>If no feedback data is available, ask for it</li>\n</ol>\n<hr>\n<h2>Anti-Patterns</h2>\n<ul>\n<li>Don't generate generic content ideas disconnected from actual feedback</li>\n<li>Don't skip the tracker check — duplication is the #1 failure mode</li>\n<li>Don't overweight old themes — rerun /analyze with fresh data regularly</li>\n<li>Don't mark ideas as \"used\" automatically — only the user decides what got published</li>\n</ul>\n<p>#content-sop #content-strategy #flywheel #ideation</p>\n"}