Turn an idea into a buildable MVP — Full Prompt Suite

A guided prompt system to find the smallest useful product flow and make its build sequence reviewable.

8 downloadable Markdown files

Discovery, master, implementation, review and handoff prompts

Business-context worksheet and internal-use license

Immediate ZIP download after confirmed payment

Support: account and delivery help through AEVUS Support

Refund terms: reviewed under the Terms of Service

Built for: smallest complete user journey · architecture and dependencies · acceptance states · demo evidence

Illustrative example

A fictional appointment idea has many proposed features but no complete first user journey.

A useful result: A one-request, one-response MVP flow with a simple architecture, ordered backlog, and acceptance checks.

Review before use: Confirm the first journey is useful to both sides and remains within the stated time and budget.

Secure checkout by Stripe. AEVUS does not receive your complete card number.

What to provide

User problem, actors, first journey, existing assets, constraints, budget, and success measure.

What you will get

An MVP scope, simple architecture, phased backlog, acceptance checks, and open decisions.

Example: Fictional example: A booking idea starts with one request, one provider response, and a confirmed appointment.

Copy the full prompt

Customize the bracketed fields.

Use approved business information and have a person review the result before acting.

Turn this idea into a reviewable minimum viable product plan.
Problem and intended users: [details]
First useful journey: [start, action, result]
Existing assets and stack: [verified facts]
Budget, time, and team: [constraints]
Data and permission boundaries: [known rules]
Success measure: [observable result]

Ask for missing outcomes before choosing features. Define the smallest end-to-end journey, including initiation, receiving-side response when applicable, persisted result, and visible confirmation. Separate must-have scope, later ideas, and assumptions. Produce a simple architecture and data-flow sketch, a sequenced backlog with dependencies and owner roles, acceptance checks for success, empty, error, unauthorized, and recovery states, and a demo scenario using fictional data. Flag decisions needing security, legal, financial, or human approval. Do not invent integrations, estimate unsupported costs, create accounts, or deploy.

Response requirements:
- Begin with a short summary of the goal, confirmed facts, assumptions, and missing information.
- Ask focused clarification questions before completing the work when a missing answer would materially change the result.
- Use clear headings, tables, checklists, or numbered steps where they make the output easier to use.
- Keep source facts separate from recommendations. Quote or cite supplied evidence when the task depends on source material.
- Mark unsupported details, decisions, owners, dates, costs, credentials, and commitments as [TO CONFIRM].
- Identify the three most important risks, failure conditions, or quality checks.
- End with a practical next-action checklist that names the responsible role and the evidence needed to confirm completion.
- Include a final self-review: check the answer against this prompt, list any unmet requirement, and correct it before responding.
- Do not claim that you accessed a system, verified an external fact, completed an action, or tested the result unless evidence in this conversation proves it.

Get help adapting this prompt ↗

Version 1.0 · Updated 2026-10-10 · Free starter template. Evaluate the output in your approved environment.