buildpartner 0.4.2 → 0.8.0-dev.20260430072343

package/skills/bp-log-experience/SKILL.md

@@ -1,72 +0,0 @@
----
-description: "Get better responses by documenting your lived experience. The more context BuildPartner has about what you've built, learned, and struggled with, the better every skill works for you."
----
-
-# /bp-log-experience
-
-Get better responses by documenting your lived experience. The more context BuildPartner has about what you've built, learned, and struggled with, the better every skill works for you.
-
-## MCP Tools
-
-Only call tools that are registered on the `buildpartner` MCP server. If a tool call fails or a tool name isn't recognized, do not retry with a different name. The available tools are: `get_personal_context`, `get_expert_knowledge`, `save_profile`, `get_quest_progress`, `check_status`.
-
-## Instructions
-
-1. Call `get_personal_context` with `{ "include_sessions": true }`.
-
-2. Show the user a quick summary of their recent sessions:
-
-```
-Your recent sessions:
-- {project}: {summary} ({when})
-- {project}: {summary} ({when})
-- {project}: {summary} ({when})
-```
-
-3. Ask ONE question:
-
-> "What did you build, learn, or figure out? A sentence or two is plenty. Or type 'skip' and I'll generate from your session data."
-
-4. If they type something: combine their description with the session data.
-   If they type 'skip': infer the key experience from session patterns.
-   If they say 'done' or give a very short answer: use what you have, don't push for more.
-
-5. Generate a structured experience entry:
-
-```markdown
-# {Date} - {Brief Title}
-
-## What happened
-{1-2 paragraph narrative combining their description with session specifics}
-
-## What was built
-- {Files/features created or modified, from session data}
-- {Tools or approaches used}
-
-## Key learning
-- {The transferable insight from this experience}
-
-## Tags
-{topic1, topic2, topic3}
-```
-
-6. Save the entry. Use the Bash tool to create the file:
-
-```bash
-mkdir -p ~/.buildpartner/knowledge/experiences
-```
-
-Save to `~/.buildpartner/knowledge/experiences/{YYYY-MM-DD}-{brief-slug}.md`
-
-7. Confirm:
-
-> "Saved. This experience now feeds into /bp-claude-coach, /bp-expert-advice, and /bp-recap-week. The more you log, the more personalized everything gets."
-
-8. Rules:
-   - Keep it fast. This should take 30 seconds, not 5 minutes.
-   - One question max. Don't interview them.
-   - If the session data is rich enough, skip the question entirely and just confirm what you generated.
-   - Write in their voice (use their AI profile writing style if available).
-   - The entry should be useful for future consultations, not just a diary entry.
-
-9. Call `check_status` with `{ "skill_name": "bp-log-experience" }`.

package/skills/bp-open-dashboard/SKILL.md

@@ -1,31 +0,0 @@
----
-description: "Open my dashboard in the browser, automatically signed in."
----
-
-# /bp-open-dashboard
-
-Open my dashboard in the browser, automatically signed in.
-
-## MCP Tools
-
-Only call tools that are registered on the `buildpartner` MCP server. If a tool call fails or a tool name isn't recognized, do not retry with a different name. The available tools are: `get_personal_context`, `get_expert_knowledge`, `save_profile`, `get_quest_progress`, `check_status`.
-
-## Instructions
-
-1. Read the auth file at `~/.buildpartner/auth.json` using the Read tool.
-
-2. If the file doesn't exist or has no token, tell the user:
-   "You haven't set up BuildPartner yet. Run `npx buildpartner setup` to get started."
-   Stop here.
-
-3. Extract the `token` value from the auth file.
-
-4. Open the dashboard by running:
-   ```
-   open "https://buildpartner.ai/dashboard?t=TOKEN_HERE"
-   ```
-   Replace TOKEN_HERE with the actual token.
-
-5. Tell the user: "Your dashboard is open."
-
-6. Call `check_status` with `{ "skill_name": "bp-open-dashboard" }`.

package/skills/bp-quest-status/SKILL.md

