Prototype
Build the cheapest lookable or clickable artifact that can answer one live product question.
What is the smallest thing that can settle this uncertainty?
A narrow job with a visible boundary
Use it before implementation hardens an idea, especially when structure, navigation, or comprehension is still open.
Input
One explicit question, the relevant job, and the fidelity the project can currently support.
Outputs
- An ASCII sketch, SVG click-dummy, or HTML prototype
- Embedded notes and evidence references
- A clear next review handoff
Boundary
A prototype answers one question. It is not production code, user validation, or permission to conceal fake data.
Invocation
humane:prototype
See the decision change
Create a four-screen SVG click-dummy with real navigation labels and representative routes. Defer visual polish.
Navigation can be tested without financing an entire interface.
1 / 2- Too much fidelity
Build the full dashboard so we can decide whether the navigation works.
Create a four-screen SVG click-dummy with real navigation labels and representative routes. Defer visual polish.
- Unclear question
Prototype the new flow.
Open question: can a returning user locate and resume interrupted work? Build only the states required to attempt that task.
Run the skill by name
Install the Humane pack once, then name this skill when the task reaches its boundary.
humane:prototype