prototyping-concept-throwaway-evolutionary
Use this skill when picking which kind of prototype to build for the question at hand — concept (exploratory), throwaway (testing one specific aspect), or evolutionary (incremental toward final). Trigger when planning a research method, when scoping a technical spike, or when deciding whether an MVP should evolve or be thrown away. Sub-aspect of `prototyping`; read that first.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- prototyping-concept-throwaway-evolutionary
- description
- Use this skill when picking which kind of prototype to build for the question at hand — concept (exploratory), throwaway (testing one specific aspect), or evolutionary (incremental toward final). Trigger when planning a research method, when scoping a technical spike, or when deciding whether an MVP should evolve or be thrown away. Sub-aspect of `prototyping`; read that first.
02 资源文件 1
- 参考文档references/three-kinds-cases.md2.2 KB
03 SKILL.md 正文
The three prototype kinds
The book identifies three prototype kinds — concept, throwaway, evolutionary — each with characteristic uses, costs, and failure modes.
Concept prototypes
For exploring preliminary ideas. Quick, cheap, often disposable.
Use for: brainstorming sessions, early stakeholder alignment, exploring whether a direction is worth pursuing.
Examples: paper sketches, storyboards, mood boards, foam mockups, role-playing.
Failure mode: artificial reality problem. A skilled designer can make any concept look plausible; the prototype's polish doesn't predict actual workability.
Throwaway prototypes
For testing specific aspects of a design.
Use for: performance benchmarks, A/B tests, single-flow user studies, technical spikes.
Examples: standalone interactive demos, wind-tunnel models, isolated code experiments.
Failure mode: scaling and integration problem. A throwaway that works in isolation may fail when integrated or at scale.
Evolutionary prototypes
For incrementally building toward the final design.
Use for: MVPs that grow into products, iterative startup development, products with uncertain requirements.
Examples: software MVPs, agile sprint outputs, lean startup builds.
Failure mode: tunnel vision. Iterations refine the current direction; teams may miss fundamentally better directions.
Picking the right kind
| Situation | Prototype kind |
|---|---|
| Exploring ideas; "is this worth doing?" | Concept |
| Testing one specific question | Throwaway |
| Iterating toward a final product | Evolutionary |
| Stakeholder alignment | Concept |
| Performance benchmark | Throwaway |
| Scaling a startup | Evolutionary |
The kinds aren't mutually exclusive. A typical project uses concept prototypes early (to align), throwaway prototypes mid (to test specifics), and evolutionary prototypes late (to ship and refine).
Combining the kinds
A common pattern:
- Concept prototypes to explore directions and align stakeholders.
- Throwaway prototypes to test specific risks (performance, user flow, integration).
- Evolutionary prototyping to build the actual product, informed by what concept and throwaway prototypes revealed.
Each kind catches different issues; using all three reduces the risk of any single failure mode.
Resources
- Lidwell, Holden, Butler — Universal Principles of Design (2003).
- Schrage, M. Serious Play (1999).
- Brooks, F. The Mythical Man-Month (1995).
- Boehm, B. "A Spiral Model of Software Development and Enhancement" (1986).
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.