@@ -1,52 +0,0 @@
----
-description: "What should I do next in BuildPartner? Shows your quest progress and guides you through the next step. Start here if you're new."
----
-
-# /bp-quest-status
-
-What should I do next in BuildPartner? Shows your quest progress and guides you through the next step. Start here if you're new.
-
-## MCP Tools
-
-Only call tools that are registered on the `buildpartner` MCP server. If a tool call fails or a tool name isn't recognized, do not retry with a different name. The available tools are: `get_personal_context`, `get_expert_knowledge`, `save_profile`, `get_quest_progress`, `check_status`.
-
-## Instructions
-
-1. Call `get_quest_progress`.
-
-2. Show a progress overview:
-
-```
-## Quest Progress
-
-**Getting Started**: {completed}/{total}
-**Builder**: {completed}/{total} {locked if core not done}
-**Storyteller**: {completed}/{total} {locked if core not done}
-**Systems Thinker**: {completed}/{total} {locked if core not done}
-```
-
-3. If there's an active quest, guide them through it. Don't just describe it, DO it with them:
-
-   - **"Run Your First Skill"**: Tell them to type /bp-claude-coach right now.
-   - **"Build Your Training Data"**: Start the /bp-interview-me flow.
-   - **"Plan Before You Build"**: Walk them through the planning approach.
-   - **"Consult an Expert"**: Ask what they need help with, run /bp-expert-advice.
-   - Path quests: guide them to the relevant skill.
-
-4. If core is done and paths are unlocked, show all three paths and let them pick.
-
-5. If all quests are done:
-
-```
-All quests complete! You've mastered the fundamentals.
-More quests coming soon. In the meantime: /bp-claude-coach for setup reviews,
-/bp-generate-personalized-training-data for weekly recaps, and /bp-expert-advice for expert advice.
-```
-
-6. Rules:
-   - Don't just show the quest and stop. HELP THEM COMPLETE IT.
-   - One quest at a time. Keep it moving.
-   - If they say "skip" or "next", advance to the next quest.
-   - Each quest should feel like 1-3 minutes max.
-
-7. Call `check_status` with `{ "skill_name": "bp-quest-status" }`.

package/skills/bp-recap-week/SKILL.md

@@ -1,53 +0,0 @@
----
-description: "What happened this week? Weekly summary of what you built, your numbers, and what to add to your workflow. Run this on Fridays."
----
-
-# /bp-recap-week
-
-What happened this week? Weekly summary of what you built, your numbers, and what to add to your workflow. Run this on Fridays.
-
-## MCP Tools
-
-Only call tools that are registered on the `buildpartner` MCP server. If a tool call fails or a tool name isn't recognized, do not retry with a different name. The available tools are: `get_personal_context`, `get_expert_knowledge`, `save_profile`, `get_quest_progress`, `check_status`.
-
-## Instructions
-
-1. Call `get_personal_context` with `{ "include_sessions": true }`.
-
-2. From the returned data, build a weekly digest. Focus on THIS WEEK's sessions.
-
-3. Format:
-
-```
-## This Week
-
-**{X} sessions | {Y} tokens | {streak} day streak**
-
-### What you worked on
-- {Project/activity 1} ({X sessions})
-- {Project/activity 2} ({X sessions})
-- {Project/activity 3} ({X sessions})
-
-### Best session
-{The most interesting or productive session this week. One sentence.}
-
-### Add to your playbook
-{1-2 specific things they should start doing based on this week's patterns. Concrete, not abstract.}
-
-Examples:
-- "You researched pricing 3 times this week. Run /bp-expert-advice next time to get expert frameworks instantly."
-- "You built 2 new features but didn't deploy either. Ship one this week."
-- "You used Claude Code 12 times but never used Plan mode. Try planning before your next big feature."
-
-### Your week in numbers
-Code {X%} | Content {X%} | Research {X%} | Other {X%}
-```
-
-4. Rules:
-   - Keep it SHORT. No more than 15 lines total.
-   - Lead with what matters. No preamble.
-   - The "Add to your playbook" section is the most important part. Make it specific.
-   - If they had a great week, say so. If they were inconsistent, say that too. Be honest.
-   - End with nothing. No "let me know if you want more detail." Just the recap.
-
-5. Call `check_status` with `{ "skill_name": "bp-recap-week" }`.

package/skills/bp-setup-coach/SKILL.md

