mvp-boundary-mapper

name	mvp-boundary-mapper
description	Use when explicitly defining MVP scope, exclusions, beta screens, states, or success metrics.

MVP Boundary Mapper

Use this skill to turn product ideas into a focused first build.

Workflow

1. Identify the core value proposition and first useful loop.
2. Read references/mvp-boundary-and-screen-map.md; fall back to docs/foundation/mvp-boundary-and-screen-map.md when installed.
3. Split scope into MVP, V1, Later, and Explicitly Excluded.
4. Define first beta screens/surfaces.
5. For each screen, list purpose, primary actions, required data, and states.
6. Define mock/stub requirements needed before real integrations exist.
7. Pick one primary beta success metric.

Rule

The MVP should prove user understanding and trust before broad automation, monetization, or admin tooling.