# Prototype Elicitation

> Purpose

- Skill: `45ck/prototype-elicitation` (Agent Skill)
- Install (CLI): `npx skillmds@latest add 45ck/prototype-elicitation`
- Raw SKILL.md: https://api.skillmd.com/api/skills/45ck/prototype-elicitation/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: 45ck (https://skillmd.com/u/45ck)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/45ck/prototype-elicitation

---

## Purpose
Use sketches, mock-ups, or prototypes to expose assumptions and refine requirements.

## Use when
- stakeholders struggle to react to text-only requirements
- interface, workflow, or interaction detail matters
- ambiguity remains after interviews/workshops

## Inputs
- problem context
- available evidence and constraints
- known stakeholders or actors
- desired output format

## Procedure
1. Clarify the decision or deliverable.
2. State assumptions before analysis.
3. Apply the technique explicitly rather than implicitly.
4. Capture findings in a structured table or list.
5. Separate facts, inferences, and unknowns.
6. End with implications for next actions.

## Outputs
- prototype goals
- prototype fidelity recommendation
- test scenarios
- feedback questions
- requirement changes log

## Guardrails
- Do not present the technique as the answer; use it to inform a decision.
- Flag missing evidence and weak assumptions.
- Keep terminology consistent with the project glossary.
- Where tradeoffs exist, rank them explicitly.

## Completion criteria
- technique applied correctly
- assumptions visible
- findings actionable
- next step clear