META·SUITE ← all nine
overview / skills / meta-mvp
Skill 04 · make axis

meta-mvp

One line in. A full, research-grounded deliverable bundle out.

ONE LINE ↓ expand FULL BUNDLE spec.mdscope · goals prototypeworking v0 testshappy + edge docshow to run next-steps planwhat's after v0 WHAT'S HAPPENING 1 · Start from a single line describing the thing. 2 · Fill in the decisions a plan usually leaves invisible. 3 · Out comes a runnable bundle: spec, prototype, tests, docs, plan. The smallest thing worth shipping — researched before it's built, so v0 holds up on day one.
FIG — a one-line prompt unfolds into a complete, runnable bundle
// what it does

Most "MVPs" stall because the gap between an idea and something you can actually run is full of invisible decisions. meta-mvp makes those decisions explicit and fills them — turning a one-liner into a spec, a working prototype, tests, docs, and a next-steps plan.

It is grounded, not guessed: it researches the space before it builds, so the v0 is defensible on day one — the smallest thing that is genuinely worth shipping.

// what's in the bundle
the spec

Scope, goals, and the one thing this version must prove.

the prototype

A working v0 — the smallest thing that actually runs.

the runway

Tests, docs, and the plan for what comes after v0.

// invoke it
/meta-suite:meta-mvp <one line describing the thing>

Returns a full bundle — spec, prototype, tests, docs, plan — researched before it's built. Hand it the line; get back something you can run and show today.

Runs on day one

Not a slide about a plan.

Research-grounded

Defensible, not guessed.

Smallest worth it

Nothing padded in.

It compounds

A runway, not a dead end.

Grounding

The ideas here aren't invented — the skill generalizes established practice into one reusable, task-agnostic move. Below: the prior art it builds on, and the in-repo contract it actually runs on.

Prior art
Minimum Viable Product — Eric Ries, The Lean Startup (2011) — ship the smallest thing that proves the value, then learn from it.
Structure-preserving expansion — a one-line prompt mapped onto a full bundle: entities → data model, relationships → contracts, independence → build lanes. kept internal
Research-grounded, no invented facts — ground on real sources before building; flag anything unverified rather than assert it.
In this suite
The 9-stage pipeline references/pipeline.md and its hard completion gate — intake → ground → expand → meta-prompt → spec layer → plan → model → build → verify → ship.