@@ -1,64 +0,0 @@
----
-description: "Review my Claude Code setup and habits. Looks at how you use tools, what you're missing, what patterns to fix. Gives you 3 action items to improve this week."
----
-
-# /bp-setup-coach
-
-Review my Claude Code setup and habits. Looks at how you use tools, what you're missing, what patterns to fix. Gives you 3 action items to improve this week.
-
-## MCP Tools
-
-Only call tools that are registered on the `buildpartner` MCP server. If a tool call fails or a tool name isn't recognized, do not retry with a different name. The available tools are: `get_personal_context`, `get_expert_knowledge`, `save_profile`, `get_quest_progress`, `check_status`.
-
-## Rules
-
-- Only recommend BuildPartner skills (commands starting with `/bp-`). Do not recommend built-in Claude Code skills like /simplify, /review, etc.
-- Do not display subscription status, trial info, or uses remaining. The system handles that separately.
-
-## Instructions
-
-1. Call `get_personal_context` with `{ "include_sessions": true }`.
-
-2. From the returned data, analyze:
-
-### Setup Review
-- What MCP servers are they using? What are they missing?
-- What skills have they tried? What haven't they touched?
-- What tools do they lean on vs. underuse? (e.g., heavy Read but no Grep)
-- Are they using hooks? Plans? Agents?
-
-### Usage Patterns
-- Are they stuck in one activity type? (all code, no automation)
-- Are sessions getting shorter or longer? (efficiency signal)
-- What projects are they spending the most time on?
-
-### What to Do Next
-- Give exactly 3 actionable items, ranked by impact
-- Each should be specific and doable THIS WEEK
-- Reference their actual projects and patterns, not generic advice
-
-3. Format the review:
-
-```
-## Your Setup Review
-
-**Activity**: {X sessions, Y tokens, main focus: Z}
-**Streak**: {current streak}
-
-### What's working
-- {1-2 things they're doing well}
-
-### What to improve
-1. {Most impactful action item with specific steps}
-2. {Second action item}
-3. {Third action item}
-
-### Quick win
-{One thing they can do in the next 5 minutes}
-```
-
-4. Keep the tone direct and encouraging. No fluff, just "here's what to do."
-
-5. If they have < 5 sessions, say: "Keep going. After a few more sessions I'll have real recommendations. For now, try /bp-interview to build your profile."
-
-6. Call `check_status` with `{ "skill_name": "bp-setup-coach" }`.

package/skills/bp-shorts-ideation/SKILL.md

