whats-nextlisted

Analyze one or more projects by identifying the top 5 user personas across the full spectrum from technical to non-technical, surfacing gaps each persona hits, and synthesizing what to build next — including breakthrough moves that elevate the project to a new level. Use this skill whenever the user asks "what should I build next", "what do my users want", "what's missing from this project", "who uses this and what do they need", or wants strategic product direction for a repo or portfolio. Trigger even if the user just says "analyze my repos" or "what should I add to X" — persona-based product thinking is almost always the right lens. Works with GitHub URLs, repo names, local project paths, plain project descriptions, or pasted user conversations (emails, Discord, reviews, support tickets).
googlarz/whats-next · ★ 1 · Web & Frontend · score 72

Install: claude install-skill googlarz/whats-next

# whats-next Strategic product direction through persona-based analysis. You identify who actually uses a project — spanning the full range from power users to casual non-technical users — give each persona a voice, surface the gaps they hit, and run five product lenses to catch what persona analysis misses. You then produce **one comprehensive list of recommendations, ranked best-first against the builder's actual goal**, each carrying its own analysis. The persona/lens machinery is the engine; the ranked recommendation list is the output. Two things make this more than a generic "what should I build" answer: it ranks every recommendation by **impact toward a confirmed goal ÷ effort** (so the #1 pick is the best move *for this builder*, not the most exciting one), and it leads with the best recommendation and its reasoning rather than burying it under persona cards. After analysis, you offer to action the top pick. ## When this skill applies - "What should I build next for [project]?" - "What do my users want?" / "What's missing?" - "Analyze my repos" / "Give me product direction on Y" - Any pasted user conversations, support emails, reviews, Discord logs ## Input gathering Accept whatever the user gives you: GitHub repo names / URLs / local paths / plain descriptions / pasted user conversations / combinations. If the user gives you nothing specific, ask: "Which project or projects? Or should I look at your GitHub profile as a whole?" **If the user pastes raw user c