MVP Blueprint
Purpose
Define your Minimum Viable Product - the smallest version that delivers core value and validates demand. Avoid building too much before knowing if people will pay, while building enough to actually test the concept.
When to Use
Use this Skill when you need to:
- Plan your first product version
- Reduce scope to essential features
- Get to market faster
- Test assumptions with real users
- Prioritize what to build first
Step-by-Step Process
Step 1: Define Core Value
Identify the essential value proposition.
Ask the user:
- What is the main problem you solve?
- What would success look like for a user?
- What is the ONE thing your product must do?
- What can you remove and still deliver value?
- Who is your first target user?
Output Variable: core_value
Step 2: Map User Journey
Outline the critical path.
Define:
- Entry point: How do users discover you?
- Core action: What do they do to get value?
- Value moment: When do they feel success?
- Retention hook: Why would they come back?
Output Variable: user_journey Context Used: core_value
Step 3: Prioritize Features
Separate must-have from nice-to-have.
Feature categories:
- Must Have: Required for core value
- Should Have: Important but not critical
- Could Have: Nice additions
- Will Not Have: Explicitly excluded for V1
Use the question: "Could a user get value without this?"
Output Variable: feature_priority Context Used: core_value, user_journey
Step 4: Define Success Metrics
Know how you will measure validation.
Identify:
- Key metric that indicates success
- Target numbers for validation
- Timeline for testing
- Signals that mean pivot vs persevere
Output Variable: success_metrics
Step 5: Create MVP Specification
Document your MVP plan.
Include:
- Product Vision: One-sentence description
- Target User: Who this is for
- Core Value Proposition: Main benefit
- User Journey: Step-by-step flow
- Feature List: Must-have only
- Not Included: Explicit exclusions
- Success Metrics: How to validate
- Timeline: Target launch date
- Next Steps: Immediate actions
Save using basile_create_document.
Output Variable: mvp_spec