prototyping-concept-throwaway-evolutionary

Select concept, throwaway, or evolutionary prototypes for planning decisions.

6|3|Updated May 3, 2026
One-click install
npx skills add https://github.com/HDeibler/universal-design-principles --skill prototyping-concept-throwaway-evolutionary
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prototyping-concept-throwaway-evolutionary
Source: https://github.com/HDeibler/universal-design-principles/tree/main/plugins/process-and-robustness-principles/skills/prototyping-concept-throwaway-evolutionary
Command: npx skills add https://github.com/HDeibler/universal-design-principles --skill prototyping-concept-throwaway-evolutionary

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you select the most appropriate prototype type so you can test the right uncertainties at the right time, instead of wasting effort or shipping work that fails integration, scaling, or reality checks.

Core Features & Use Cases

  • Concept prototyping guidance: Choose concept (exploratory) prototypes for direction-finding, early alignment, and validating whether an idea is worth pursuing.
  • Throwaway prototyping guidance: Choose throwaway prototypes for isolating and testing one specific aspect (e.g., a hypothesis, risk, or performance constraint) without building the whole system.
  • Evolutionary prototyping guidance: Choose evolutionary prototypes for incremental delivery that can become the real product (e.g., MVPs with uncertain requirements).
  • Failure-mode awareness: Avoid common pitfalls such as treating concept as a near-final build, treating evolutionary as throwaway, or skipping concept prototypes.

Quick Start

Use the skill when you are planning a research method, technical spike, or MVP decision and ask: "Which prototype type (concept, throwaway, or evolutionary) should we use for this goal, what should we build, and what failure mode should we watch for?"

Frequently Asked Questions about prototyping-concept-throwaway-evolutionary

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

FAQPage Schema
What type of prototype should I use for MVP hypothesis testing?▼

Selecting the right prototype type reduces product risk by matching the method to your uncertainty: concept prototypes for early direction-finding, throwaway prototypes for isolating specific risks, and evolutionary prototypes for incrementally building an MVP that becomes the real product.

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

Use throwaway prototypes to isolate and test one specific aspect like a hypothesis or performance constraint, whereas evolutionary prototypes are for incremental delivery where the prototype becomes the real product when requirements are uncertain.

What are common failure modes when choosing a prototype type?▼

Common failure modes include treating concept prototypes as near-final builds, treating evolutionary prototypes as throwaway, or skipping concept prototypes entirely, which wastes effort and causes integration failures.

How do I scope a technical spike using the right prototype?▼

Scope technical spikes using throwaway prototypes to isolate and test specific technical risks or performance constraints without building the whole system, preventing premature architecture commitments.

Can I combine multiple prototype types in a single product development stage?▼

Yes, you can apply a staged combination strategy by starting with a concept prototype for direction-finding, using a throwaway prototype to isolate specific risks, and finishing with an evolutionary prototype for incremental MVP delivery.