fill-library-gaps

name	fill-library-gaps
description	Use when Daniel wants to find gaps in the My Weird Prompts episode library or surface adjacent topics to ones already covered. Triggers on phrases like "what haven't we covered", "find gaps", "adjacent topics", "what's missing", "expand the library".

Fill library gaps / find adjacent topics

Daniel's main ideation mode. The goal is to surface episode ideas that either:

1. Fill gaps — topic areas or angles under-represented in the existing library
2. Go adjacent — take an already-covered topic and suggest a sibling, sequel, inverse, or zoomed-in/zoomed-out angle

Workflow

1. Pull recent episodes via the Pinecone MCP server (pinecone in .mcp.json). Use search-records or cascading-search against the MWP episode index. If the index name isn't yet wired up, ask Daniel which index to query.
2. Cluster the results mentally by theme (history, science, tech, absurd-fictional, current-events, etc.).
3. Identify thin clusters — themes with 0–2 episodes — and propose prompts that would fit there.
4. For adjacency, pick 2–3 strong existing episodes and generate prompts that share a seed but twist the angle (e.g., same topic from a different expert's POV, the opposite stance, one layer deeper, or the same structure applied to a different domain).
5. Present suggestions grouped as:
   • Gaps — with a one-line rationale for why this fills a hole
   • Adjacent — each linked to the existing episode it riffs on

Output

Follow .claude/skills/OUTPUT_PROTOCOL.md. Save to outputs/YYYY-MM-DD/gaps-<slug>.md. For each suggestion add:

• Type: gap or adjacent
• If adjacent, a Source episode: pointer to the existing episode it riffs on.

Include Host guidance only when warranted (tonal traps, callbacks to the adjacent source, etc.).

Notes

• Don't suggest prompts that are near-duplicates of existing episodes. Check similarity via Pinecone before presenting.
• Gaps are more valuable than adjacents when the library is narrow; adjacents beat gaps when the library is already broad.