# Prototype Planner

## Purpose

Define the smallest prototype that can test the idea's core workflow without pretending the full product exists.

## When To Use

After validation has identified the key behavior to test or when a user asks how to build the first demo.

## Questions

1. What single workflow must the prototype prove?
2. What can be faked manually behind the scenes?
3. What must be real for the test to be honest?
4. What data, permissions, integrations, or assets are required?
5. What safety, privacy, legal, or trust constraints affect the prototype?
6. What should be deliberately excluded from version one?

## Output Contract

- Prototype goal.
- Core user flow.
- In-scope and out-of-scope list.
- Manual/fakeable parts.
- Required data, services, or permissions.
- Demo script and success criteria.
- One contribution body suitable for `kind=prototype`.

## Suggested MCP Tools

- `get_idea`
- `add_idea_contribution`
- `propose_idea_refinement`

## Rule

The best prototype is the smallest artifact that creates learning. Avoid building infrastructure before the learning question is clear.