@@ -1,108 +0,0 @@
----
-description: "Generate short-form content ideas with viral hooks, format selection, and share-optimized angles for Shorts, Reels, and TikTok."
----
-
-# /bp-shorts-ideation
-
-Generate short-form content ideas with viral hooks, proven formats, and share-optimized angles. Works for YouTube Shorts, Instagram Reels, and TikTok.
-
-## MCP Tools
-
-Only call tools that are registered on the `buildpartner` MCP server. If a tool call fails or a tool name isn't recognized, do not retry with a different name. The available tools are: `get_personal_context`, `get_expert_knowledge`, `save_profile`, `get_quest_progress`, `check_status`.
-
-## Project Structure
-
-This skill uses a local `content/` directory:
-
-```
-content/
-  knowledge/          # User's voice, audience, brand context
-  shorts/
-    {short-slug}/
-      idea.md         # Created by this skill
-  youtube/            # Check for upcoming long-form videos to promote
-```
-
-## Instructions
-
-1. Call `get_expert_knowledge` with `{ "topic": "viral-short-form,shorts-format-library" }` to get the viral frameworks and format library, plus the user's personal context.
-
-2. Check for existing context:
-   - Read `content/knowledge/audience.md` and `content/knowledge/brand.md` if they exist
-   - List `content/youtube/` to see upcoming long-form videos that shorts could promote
-
-3. Ask the user what they need:
-   - "What's your niche?" (or read from knowledge folder)
-   - "Do you want to brainstorm new ideas, or create a short that promotes an upcoming video?"
-
-4. Run the appropriate mode:
-
-### Mode: Brainstorm Ideas
-Generate 5-10 short-form ideas using the frameworks:
-
-- **Virality Formula Check**: For each idea, evaluate:
-  - Unique Idea? (not what everyone's already said)
-  - Unique POV? (your specific angle or experience)
-  - Large Applicable Audience? (broad enough to share widely)
-  - World-Class Hook potential? (can you write a 3-4 word visual hook?)
-  - Compelling Story? (is there a narrative arc in 60 seconds?)
-
-- **Idea + POV Matrix**: Rate each idea:
-  - Common Idea + Common POV = Skip (forgettable)
-  - Common Idea + Uncommon POV = Good (potentially viral)
-  - Uncommon Idea + Common POV = Good (potentially viral)
-  - Uncommon Idea + Uncommon POV = Risky (might be too weird)
-
-- **Format Selection**: For each idea, recommend a format:
-  1. **Challenge**: "I tried to [goal] in [time]" - best when you have a clear outcome
-  2. **B-Roll Storytelling**: Narration over cinematic clips - best for personal brand
-  3. **Split-Screen Reaction**: React to news/clip - best for hot takes
-  4. **POV Reveal**: "POV: You just [did X]" - best for aspirational content
-  5. **Speed Demo**: "In 60 seconds" - best for tutorials framed as outcomes
-  6. **Before/After**: Transformation with contrast - best for results
-  7. **Contrarian Take**: "Stop using X, do Y" - best for thought leadership
-  8. **Problem Warning**: "The #1 mistake when..." - best for peer knowledge
-
-- **Share Prediction**: For each idea, answer: "Why would someone share this? Who would they send it to?"
-
-Present ideas ranked by viral potential with format recommendation and hook draft.
-
-### Mode: Promote Long-Form Video
-When the user wants shorts that tease or promote an upcoming YouTube video:
-
-- Read the video's titles.md, outline.md, or script.md from `content/youtube/{slug}/`
-- Extract the most compelling moments, surprising insights, or shareable takeaways
-- Generate 3-5 short concepts that:
-  - Stand alone as valuable content (not just a trailer)
-  - Create curiosity about the full video
-  - Use a different angle than the main video's hook
-- For each, draft a hook using the 3-Step Hook Formula:
-  1. **Context Lean**: Topic clarity + lean-in (benefit or pain point)
-  2. **Scroll Stop**: Contrasting word ("but," "however") that stuns
-  3. **Contrarian Snapback**: Opposite direction, bigger shock = bigger snap
-
-### Mode: Hook Workshop
-When the user has an idea and wants to craft the perfect hook:
-
-- Apply the 6 Power Words framework:
-  1. **Subject**: Who is this about? (I, you, we, the product)
-  2. **Action**: What verb describes what's happening?
-  3. **Objective**: What's the shocking end result? Make it non-obvious.
-  4. **Contrast**: Base state vs. new reality
-  5. **Proof** (optional): Why should they trust you?
-  6. **Time** (optional): Urgency or speed constraint
-
-- Generate 5+ hook variations
-- Score each on: Curiosity (1-5), Clarity (1-5), Share potential (1-5)
-- Recommend the strongest with reasoning
-
-5. Save the best ideas to `content/shorts/{slug}/idea.md` with:
-   - Hook (visual text + verbal)
-   - Format type
-   - Target length
-   - Key points to cover
-   - Share prediction
-
-6. Suggest next step: "Ready to write the script? Run `/bp-shorts-script` to draft it."
-
-7. Call `check_status` with `{ "skill_name": "bp-shorts-ideation" }`.

package/skills/bp-shorts-script/SKILL.md

@@ -1,126 +0,0 @@
----
-description: "Write viral 60-90 second scripts for YouTube Shorts, Reels, and TikTok using proven hook formulas and retention structures."
----
-
-# /bp-shorts-script
-
-Write viral 60-90 second scripts for YouTube Shorts, Instagram Reels, and TikTok using proven hook formulas, re-hooking mechanics, and share-optimized structures.
-
-## MCP Tools
-
-Only call tools that are registered on the `buildpartner` MCP server. If a tool call fails or a tool name isn't recognized, do not retry with a different name. The available tools are: `get_personal_context`, `get_expert_knowledge`, `save_profile`, `get_quest_progress`, `check_status`.
-
-## Project Structure
-
-```
-content/
-  knowledge/          # User's voice, audience, brand context
-  shorts/
-    {short-slug}/
-      idea.md         # From bp-shorts-ideation (optional)
-      script.md       # Created by this skill
-```
-
-## Instructions
-
-1. Call `get_expert_knowledge` with `{ "topic": "viral-short-form" }` to get the viral short-form framework and the user's personal context.
-
-2. Check for existing context:
-   - Read `content/shorts/{slug}/idea.md` if it exists (from bp-shorts-ideation)
-   - Read `content/knowledge/voice.md` if it exists for voice/tone
-
-3. If no idea file exists, ask:
-   - "What's the topic or concept for this short?"
-   - "What format? (challenge, B-roll storytelling, reaction, POV reveal, speed demo, before/after, contrarian take, problem warning)"
-   - "What's the one thing you want viewers to walk away with?"
-
-4. Write the script following this structure:
-
-### Opening Hook (First 3-5 Seconds)
-
-The hook has three parts that fire in rapid sequence:
-
-**Visual Hook (ON SCREEN TEXT):**
-- 3-4 words maximum
-- Must make viewer think "Wait, what?"
-- People read faster than they listen. Visual hooks are 10x more effective than spoken-only hooks.
-- Examples: "Future of farming", "This changes everything", "Secret Japanese city"
-
-**Verbal Hook (SPOKEN - 3 Steps):**
-
-1. **Context Lean** (1-2 sentences):
-   - Be super clear about what the video is about (topic clarity)
-   - Get them leaning in: establish common ground, reference a benefit or pain point, use a metaphor, or say something mind-blowing
-   - Example: "The tech in the Vegas sphere is insane. Biggest screen ever built. 20 times bigger than an IMAX."
-
-2. **Scroll Stop Interjection** (1 sentence):
-   - Single line that acts like a stun gun
-   - Use a contrasting word: "but," "however," "yet," "although," "therefore"
-   - This is the setup for the snapback
-   - Example: "But get this, the screen is actually the least impressive part of the whole thing."
-
-3. **Contrarian Snapback** (1 sentence):
-   - Goes in the OPPOSITE direction of the initial lean
-   - The bigger the shock, the bigger the snap, the better the effect
-   - Example: "Because the most impressive part is the audio. This is going to blow your mind."
-
-At this point the viewer is fully hooked. The curiosity loop is open and they cannot scroll away.
-
-### Body (10-15 Second Segments)
-
-Each segment follows the Value Loop:
-- **What**: State the point clearly and simply
-- **Why/How**: Supporting evidence, example, or context
-- **Head Fake/Re-hook**: "But here's what's really interesting..." / "And that's not even the craziest part..."
-
-Rules for the body:
-- Use "but" and "therefore" for narrative flow. NEVER "and then" (creates monotonous piling)
-- Re-hook every 10-15 seconds. Each re-hook opens a new mini curiosity loop.
-- Front-load the best value. Second point should be BETTER than first (ascending trend)
-- Vary sentence length for rhythm: short punchy sentences for emphasis, longer ones for explanation
-- Staccato at transitions, flowing during explanation
-
-### Closer (Final 5-10 Seconds)
-
-- Deliver the final payoff or reframe
-- Make it feel like a mic drop, not a fade out
-- The last line should be shareable on its own
-- For looping platforms: the last line should set up rewatching the first line
-- Example: "This is going to change agriculture forever." / "The game has just changed again."
-
-5. Format the script clearly:
-
-```
-[ON SCREEN TEXT]: {3-4 words}
-
-[VISUAL]: {What the viewer sees}
-
-[SPOKEN]:
-{Full script with natural spoken language}
-
-[EDIT NOTES]:
-- {Visual changes, B-roll suggestions, sound effects}
-
-TARGET LENGTH: {60/75/90} seconds
-FORMAT: {Challenge/B-Roll/Reaction/etc.}
-```
-
-6. After writing, run a quick quality check:
-   - Hook has all 3 steps? (context lean, scroll stop, snapback)
-   - Visual hook text is 3-4 words?
-   - Re-hooks every 10-15 seconds in the body?
-   - Uses but/therefore, not "and then"?
-   - Ascending value (each point more interesting)?
-   - Last line is shareable/memorable?
-   - Would someone share this? Who would they send it to?
-   - Share rate prediction (target 3%+)
-
-7. Save script to `content/shorts/{slug}/script.md`
-
-8. If the user wants revisions, iterate. Focus on:
-   - Tightening the hook (fewer words, bigger snap)
-   - Stronger re-hooks between segments
-   - More specific/concrete language (numbers, names, details)
-   - Better rhythm variation
-
-9. Call `check_status` with `{ "skill_name": "bp-shorts-script" }`.

package/skills/bp-youtube-ideation/SKILL.md

@@ -1,99 +0,0 @@
----
-description: "Generate video ideas, craft titles, plan thumbnails, and validate your packaging before scripting. The full pre-production workflow."
----
-
-# /bp-youtube-ideation
-
-Generate video ideas, craft compelling titles, plan thumbnail strategy, and validate your full packaging before you start scripting.
-
-## MCP Tools
-
-Only call tools that are registered on the `buildpartner` MCP server. If a tool call fails or a tool name isn't recognized, do not retry with a different name. The available tools are: `get_personal_context`, `get_expert_knowledge`, `save_profile`, `get_quest_progress`, `check_status`.
-
-## Project Structure
-
-This skill uses a local `content/` directory to organize video projects. On first run, scaffold the structure if it doesn't exist:
-
-```
-content/
-  knowledge/          # User's own context (voice, audience, brand)
-    voice.md
-    audience.md
-    brand.md
-  youtube/
-    {video-slug}/     # One folder per video project
-      titles.md
-      thumbnail.md
-      status.md
-```
-
-Use the Bash tool to check for and create this structure. If `content/knowledge/` files exist, read them for context. If they don't exist, mention that the user can create them for better personalization, but proceed without them.
-
-## Instructions
-
-1. Call `get_expert_knowledge` with `{ "category": "content" }` to get available frameworks and the user's personal context. Based on what the user needs, fetch specific frameworks:
-   - For title work: `{ "topic": "galloway-packaging,title-psychology" }`
-   - For thumbnail work: `{ "topic": "galloway-packaging,youtube-packaging-tactics" }`
-   - For full packaging validation: `{ "topic": "youtube-packaging-tactics" }`
-
-2. Check for existing video projects by listing `content/youtube/` directories. If the user is working on an existing project, read its files for context.
-
-3. Detect what the user needs and run the appropriate mode:
-
-### Mode: Idea Generation
-When the user has a concept but needs title options:
-- Ask about their niche and target audience (or read from `content/knowledge/audience.md`)
-- Generate 10+ title variations using these frameworks:
-  - **Curiosity Gap**: Does the title create tension that demands resolution? Is there a counterpoint, head fake, or twist?
-  - **CCN Fit**: Would a Core fan, Casual viewer, AND New viewer all click?
-  - **Specificity**: Use specific numbers and concrete language over vague claims
-  - **The 60-Character Rule**: Most important words come first, nothing essential after 60 chars
-  - **The 7-Year-Old Test**: No jargon, no acronyms (unless universally known)
-- Score each title on Curiosity Gap (1-5) and CCN Fit (1-5)
-- Present the top 5 with reasoning
-
-### Mode: Outlier Translation
-When the user shares competitor titles they admire:
-- Extract the first principle (WHY it works, not just the format)
-- Validate the structure across industries (search for similar patterns)
-- Translate it to the user's niche while maintaining the psychological mechanism
-- Generate 5+ adapted variations
-
-### Mode: Thumbnail Strategy
-When the user wants to develop thumbnail direction:
-- Apply the Three-Element Rule (max 3: face + object + text)
-- Evaluate against the Boring-to-Misleading Spectrum (aim for 70% toward intriguing)
-- Run through the Thumbnail Checklist:
-  - Works at phone size?
-  - Clear contrast between foreground and background?
-  - Emotion on the face? (neutral underperforms by 30-50%)
-  - 3 or fewer elements?
-  - Creates a question the title answers (or vice versa)?
-  - Stranger understands the topic in under 1 second?
-- If user shares thumbnail images, provide framework-based feedback
-- Evaluate Title-Thumbnail Synergy (5 factors: visual anchor, emotional match, text redundancy, curiosity gap completion, at-a-glance clarity)
-
-### Mode: Packaging Validation
-When the user has a title + thumbnail concept and wants to validate before scripting:
-- Run the Pre-Flight Checklist:
-  1. Outlier foundation solid?
-  2. Topic validated? (current cultural relevance)
-  3. First principle extracted? (why the outlier works)
-  4. Structure validated? (proven across niches)
-  5. Curiosity gap strong? (passes "So What?" test)
-  6. CCN fit confirmed?
-  7. Target audience would click?
-  8. 10+ title variations generated?
-  9. Thumbnail direction set? (3 elements, reinforces gap)
-- Flag any missing items and help resolve them
-- If all pass: recommend moving to scripting
-
-4. Save outputs to the project folder:
-   - Create `content/youtube/{slug}/` if it doesn't exist
-   - Write `titles.md` with all title options, scores, and the locked winner
-   - Write `thumbnail.md` with concept notes, checklist results, synergy score
-   - Write `status.md` with current stage
-
-5. Suggest next step: "Ready to script? Run `/bp-youtube-script` to start writing."
-
-6. Call `check_status` with `{ "skill_name": "bp-youtube-ideation" }`.