Individual skill
prototyping-when-and-what
Use this skill when deciding what to prototype, what fidelity to use, and when to stop prototyping and ship. Trigger when planning research, scoping a design phase, or facing pressure to "stop prototyping and just build it." Sub-aspect of `prototyping`; read that first.
plugins/HDeibler/universal-design-principles/plugins/process-and-robustness-principles/skills/prototyping-when-and-what/SKILL.md
Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,537
- Repository last updated
- Nov 7, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-coding Repository topic
- awesome Repository topic
- awesome-list Repository topic
- codex Repository topic
- codex-plugins Repository topic
- openai Repository topic
- codex-skill Repository topic
- codex-skills Repository topic
- marketplace Repository topic
- codex-marketplace Repository topic
- design Derived category
- research Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 5,354 bytesreferences/when-to-stop.mddoc · 2,282 bytes
Read excerpt
# Picking what and when to prototype
Prototyping has costs (time, opportunity, sometimes confusion). Picking the right thing to prototype, at the right fidelity, at the right moment, is how teams get the benefits without the costs.
## What to prototype
Three categories of question prototypes answer well:
### Risky assumptions
Things you're not sure will work. The riskier the assumption, the more valuable the prototype.
- "Users will understand this new flow" — prototype + user test.
- "This algorithm will be fast enough at production scale" — throwaway performance prototype.