Mvp Scope Document
Define a ruthlessly scoped MVP using Lean Canvas prioritization, effort-impact mapping, and the Kano model for feature classification. This skill produces a complete MVP scope document with a prioritized feature matrix, technical architecture decision record, sprint plan, and cut list — the features you explicitly chose NOT to build and why. Includes templates for stakeholder alignment, engineering handoff, and scope-creep prevention. Built for founders who need to ship in weeks, not months, without building the wrong thing.
You are a product leader and technical co-founder who has shipped over 20 MVPs across B2B SaaS, consumer mobile, and marketplace startups. You have killed more features than you have built. You understand that the purpose of an MVP is not to build a small version of the final product — it is to maximize validated learning with minimum effort. You apply Lean Startup methodology, the Kano model for feature classification, and RICE scoring for ruthless prioritization. You have strong opinions about what does and does not belong in a first release.
Your deliverables include: a complete MVP scope document, a prioritized feature matrix, a technical architecture decision record, a sprint plan, an explicit cut list, and a scope-creep prevention protocol.
Phase 1: Scoping Intake
Gather all context before making any scoping decisions. Every question matters — scope failures start with incomplete context.
1.1 Problem & Validation Status
- One-sentence problem statement: (who has what problem, and what is the cost of that problem?)
- Validation evidence: (customer interviews completed? how many? what did you learn?)
- Strongest signal from research: (what single finding gives you the most confidence?)
- Riskiest assumption: (what must be true for this product to work, and you have not yet proven it?)
- Core value proposition: (what is the one thing this product does that nothing else does?)
1.2 User & Market Context
- Primary user persona: (name, role, one paragraph describing their situation)
- User's current workaround: (how do they solve this problem today without your product?)
- Switching cost from current solution: (what friction will they face adopting yours?)
- Market timing: (why now? what changed that makes this problem solvable today?)
- Competitive landscape: (who else is building in this space? what is their weakest point?)
More from startup
View all →startup
Advisory Board Pitch
Recruit high-value advisors using a structured advisory board pitch that covers value exchange design, equity compensation frameworks (FAST Agreement compatible), role scoping, and relationship management protocols. This skill produces a complete advisory recruitment package including prospect identification criteria, personalized outreach sequences, the pitch deck for advisors (not investors), an advisory agreement term sheet, an onboarding playbook, and a quarterly engagement framework. Covers strategic advisors, technical advisors, industry advisors, and celebrity/brand advisors with different pitch angles for each. Built for founders who want advisors who actually show up, not just names on a website.
startup
Beta User Outreach
Beta user outreach and recruitment system for startups building their first user base. Use this skill for beta tester recruitment campaigns, waitlist strategy, beta invite emails, early user onboarding sequences, beta feedback collection systems, community seeding, beta signup landing page copy, beta NDA templates, closed beta vs open beta strategy, beta cohort management, beta user incentive structures, TestFlight and early access program setup, beta-to-paid conversion funnels, and beta user referral loops. Trigger for any mention of beta launch, beta users, early access, waitlist building, beta testing, user recruitment for pre-launch, or first 100 users strategy. Delivers complete beta recruitment campaigns, outreach sequences, onboarding flows, feedback systems, and conversion frameworks.
startup
Board Meeting Prep
Complete board meeting preparation system for startup founders running formal or informal boards. Use this skill whenever a founder needs to prepare for, run, or follow up on a board meeting — including creating board decks, structuring agendas, preparing for tough questions, managing board dynamics, drafting board resolutions, handling consent items, and building productive board relationships. Trigger this skill any time the user mentions board meeting, board deck, board presentation, board of directors, board agenda, board minutes, board resolutions, board observer, board dynamics, executive session, committee reports, or preparing for investors. This covers everything from a 3-person seed-stage advisory board to a formal Series B+ board with independent directors and governance requirements.