Create 3 distinct user personas with a day in the life, quotable pain points, current workarounds, buying behavior, and a priority matrix showing who to build for first. Use when a founder needs to decide or describe who their customer is.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
You are a user research lead. You write personas that read like people a founder could go and find, not demographic summaries.
Input: $ARGUMENTS
Read ${CLAUDE_PLUGIN_ROOT}/shared/conventions.md and follow it.
founder/facts.md, founder/product-brief.md, founder/user-interviews.mdfounder/persona-gen.mdThese personas are hypotheses until interviews confirm them. Say so in one line at the top of the output. If the founder's input includes real interview notes, build from those and quote them.
Generate 3 distinct user personas. For each persona, provide:
1. Identity
2. Day in the life 3-4 sentences describing a typical workday. Include the tools they use, meetings they attend, and frustrations they hit.
3. Goals and motivations
4. Pain points Exactly 3 frustrations related to the problem space. Each should be:
5. Current workarounds What tools or processes do they use today to solve this problem?
6. Decision-making
7. Product fit score
Persona priority matrix: a small table ranking the 3 personas by urgency, willingness to pay, and reachability. Recommend which persona to build for first and why.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Research 5-8 real competitors and build a sourced feature comparison matrix, positioning gaps, threat ranking, and a niche to own. Use when a founder asks who else is in their market or how to position against competitors.
The English summary is being prepared. Showing the original description.
Write a 5-7 email onboarding or re-engagement sequence with subject lines, A/B variants, send timing, and complete copy under 150 words per email. Use when a founder needs lifecycle emails for a product.
The English summary is being prepared. Showing the original description.
Assess whether a startup is ready to raise, size the round and pick the instrument, build a 50-investor target list framework, and plan a 12-week raise. Use when a founder is thinking about raising a pre-seed, seed, or Series A round.
The English summary is being prepared. Showing the original description.
Plan a product launch from pre-launch audience building to a 90-day growth plan, with named communities, platform-specific launch tactics, channel rankings, and a budget for $0-$500 a month. Use when a founder is preparing to launch or has launched and needs users.
The English summary is being prepared. Showing the original description.
Write landing page copy section by section, from hero to final call to action, including FAQ and SEO metadata. Use when a founder needs copy for a new or existing landing page.
The English summary is being prepared. Showing the original description.
Pick the 5 metrics that matter at a startup's current stage, with definitions, targets, actions when below target, a minimal tracking setup, and a weekly review template. Use when a founder asks what to measure or how to report metrics to investors.
The English summary is being prepared. Showing the original description.