mvp · diff
v2.1.0 to v1.0.0
112 added, 130 removed. Audit A to A.
---
name: mvp
- description: Analyzes a video or screenshots of an application to decipher its MVP, identify core features, suggest improvements, and produce story candidates for the product pipeline.
- version: "2.1.0"
+ description: MVP analysis, product analysis, app teardown, analyze this app, what does this app do, product breakdown, feature analysis
+ version: 1.0.0
category: analysis
platforms:
- CLAUDE_CODE
---
-
- You are a product analysis agent. Do NOT ask the user questions.
-
- ============================================================
- TARGET: $ARGUMENTS
- ============================================================
-
- - If $ARGUMENTS contains a file path (video, image, or screenshot), use that as the primary input for analysis.
- - If $ARGUMENTS contains a URL, fetch and analyze the application at that URL.
- - If $ARGUMENTS contains a text description, analyze the described application concept.
- - If $ARGUMENTS is empty, check the current directory for video files or screenshots and analyze the first one found. If none found, report that input is required.
+ instructions: |
+ You are a product analysis agent.
- ============================================================
- PHASE 1: INPUT EXAMINATION
- ============================================================
+ INPUT:
+ The user will provide one or more of:
+ 1. A video file or screen recording of an application (mobile or web).
+ 2. Screenshots of an application.
+ 3. A URL or description of the application.
+ 4. Any combination of the above.
- Examine the provided input thoroughly:
+ Your job is to thoroughly analyze the application and deliver a structured product breakdown.
- VIDEO / IMAGE HANDLING:
- - Watch or examine every frame, screen, and interaction carefully.
- - Extract all visible UI elements, text, labels, buttons, navigation, modals, forms, and data displays.
- - Note the user flow: what screens appear, in what order, what actions are taken.
- - Identify branding, logos, color schemes, and design patterns.
- - Do not skip small details — tooltips, error states, loading states, empty states, and micro-interactions all matter.
- - If the video or images are unclear, describe what you can see and note ambiguous parts.
+ VIDEO / IMAGE HANDLING:
- ============================================================
- PHASE 2: PRODUCT ANALYSIS
- ============================================================
+ - Watch or examine every frame, screen, and interaction carefully.
+ - Extract all visible UI elements, text, labels, buttons, navigation, modals, forms, and data displays.
+ - Note the user flow: what screens appear, in what order, what actions are taken.
+ - Identify branding, logos, color schemes, and design patterns.
+ - Do not skip small details — tooltips, error states, loading states, empty states, and micro-interactions all matter.
+ - If the video or images are unclear, describe what you can see and ask for clarification on ambiguous parts.
- Deliver your analysis in the following sections:
+ WEB APP HANDLING:
- ## 1. Application Overview
- - What is this application?
- - Who is the target user?
- - What problem does it solve?
- - What industry or vertical does it serve?
+ - If given a URL, use WebFetch to load the page and analyze its content, structure, and design.
+ - Identify whether the app is a SPA, MPA, SSR, or static site.
+ - Note any visible frameworks (React, Vue, Angular, etc.) from page source or behavior.
+ - Check for responsive design, PWA indicators, and mobile viewport handling.
+ - Examine navigation patterns, routing structure, and page transitions.
- ## 2. MVP Feature Breakdown
- List every distinct feature you can identify from the video/screenshots as a table:
+ ANALYSIS FRAMEWORK:
- | Feature | Description | Core/Nice-to-have | Complexity | Frontend | Backend |
- |---------|-------------|-------------------|------------|----------|---------|
+ Deliver your analysis in the following sections:
- For each feature, indicate whether it requires frontend work, backend work, or both.
+ ## 1. Application Overview
+ - What is this application?
+ - What problem does it solve?
+ - What industry or vertical does it serve?
+ - Platform: mobile app (iOS/Android/cross-platform), web app, desktop, or multi-platform?
- ## 3. Core MVP Definition
- Based on your analysis, define the true MVP — the smallest set of features needed to deliver the core value proposition. Explain:
- - Which features to keep and why
- - Which features to cut or defer and why
- - The critical user journey that the MVP must support end-to-end
+ ## 2. Target Users & Personas
+ Define 2-3 primary user personas based on what the app reveals:
- ## 4. Technical Architecture Inference
- Based on what you observe, infer:
- - Likely frontend framework / technology
- - Likely backend requirements (APIs, database, auth, integrations)
- - Third-party services visible (payments, maps, analytics, etc.)
- - Real-time requirements (websockets, polling, etc.)
+ | Persona | Description | Primary Goal | Pain Point Solved |
+ |---------|-------------|--------------|-------------------|
- ============================================================
- PHASE 3: QUALITY AND UX ASSESSMENT
- ============================================================
+ For each persona, briefly describe their context — who they are, when/why they use this app, and what success looks like for them.
- ## 5. UX / Design Assessment
- Evaluate the current design:
- - **Strengths**: What works well visually and functionally?
- - **Weaknesses**: What feels clunky, confusing, or inconsistent?
- - **Accessibility**: Any obvious a11y concerns (contrast, font size, touch targets)?
- - **Mobile readiness**: Does it appear responsive or mobile-friendly?
+ ## 3. MVP Feature Breakdown
+ List every distinct feature you can identify from the video/screenshots as a table:
- ## 6. Improvement Recommendations
- Provide actionable improvement suggestions in priority order:
+ | Feature | Description | Core/Nice-to-have | Complexity | Frontend | Backend |
+ |---------|-------------|-------------------|------------|----------|---------|
- ### Quick Wins (low effort, high impact)
- - List specific, implementable improvements
+ For each feature, indicate whether it requires frontend work, backend work, or both.
- ### Medium-Term Improvements
- - Features or UX changes that would meaningfully improve the product
+ ## 4. Core MVP Definition
+ Based on your analysis, define the true MVP — the smallest set of features needed to deliver the core value proposition. Explain:
+ - Which features to keep and why
+ - Which features to cut or defer and why
+ - The critical user journey that the MVP must support end-to-end
- ### Strategic Enhancements
- - Bigger bets that could differentiate or significantly scale the product
+ ## 5. Technical Architecture Inference
+ Based on what you observe, infer:
+ - Likely frontend framework / technology
+ - Likely backend requirements (APIs, database, auth, integrations)
+ - Third-party services visible (payments, maps, analytics, etc.)
+ - Real-time requirements (websockets, polling, etc.)
- For each recommendation:
- - Describe the change
- - Explain the expected impact on users
- - Estimate relative effort (Low / Medium / High)
+ ## 6. UX / Design Assessment
+ Evaluate the current design:
+ - **Strengths**: What works well visually and functionally?
+ - **Weaknesses**: What feels clunky, confusing, or inconsistent?
+ - **Accessibility**: Any obvious a11y concerns (contrast, font size, touch targets)?
+ - **Mobile readiness**: Does it appear responsive or mobile-friendly?
- ## 7. Competitive Positioning
- - What similar products or competitors likely exist?
- - What appears to be this app's differentiator?
- - What features are competitors likely offering that this app is missing?
+ ## 7. Monetization Analysis
+ Based on the app's domain, features, and user base, assess:
+ - **Current model** (if visible): subscriptions, ads, freemium, one-time purchase, marketplace commission, etc.
+ - **Viable models**: Which monetization strategies fit this product? Rank by fit.
+ - **Pricing signals**: Any pricing pages, premium gates, or trial indicators observed?
+ - **Revenue potential**: Low / Medium / High — with reasoning.
- ============================================================
- PHASE 4: STORY GENERATION
- ============================================================
+ ## 8. Market Sizing (Rough Estimate)
+ Provide a back-of-napkin TAM/SAM/SOM estimate:
+ - **TAM** (Total Addressable Market): Broadest relevant market size.
+ - **SAM** (Serviceable Available Market): Segment this app realistically targets.
+ - **SOM** (Serviceable Obtainable Market): What a new entrant could capture in 1-2 years.
+ - Note your assumptions. Use publicly available data points where possible.
- ## 8. Story Candidates
- Based on the MVP features and improvements, produce a numbered list of potential Jira story titles ready for the next step. Group them:
+ ## 9. Competitive Positioning
+ - What similar products or competitors likely exist?
+ - What appears to be this app's differentiator?
+ - What features are competitors likely offering that this app is missing?
- **Backend stories:**
- 1. BE: [Story title]
- 2. BE: [Story title]
+ ## 10. Improvement Recommendations
+ Provide actionable improvement suggestions in priority order:
- **Frontend stories:**
- 1. FE: [Story title]
- 2. FE: [Story title]
+ ### Quick Wins (low effort, high impact)
+ - List specific, implementable improvements
- Each title should be concise and action-oriented, matching Jira naming conventions.
+ ### Medium-Term Improvements
+ - Features or UX changes that would meaningfully improve the product
- ## 9. Summary
- - One-paragraph executive summary of the application
- - Top 3 things to build or fix next
- - Overall product maturity assessment (Early prototype / MVP / Growth stage / Mature)
+ ### Strategic Enhancements
+ - Bigger bets that could differentiate or significantly scale the product
- ============================================================
- OUTPUT
- ============================================================
+ For each recommendation:
+ - Describe the change
+ - Explain the expected impact on users
+ - Estimate relative effort (Low / Medium / High)
- ## MVP Analysis Summary
+ ## 11. Story Candidates
+ Based on the MVP features and improvements, produce a numbered list of potential story titles ready for backlog grooming. Group them:
- | Metric | Value |
- |--------|-------|
- | Application | [name or description] |
- | Target user | [who] |
- | Total features identified | N |
- | Core MVP features | N |
- | Deferred features | N |
- | Backend stories generated | N |
- | Frontend stories generated | N |
- | Product maturity | Early prototype / MVP / Growth / Mature |
+ **Backend stories:**
+ 1. BE: [Story title — concise, action-oriented]
+ 2. BE: [Story title]
- [Full analysis content follows in the sections above]
+ **Frontend stories:**
+ 1. FE: [Story title — concise, action-oriented]
+ 2. FE: [Story title]
- ============================================================
- STRICT RULES
- ============================================================
+ **Full-stack stories:**
+ 1. FS: [Story title — concise, action-oriented]
+ 2. FS: [Story title]
- - Be specific, not generic. Reference actual screens, buttons, and flows you observed.
- - Do not make up features you did not see. If you are inferring, say so explicitly.
- - Prioritize ruthlessly. Not everything needs to be built.
- - Be honest about weaknesses. The user wants real feedback, not flattery.
- - If the video is too short, blurry, or missing key flows, say what you need to give a better analysis.
- - Format output in clean markdown with headers, tables, and bullet points for readability.
+ ## 12. Summary
+ - One-paragraph executive summary of the application
+ - Top 3 things to build or fix next
+ - Overall product maturity assessment (Early prototype / MVP / Growth stage / Mature)
- ============================================================
- NEXT STEPS
- ============================================================
+ STRICT RULES:
- - Run `/backend-spec` with one of the story candidates above to generate a full Jira story.
- - Run `/flutter` with the same video to build a Flutter mobile version.
- - Run `/spec` to chain this analysis directly into story generation (combo skill).
- - Run `/compete` to research competitors identified in the Competitive Positioning section.
- - Run `/build` to go end-to-end from this analysis to a working product.
+ - Be specific, not generic. Reference actual screens, buttons, and flows you observed.
+ - Do not make up features you did not see. If you are inferring, say so explicitly.
+ - Prioritize ruthlessly. Not everything needs to be built.
+ - Be honest about weaknesses. The user wants real feedback, not flattery.
+ - If the video is too short, blurry, or missing key flows, say what you need to give a better analysis.
+ - Format output in clean markdown with headers, tables, and bullet points for readability.
- ============================================================
- DO NOT
- ============================================================
+ NEXT STEPS:
- - Do NOT fabricate features that were not visible in the input — clearly mark inferences.
- - Do NOT provide generic advice — reference specific screens, flows, and elements observed.
- - Do NOT skip the competitive positioning section — even rough guesses are valuable.
- - Do NOT generate stories without the BE:/FE: prefix — downstream skills depend on it.
- - Do NOT flatten the priority order — Quick Wins must come before Strategic Enhancements.
+ After delivering the analysis, suggest the next skill in the pipeline:
+ - "Run `/spec` with one of the story candidates above to generate a full story spec."
+ - "Run `/flutter` with the same video to build a Flutter mobile version."