Popular idea prototype

# Popular idea prototype

Use when reviewing a popular idea and you want an interactive prototype to test the concept before committing engineering effort.

## Definitions

Use these meanings consistently in every step.

- **Idea:** The idea record being prototyped, or the idea whose record link the user pasted into the chat
- **Fidelity:** How finished the prototype looks. Low shows structure and flow only. Medium adds real labels and states. High applies visual design.
- **Demand evidence:** The votes, linked organizations, and comments on the idea that explain why it is worth prototyping
- **Scope:** The specific screens the prototype covers. Everything outside that set is out of scope.

## Workflow

1. Read the idea, its description, its votes, and its comments. Note the named organizations and the vote count so the prototype answers the demand that exists.
2. Confirm fidelity and scope with the user. Default to low fidelity and the smallest set of screens that demonstrates the concept.
3. Identify the workflow the prototype has to show, from entry point to completion. A prototype that shows one complete path is more useful than one that shows fragments of several.
4. Generate realistic sample data drawn from the idea and the workspace. Use plausible names, dates, and values rather than placeholder text.
5. Build the prototype. Cover the primary path first, then add the empty state and one error state.
6. Note what the prototype deliberately leaves out, so reviewers do not read a gap as a decision.
7. Suggest what to validate with customers, tied to the accounts that voted on the idea.

## Rules

- If the idea is missing, ask which idea to prototype before generating anything
- Match the visual conventions of Aha! software unless the user supplies a different design reference
- When the user uploads an image as a design reference, follow its layout and styling
- Sample data is realistic and internally consistent. Never leave lorem ipsum in a prototype.
- Reference the idea by reference number and name
- Do not promote the idea or create records from it. Present the prototype and let the user decide.
- Headers use sentence case. No em dashes, en dashes, or curly quotes.

## Output

```
## What this prototype shows  
<the concept and the workflow it covers, in two to three sentences>  
  
## Demand behind it  
- <votes, named organizations, and the strongest comment>  
  
## Screens  
| Screen | Purpose | States covered |  
  
## Out of scope  
- <what was deliberately left out>  
  
## What to validate  
- <question to put to a specific customer or segment>
```

Save the prototype as an artifact and share the link so the team reviews the same version.

## Quality checks

- The prototype covers one complete path rather than several partial ones
- Sample data is plausible and consistent across screens
- The out of scope list is present, so gaps do not read as decisions
- Every validation question maps to demand evidence on the idea