prototyping-strategy

Select prototyping approaches based on project risks, fidelity needs, and evaluation goals.

23|1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/jdm4pku/RE-Skills --skill prototyping-strategy-jdm4pku
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prototyping-strategy
Source: https://github.com/jdm4pku/RE-Skills/tree/main/skills/prototyping-strategy
Command: npx skills add https://github.com/jdm4pku/RE-Skills --skill prototyping-strategy-jdm4pku

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When requirements are unclear, feasibility is uncertain, or stakeholders disagree on UI direction, teams often build the wrong prototype or skip evaluation entirely. This Skill provides a decision framework for choosing what to prototype, at what fidelity, with what lifecycle intent, and how to evaluate the results. ## Core Features & Use Cases - Adaptive Selection Questions: Four structured questions covering prototype purpose, fidelity level, lifecycle intent, and evaluation method drive a concrete recommendation. - Recommendation Logic: Maps answer combinations to specific approaches such as paper prototypes, clickable wireframes, vertical proof-of-concepts, and Wizard of Oz setups, each with scope, time estimates, and outputs. - Evaluation Script Template: A reusable session script covering introduction, background questions, task scenarios, post-task questions, and debrief. - Use Case: A team unsure how users will search a chemical inventory answers the four questions, receives a recommendation for a low-fidelity horizontal throwaway prototype, and runs task-based think-aloud sessions with five lab technicians. ## Quick Start Ask the assistant to help you choose a prototyping approach for a feature with uncertain requirements and have it walk you through the four selection questions.

Frequently Asked Questions about prototyping-strategy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose the right prototyping approach for unclear requirements?▼

Answer four questions about purpose, fidelity, lifecycle intent, and evaluation method. The recommendation logic maps your answers to an approach such as a paper prototype, clickable wireframe, or vertical proof-of-concept, with scope and time estimates.

What is the difference between horizontal and vertical prototypes?▼

A horizontal prototype shows many features at surface level to validate navigation and workflows. A vertical prototype implements one feature deeply end to end to validate technical feasibility, performance, or integration.

When should I use a throwaway versus an evolutionary prototype?▼

Use a throwaway prototype when exploring uncertain requirements or evaluating alternatives, and discard it after learning. Use an evolutionary prototype only when requirements are fairly stable and the architecture is proven, since it grows into the production system.

What is the Wizard of Oz prototyping technique?▼

A human behind the scenes simulates system responses that have not been built yet while users interact with a realistic interface. It is useful for AI features, complex search, or recommendation engines where building the real backend is expensive.

Why do prototype evaluations fail to produce useful feedback?▼

Evaluations fail when there is no plan defined before building the prototype, resulting in vague feedback like "looks good." Define tasks, participants, and measurable success criteria upfront, and use think-aloud or task-based protocols.

What fidelity level should a prototype have?▼

Match fidelity to the question being answered. Navigation and layout questions need only paper or low-fidelity wireframes, while feasibility questions require high-fidelity vertical slices. High fidelity for simple questions wastes effort and distracts users.