MVP Doc

Turn an idea into a decision-complete MVP document set — and keep that document set truthful as work lands. The bundled template (assets/mvp-template.md) defines the target structure; this skill defines the process. It is the entrypoint of a collection: the documents it emits are what the companion skills (/epic, /demo-ideas, /wrap-up, /delegate, /spike, /regression) run the build loop against.

There are two modes. Detect which one applies before doing anything else:

• Create mode — no instantiated MVP doc exists yet (or the user is starting a new project). Run the interview, then generate the docs.
• Update mode — a ROADMAP.md, PRD.md, or instantiated MVP.md already exists in the working directory or was provided. Read it first, then follow references/editing-rules.md. Never re-interview from scratch when a doc exists.

The documents ARE the memory. You have no state between sessions; the roadmap's checkboxes and the PRD's sections are the only persistent record of what was decided and what is done. Treat them accordingly: read them fully at the start of any session that touches the project, and reconcile them before the session ends.

Create mode

Step 0 — Survey before asking

Never open with questions. First, gather everything answerable without the user: