mvp-architect

Included with Lifetime

$97 forever

Use this skill when users need to scope an MVP, define minimum viable features, plan early product development, or determine what to build first. Activates for "what should my MVP include," "scope my MVP," "what to build first," or product scoping questions.

General

What this skill does


# MVP Architect - Minimum Viable Product Scoping

## Overview

Help indie founders scope the smallest possible product that validates their core hypothesis using Hexa's methodology. Get to market in 3 months or less.

**Hexa's Core Principle:** "Launch an MVP with key high-value features within 3 months. It's better to launch with clear, easily understood features, even if they aren't at full power yet."

## When This Activates

- "What should my MVP include"
- "Help me scope my MVP"
- "What features do I need"
- "What to build first"
- "Been building for months, haven't launched"

## Hexa's 7 Principles

1. **Dig Beyond User Requests** — Root needs, not surface wants
2. **Combat Confirmation Bias** — Challenge assumptions
3. **Partner with Design Partners Early** — Build with real users
4. **Prioritize Adaptable Milestones** — 6-month goals, 2-week sprints
5. **Sketch Before Designing** — Keep ugly until validated
6. **Build Around Dry Elements** — Only include stable features
7. **Stress-Test Architecture** — Database design affects everything

## Quick Workflow

### Step 1: Problem Clarity Check

- 10+ customer interviews?
- One-sentence problem?
- 3-5 design partners?

### Step 2: Core Hypothesis

```
We believe that [customer] has a problem with [pain point].
We believe that [solution] will solve this.
We will know we're right when [success metric].
```

### Step 3: Feature Prioritization

For each feature ask:

- Tests core hypothesis? → Keep
- Users explicitly asked? → Maybe
- Critical path? → Keep
- Can do manually? → Don't build

**Target: 3-5 features maximum.**

### Step 4: Dry Elements Test

Only build features that remained stable through ALL design partner feedback.

### Step 5: User Journey (3-4 Screens)

- How do users sign up?
- First action?
- Core value delivery?
- Success confirmation?

## Anti-Scope Creep Checklist

Before adding ANY feature:

1. Does this test our core hypothesis? → If no, cut it
2. Have 3+ design partners asked? → If no, defer it
3. Can we launch without this? → If yes, defer it
4. Can we do this manually first? → If yes, don't build it
5. Will this delay launch by >3 days? → If yes, cut it

## The "Launch in 2 Weeks" Test

If you HAD to launch in 2 weeks, what would you cut?
**Whatever you'd cut... cut it now.** That's your real MVP.

## Integration

- `idea-validator` - Validate before scoping
- `startup-icp-definer` - Define who you're building for
- `fullstack-workspace-init` - Set up codebase
- `brand-architect` - Name and position product

---

**For complete hypothesis framework, feature prioritization matrix, dry elements identification, screen mapping, technical architecture checklist, timeline templates, and output format, see:** `references/full-guide.md`

Files: 3

Size: 13.3 KB

Complexity: 33/100

Category: General

Source: https://github.com/shipshitdev/library/tree/main/bundles/startup/skills/mvp-architect

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts