5a40b6fdc4
* feat: add OAC package refactor context file - Add comprehensive feature context for OAC package refactor - Document multi-IDE support architecture - Define community component registry (shadcn-like) - Outline flexible configuration system - Detail context file location flexibility - Define 7-phase implementation plan - Include CLI commands reference - Add community publishing guidelines * docs: add OAC refactor quick start guide - Add quick reference for Phase 1 implementation - Include project structure and file locations - Document configuration schema and defaults - Add testing strategy and validation steps - Include development workflow - Reference all related resources * feat: add critical user approval and context resolution systems CRITICAL FEATURES ADDED: 1. User Approval & YOLO Mode - Default: Interactive approval for all file operations - Always asks: local vs global install - Confirms before overwriting files - Shows diffs and file details - YOLO mode (--yolo): Skip confirmations, auto-resolve, report at end - Conflict strategies: ask, skip, overwrite, backup, yolo - Safety: backups, git detection, rollback support, audit log 2. Context Resolution System - Layered context resolution (6 priority levels) - Project override (.oac/context/) - highest priority - Project context (.opencode/context/) - IDE context (.cursor/, .claude/) - Project docs (docs/) - User global (~/.config/oac/context/) - OAC official (~/.config/oac/official/) - lowest priority - Smart resolution based on agent location (global vs local) - preferLocal config option - Context merging strategies - CLI commands for context management - Environment variable overrides - Validation and fallback support 3. Enhanced CLI Commands - All commands support --yolo, --dry-run, --local, --global - Context management: resolve, list, validate, override, sync - Detailed help and examples - Global flags for all commands This ensures users maintain full control over their projects while supporting both local and global workflows with intelligent context resolution. * feat: add component creation wizard and IDE feature parity system NEW FEATURES: 1. Interactive Component Creation - oac create (interactive wizard) - Create agents, skills, contexts, plugins, commands, tools - Template system for scaffolding - Auto-generate tests and boilerplate - Multi-IDE compatibility selection - Size optimization options 2. IDE Feature Parity & Capacity Management (CRITICAL) - Feature support matrix for all IDEs - OpenCode/Claude Code: Full support (all features) - Cursor: Limited (single file, no skills/plugins, 100KB limit) - Windsurf: Partial support - Adaptive installation based on IDE capabilities - Automatic feature filtering and warnings - Component merging for single-file IDEs (Cursor) - Capacity warnings and optimization - IDE-specific profiles 3. Enhanced CLI Commands - oac create [type] - Component creation wizard - oac templates - List available templates - oac compatibility <ide> - Check IDE compatibility - oac ides - List supported IDEs with features - oac ide info <ide> - Show IDE capabilities - oac optimize --for <ide> - Optimize for specific IDE - oac validate --ide <ide> - Validate IDE installation 4. Smart Installation - Detects IDE capabilities - Warns about unsupported features - Auto-filters components - Merges agents for Cursor - Embeds contexts for limited IDEs - Monitors file size limits - Suggests IDE-specific profiles This ensures users can easily create components and OAC gracefully handles different IDE capabilities with clear warnings and automatic optimization. * docs: add critical feedback from parallel agent review CRITICAL FINDINGS: Security Gaps (BLOCKER): - No component signing or verification - No malware/secret scanning - No permission system - Action: Add security layer in Phase 1 Missing Features (CRITICAL): - Discovery (browse, search, trending) - Lockfile for reproducibility - Version conflict management - Interactive onboarding - Progress indicators - Auto-detection for local/global Approaches to Rethink: - Context merging → Use composition instead - Always asking local/global → Auto-detect with smart defaults - Cursor agent merging → Router pattern instead Repository Structure: - Recommended: Monorepo with pnpm workspaces - Packages: core, adapters, registry, security, cli - Benefits: Shared deps, atomic commits, easier testing Community Workflow: - Component submission process - Automated security scanning - Manual review for verification - Moderation system Updated Priorities: - v1.0 MVP: Add 6 critical features (discovery, lockfile, security, etc.) - v1.1: Plugin system, workspace support, marketplace - v2.0: Enterprise features Documentation Needs: - Quick Start (5-minute guide) - CLI Reference (auto-generated) - Recipes/Cookbook - Component Creation Guide - Migration Guide Overall: Plan is 80% solid, needs 20% critical additions before Phase 1 * feat: add comprehensive agent customization and preset system CRITICAL FEATURE: Agent Customization & Personal Presets Problem: - Users want to customize agent prompts for their workflow - Users want to save personal configurations - Updates shouldn't overwrite customizations - Need easy way to view and edit agents Solution: Multi-Layer Customization System Layer 1: View Agent Configuration - oac show agent:openagent (view in pager) - oac edit agent:openagent (open in editor) - oac config show agent:openagent (config only) - oac export agent:openagent (export to file) Layer 2: Create Personal Preset - oac customize agent:openagent (create preset) - Copies to ~/.config/oac/presets/agents/ - Links to base agent for updates - Tracks customizations in metadata Layer 3: Edit Personal Preset - oac edit preset:my-openagent (edit in $EDITOR) - oac customize preset:my-openagent --interactive (wizard) - Auto-backup on save - Track modification history Layer 4: Use Personal Preset - oac use preset:my-openagent (activate) - oac use preset:my-openagent --global (set default) - oac presets list --active (show active) - Switch between presets and base agents Layer 5: Update Management (CRITICAL) - Smart update detection for base agents - Merge strategies: manual, auto-base, auto-merge, locked - Conflict resolution with user prompts - Show diffs before merging - Auto-backup before updates - Preserve user customizations by default Layer 6: Preset Sharing - oac export preset:my-openagent (export) - oac import preset ./preset.md (import) - oac share preset:my-openagent (share with team) - oac publish preset:my-openagent (publish to community) Layer 7: In-Place Editing (Advanced) - oac edit agent:openagent --in-place (risky, warns user) - Creates backup before editing - Warns that updates will overwrite - Recommends preset creation instead Update Strategies: - manual: User reviews every update - auto-base: Auto-update base, keep preset unchanged - auto-merge: Auto-merge, prompt on conflicts - locked: Never update base Configuration: - Preset metadata (.presets.json) - Update strategies per preset - Merge conflict resolution - Backup management - Warning preferences Edge Cases Handled: - In-place edits before updates - Multiple updates behind - Multiple presets for same base - Preset conflicts with IDE - Deleted base agent Best Practices: - Always create presets (safest) - Document customizations - Review updates before merging - Keep backups - Use descriptive names This ensures users can safely customize agents without fear of losing changes on updates, while still benefiting from base agent improvements. * docs: complete comprehensive user scenario analysis (16,014 lines) PLANNING PHASE COMPLETE: Documents Created (9 files, 400KB): - 00-INDEX.md (388 lines) - Planning index and overview - 01-main-plan.md (2,338 lines) - Complete feature specification - 02-quickstart-guide.md (450 lines) - Phase 1 quick reference - 03-critical-feedback.md (599 lines) - Parallel agent review - 04-solo-developer-scenarios.md (2,106 lines) - Individual workflows - 05-team-lead-scenarios.md (3,977 lines) - Team collaboration - 07-content-creator-scenarios.md (2,581 lines) - Non-technical users - 08-open-source-maintainer-scenarios.md (3,575 lines) - Community management - 09-SYNTHESIS.md (1,000+ lines) - Consolidated findings User Personas Analyzed (4/5): ✅ Solo Developer (Primary - 40% market) ✅ Team Lead (Secondary - 30% market) ✅ Content Creator (Emerging - 20% market) ✅ Open Source Maintainer (Future - 5% market) ⏸️ Enterprise Admin (Deferred to v2.0 - 5% market) Key Findings: Solo Developer (Primary User): - Setup must be < 2 minutes or they skip - Preview before committing (try mode) - Safe customization (presets) - Easy rollback/undo - Zero docs reading to start Team Lead (Secondary User): - Lockfile is non-negotiable (oac.lock) - Team configuration (oac-team.json) - Compliance monitoring (90%+ required) - Onboarding: 4-8 hours → 15 minutes (96% reduction) - Staged rollouts for updates Content Creator (Emerging - 20% market): - CLI is intimidating (need GUI wrapper) - Plain language mode (no jargon) - Visual undo (version history) - Templates and examples - Guided setup Open Source Maintainer (Future): - Security scanning pipeline (ClamAV + gitleaks) - Quality gates (70% test coverage) - Review/approval workflow - Deprecation workflow - Sustainability model Critical Additions to MVP: 1. Interactive onboarding wizard (all personas) 2. TUI browser with preview (solo dev, team lead) 3. Lockfile (oac.lock) (team lead) 4. Security scanning (all personas) 5. Try mode (solo dev) 6. Team configuration (team lead) 7. oac doctor health checks (solo dev) 8. Quality gates (maintainer) Market Opportunity: - v1.0: 70% market (solo + team) - v1.1: 90% market (+ content creators with GUI) - v2.0: 100% market (+ enterprise) Recommended Changes: - Expand MVP scope (+2 weeks, 9 weeks total) - Plan v1.1 for content creators (GUI wrapper) - Defer enterprise features to v2.0 - Build community features early (trust) Status: Ready to finalize plan and start implementation Confidence: Very High (95%+) Risk: Low (comprehensive analysis complete) * docs: add comprehensive final review of OAC planning FINAL REVIEW COMPLETE: Overall Assessment: CONDITIONAL GO ✅⚠️ Confidence Level: 85% (High, with conditions) Success Probability: 75% (with modifications) Key Strengths: ✅ Exceptional user research (16,000+ lines, 4 personas) ✅ Clear technical architecture (monorepo, TypeScript, Zod) ✅ Security-first mindset (signing, scanning, verification) ✅ Realistic scope management (v1.0 vs v1.1 vs v2.0) ✅ Comprehensive feature coverage Critical Gaps Identified: ❌ Discovery/Onboarding not in Phase 1 (but P0 in scenarios) ❌ Lockfile not in Phase 2 (but critical for teams) ❌ Security Pipeline not detailed in phases ❌ Progress UI not in Phase 1 (but needed for UX) ❌ Auto-detection not in Phase 1 (but reduces friction) Conditions for Go: 1. Add discovery/onboarding to Phase 1 (+3 days) 2. Add lockfile to Phase 2 (+2 days) 3. Add security pipeline to Phase 1 (+2 days) 4. Add progress UI to Phase 1 (+1 day) 5. Revise timeline: 7 weeks → 9 weeks Critical Action Items (6 days before Phase 1): 1. Add missing features to phases (2 days) 2. Define acceptance criteria (1 day) 3. Define testing strategy (1 day) 4. Design security pipeline (1 day) 5. Create monorepo structure (1 day) Top Risks: 🔴 Timeline Slip (70% probability, high impact) 🟡 Scope Creep (50% probability, high impact) 🟡 Context Merging Complexity (60% probability, medium impact) Recommendation: PROCEED WITH MODIFICATIONS - Complete 6 days of prerequisite work - Extend timeline to 9 weeks - Add missing features to phases - Define acceptance criteria and testing strategy Status: READY TO IMPLEMENT (with modifications) Next Steps: Complete prerequisites → Setup monorepo → Start Phase 1 * feat(context): Standardize context system with navigation, frontmatter, and MVI compliance - Add 77 navigation.md files across all context categories for token-efficient discovery - Standardize frontmatter format on 198+ context files (HTML comment format, 2026-02-15) - Compress 3 oversized guide files applying MVI principle (802 lines removed, 63% reduction) - Add context system analysis and planning artifacts in context-findings/ - Add task management enhancements (stage orchestration, planning subagents) - Document compression techniques and future optimization recommendations Context System Improvements: - All active directories now have navigation.md (200-300 tokens each) - 100% frontmatter compliance with priority/version/date metadata - Improved scannability through MVI compression (compact.md, organizing-context.md, creation.md) - Token efficiency increased for AI agent consumption Planning & Analysis: - Context system implementation plan and simplification analysis - ADR standard proposal and runtime permission architecture - SQLite context design for future scale (deferred until 500+ files) - Context discovery script analysis (rejected in favor of navigation-first) Task Management: - Enhanced task schema with stage orchestration support - New planning subagents (ADR, Architecture, Story Mapping, Prioritization) - Stage orchestrator for multi-stage workflow management - Session context management and lightweight handoff patterns Closes: context-simple-fixes task Ref: context-system-implementation analysis * fix: resolve markdown link validation errors in navigation files - Remove non-existent react-patterns.md link from react/navigation.md - Remove non-existent premium-dark-ui-quick-start.md link from design/navigation.md - Add skip patterns for pre-existing broken links in example/template files - Validation now passes: 215 files validated, 0 errors * fix: resolve all 119 broken markdown links across documentation - Update agent paths to new subagents structure (TestEngineer, ContextScout, etc.) - Fix animation file references (animation-ui.md → animation-components.md) - Update guide references (adding-agent.md → adding-agent-basics.md) - Convert non-existent example paths to placeholder text format - Add skip patterns for intentional example placeholders - Validation now passes: 232 files validated, 0 errors Co-authored-by: CoderAgent <coder@openagents.dev> --------- Co-authored-by: CoderAgent <coder@openagents.dev>
459 lines
9.3 KiB
Markdown
459 lines
9.3 KiB
Markdown
<!-- Context: content-creation/workflows | Priority: medium | Version: 1.0 | Updated: 2026-02-15 -->
|
|
|
|
# Content Ideas
|
|
|
|
Frameworks and techniques for generating endless content ideas and overcoming creative blocks.
|
|
|
|
---
|
|
|
|
## Ideation Frameworks
|
|
|
|
### SCAMPER Method
|
|
|
|
Apply these prompts to existing content or topics:
|
|
|
|
**S - Substitute**: What can you replace?
|
|
- "Instead of X, what if we tried Y?"
|
|
- "How would [different industry] approach this?"
|
|
|
|
**C - Combine**: What can you merge?
|
|
- "What if we combined [topic A] with [topic B]?"
|
|
- "How can we blend [format 1] and [format 2]?"
|
|
|
|
**A - Adapt**: What can you adjust?
|
|
- "How can we adapt [successful content] for [new audience]?"
|
|
- "What worked in [context A] that could work in [context B]?"
|
|
|
|
**M - Modify**: What can you change?
|
|
- "What if we made this [bigger/smaller/faster/slower]?"
|
|
- "How can we present this differently?"
|
|
|
|
**P - Put to other uses**: What else could this be?
|
|
- "Who else could benefit from this?"
|
|
- "What other problems does this solve?"
|
|
|
|
**E - Eliminate**: What can you remove?
|
|
- "What if we simplified this to just [core element]?"
|
|
- "What happens if we remove [common element]?"
|
|
|
|
**R - Reverse**: What if we flipped it?
|
|
- "What if we did the opposite?"
|
|
- "What if we started with the end?"
|
|
|
|
---
|
|
|
|
### Mind Mapping
|
|
|
|
**Process**:
|
|
1. Write main topic in center
|
|
2. Branch out with related subtopics
|
|
3. Branch further with specific ideas
|
|
4. Look for connections between branches
|
|
5. Identify content opportunities
|
|
|
|
**Example**:
|
|
```
|
|
[Content Creation]
|
|
|
|
|
+------------------+------------------+
|
|
| | |
|
|
[Writing] [Video] [Social]
|
|
| | |
|
|
+---+---+ +---+---+ +---+---+
|
|
| | | | | |
|
|
[Hooks] [SEO] [Scripts] [Editing] [Threads] [Reels]
|
|
```
|
|
|
|
---
|
|
|
|
### Question-Based Ideation
|
|
|
|
**What Questions**:
|
|
- What is [topic]?
|
|
- What are the types of [topic]?
|
|
- What mistakes do people make with [topic]?
|
|
- What's the future of [topic]?
|
|
|
|
**How Questions**:
|
|
- How to [achieve result]?
|
|
- How to [avoid problem]?
|
|
- How to [do task] faster/better/cheaper?
|
|
- How I [achieved result]?
|
|
|
|
**Why Questions**:
|
|
- Why [common belief] is wrong?
|
|
- Why [topic] matters?
|
|
- Why [approach] works better?
|
|
- Why you should [action]?
|
|
|
|
**When Questions**:
|
|
- When to [take action]?
|
|
- When to avoid [approach]?
|
|
- When is the best time to [action]?
|
|
|
|
**Who Questions**:
|
|
- Who should [take action]?
|
|
- Who is [topic] for?
|
|
- Who are the experts in [topic]?
|
|
|
|
**Where Questions**:
|
|
- Where to [find resource]?
|
|
- Where do [people] go wrong?
|
|
- Where to start with [topic]?
|
|
|
|
---
|
|
|
|
## Content Idea Sources
|
|
|
|
### 1. Audience Questions
|
|
|
|
**Where to find them**:
|
|
- Comments on your content
|
|
- DMs and emails
|
|
- Social media mentions
|
|
- Q&A platforms (Quora, Reddit)
|
|
- Community forums
|
|
- Customer support tickets
|
|
|
|
**How to use**:
|
|
- Answer questions directly
|
|
- Create comprehensive guides
|
|
- Address common misconceptions
|
|
- Bundle related questions
|
|
|
|
---
|
|
|
|
### 2. Trending Topics
|
|
|
|
**Tools**:
|
|
- Google Trends
|
|
- Twitter/X trending
|
|
- Reddit trending
|
|
- TikTok discover page
|
|
- YouTube trending
|
|
- Industry news sites
|
|
|
|
**Approach**:
|
|
- Add your unique angle
|
|
- Connect trend to your niche
|
|
- Timely response (strike while hot)
|
|
- Evergreen spin on trend
|
|
|
|
---
|
|
|
|
### 3. Competitor Content Analysis
|
|
|
|
**What to analyze**:
|
|
- Their most popular content
|
|
- Topics they cover frequently
|
|
- Gaps in their content
|
|
- Comment sections (what people want)
|
|
- Content formats they use
|
|
|
|
**How to differentiate**:
|
|
- Go deeper on the topic
|
|
- Different angle or perspective
|
|
- Better examples or data
|
|
- More actionable advice
|
|
- Different format
|
|
|
|
---
|
|
|
|
### 4. Your Own Experience
|
|
|
|
**Content from experience**:
|
|
- Lessons learned
|
|
- Mistakes made
|
|
- Experiments and results
|
|
- Behind-the-scenes
|
|
- Day-in-the-life
|
|
- Tools and processes
|
|
- Before and after
|
|
|
|
**Why it works**:
|
|
- Authentic and unique
|
|
- Builds trust
|
|
- Relatable
|
|
- Proof of expertise
|
|
|
|
---
|
|
|
|
### 5. Keyword Research
|
|
|
|
**Tools**:
|
|
- Google Keyword Planner
|
|
- Ahrefs
|
|
- SEMrush
|
|
- AnswerThePublic
|
|
- Google autocomplete
|
|
- "People also ask" boxes
|
|
|
|
**What to look for**:
|
|
- High volume, low competition
|
|
- Long-tail keywords
|
|
- Question-based keywords
|
|
- "How to" searches
|
|
- Comparison searches
|
|
|
|
---
|
|
|
|
### 6. Content Remixing
|
|
|
|
**Remix strategies**:
|
|
- Update old content with new info
|
|
- Change the format (blog → video)
|
|
- Different angle on same topic
|
|
- Combine multiple pieces
|
|
- Break down comprehensive guide
|
|
- Expand on brief mention
|
|
|
|
---
|
|
|
|
## Content Idea Templates
|
|
|
|
### List-Based Ideas
|
|
|
|
- "[Number] ways to [achieve result]"
|
|
- "[Number] mistakes to avoid with [topic]"
|
|
- "[Number] tools for [task]"
|
|
- "[Number] examples of [topic]"
|
|
- "[Number] lessons from [experience]"
|
|
- "Top [number] [things] for [audience]"
|
|
|
|
---
|
|
|
|
### How-To Ideas
|
|
|
|
- "How to [achieve result] in [timeframe]"
|
|
- "How to [task] without [common obstacle]"
|
|
- "How to [task] like [expert/pro]"
|
|
- "How I [achieved result]"
|
|
- "How to get started with [topic]"
|
|
- "How to [task] on a budget"
|
|
|
|
---
|
|
|
|
### Comparison Ideas
|
|
|
|
- "[Option A] vs [Option B]: Which is better?"
|
|
- "[Tool A] vs [Tool B]: Honest comparison"
|
|
- "[Approach A] vs [Approach B]: Pros and cons"
|
|
- "Why I switched from [A] to [B]"
|
|
- "[Topic] then vs now"
|
|
|
|
---
|
|
|
|
### Problem-Solution Ideas
|
|
|
|
- "Struggling with [problem]? Try this"
|
|
- "[Problem]? Here's why it happens"
|
|
- "The real reason you're [experiencing problem]"
|
|
- "How to fix [problem] in [timeframe]"
|
|
- "[Problem] solved: [solution]"
|
|
|
|
---
|
|
|
|
### Myth-Busting Ideas
|
|
|
|
- "[Number] myths about [topic]"
|
|
- "Why [common belief] is wrong"
|
|
- "The truth about [topic]"
|
|
- "Debunking [misconception]"
|
|
- "What nobody tells you about [topic]"
|
|
|
|
---
|
|
|
|
### Personal Story Ideas
|
|
|
|
- "How I [achieved result]"
|
|
- "I tried [thing] for [timeframe]. Here's what happened"
|
|
- "My biggest mistake with [topic]"
|
|
- "What [experience] taught me about [topic]"
|
|
- "From [starting point] to [end point]: My journey"
|
|
|
|
---
|
|
|
|
## Evergreen vs. Timely Content
|
|
|
|
### Evergreen Content
|
|
|
|
**Characteristics**:
|
|
- Stays relevant long-term
|
|
- Consistent traffic over time
|
|
- Foundational topics
|
|
- How-to guides and tutorials
|
|
|
|
**Examples**:
|
|
- "How to write a blog post"
|
|
- "Beginner's guide to [topic]"
|
|
- "Essential tools for [task]"
|
|
- "Common mistakes in [topic]"
|
|
|
|
**Benefits**:
|
|
- Long-term traffic
|
|
- Compound value
|
|
- Less frequent updates needed
|
|
- SEO value
|
|
|
|
---
|
|
|
|
### Timely Content
|
|
|
|
**Characteristics**:
|
|
- Relevant for short period
|
|
- Spike in traffic, then drops
|
|
- Trends and news
|
|
- Seasonal topics
|
|
|
|
**Examples**:
|
|
- "2024 trends in [industry]"
|
|
- "New [tool] review"
|
|
- "What [recent event] means for [audience]"
|
|
- "Holiday gift guide for [audience]"
|
|
|
|
**Benefits**:
|
|
- Captures immediate interest
|
|
- Shows you're current
|
|
- Viral potential
|
|
- Timely engagement
|
|
|
|
---
|
|
|
|
### Balanced Approach
|
|
|
|
**80/20 Rule**:
|
|
- 80% evergreen (long-term value)
|
|
- 20% timely (immediate relevance)
|
|
|
|
**Why**:
|
|
- Evergreen builds foundation
|
|
- Timely captures attention
|
|
- Balance sustains growth
|
|
|
|
---
|
|
|
|
## Overcoming Creative Blocks
|
|
|
|
### When You're Stuck
|
|
|
|
**Change your environment**:
|
|
- Go for a walk
|
|
- Work from different location
|
|
- Take a break
|
|
- Exercise
|
|
|
|
**Consume content**:
|
|
- Read in your niche
|
|
- Watch videos
|
|
- Listen to podcasts
|
|
- Browse social media
|
|
|
|
**Talk it out**:
|
|
- Discuss with colleague
|
|
- Explain topic to someone
|
|
- Voice record thoughts
|
|
- Join community discussions
|
|
|
|
**Use constraints**:
|
|
- Set a timer (10 minutes)
|
|
- Limit to 3 ideas
|
|
- Choose random topic
|
|
- Use a template
|
|
|
|
---
|
|
|
|
### Idea Generation Habits
|
|
|
|
**Daily practices**:
|
|
- Save interesting content
|
|
- Note questions you get
|
|
- Track what resonates
|
|
- Review analytics
|
|
- Engage with audience
|
|
|
|
**Weekly practices**:
|
|
- Brainstorm session (30 min)
|
|
- Review saved ideas
|
|
- Analyze top content
|
|
- Check trending topics
|
|
- Plan next week's content
|
|
|
|
**Monthly practices**:
|
|
- Content audit
|
|
- Competitor analysis
|
|
- Audience survey
|
|
- Trend research
|
|
- Strategy review
|
|
|
|
---
|
|
|
|
## Content Idea Bank
|
|
|
|
### Building Your Idea Bank
|
|
|
|
**What to capture**:
|
|
- Content ideas (topics, angles)
|
|
- Headlines and hooks
|
|
- Interesting quotes
|
|
- Data and statistics
|
|
- Examples and case studies
|
|
- Questions from audience
|
|
- Trending topics
|
|
|
|
**Where to store**:
|
|
- Note-taking app (Notion, Evernote)
|
|
- Spreadsheet
|
|
- Project management tool
|
|
- Voice memos
|
|
- Bookmarking tool
|
|
|
|
**How to organize**:
|
|
- By topic/category
|
|
- By format
|
|
- By priority
|
|
- By funnel stage
|
|
- By status (idea, in progress, published)
|
|
|
|
---
|
|
|
|
### Using Your Idea Bank
|
|
|
|
**Regular review**:
|
|
- Weekly: Review and prioritize
|
|
- Monthly: Organize and clean up
|
|
- Quarterly: Identify patterns
|
|
|
|
**When planning**:
|
|
- Pull from bank for content calendar
|
|
- Combine related ideas
|
|
- Prioritize based on goals
|
|
- Schedule creation
|
|
|
|
---
|
|
|
|
## Content Idea Checklist
|
|
|
|
Before committing to an idea, ask:
|
|
|
|
- [ ] Is this relevant to my audience?
|
|
- [ ] Can I add unique value or perspective?
|
|
- [ ] Do I have expertise or experience with this?
|
|
- [ ] Is there search demand or interest?
|
|
- [ ] Can I create this with available resources?
|
|
- [ ] Does it align with my goals?
|
|
- [ ] Is the timing right?
|
|
- [ ] Can I make it actionable?
|
|
|
|
---
|
|
|
|
## Usage
|
|
|
|
Use these frameworks when:
|
|
- Planning content calendar
|
|
- Overcoming creative blocks
|
|
- Brainstorming new topics
|
|
- Expanding content coverage
|
|
- Finding unique angles
|
|
- Building content pipeline
|
|
|
|
**Remember**: The best content ideas come from understanding your audience's needs and adding your unique perspective. Quality over quantity always wins.
|