iteration

Guide repeated design-build-test-refine cycles to validate assumptions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Iteration solves the problem of building a design on untested assumptions by replacing guesswork with repeated cycles of design, build, test, and refinement.

Core Features & Use Cases

  • Iteration cycles that de-risk uncertainty: Use repeated “define → build the cheapest test → expose to reality → observe and learn → decide” loops to reduce unknowns before committing to large builds.
  • Practical guidance for healthy vs. costly iteration: Distinguish planned design iteration from unplanned development rework so teams spend cheap effort early and avoid expensive rework later.
  • Decision support across product workflows: Apply iteration when planning a design process, scoping an MVP, scheduling research cadence, choosing delivery approach, or diagnosing project drift.

Quick Start

Ask an AI to help you design a 4-cycle iteration plan for your MVP by specifying what you will test, what evidence you need, and what you will build in each cycle to validate or discard your assumptions.

Frequently Asked Questions about iteration

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

FAQPage Schema
How do I validate design assumptions before committing to a large build?

Plan a 4-cycle iteration approach by specifying what to test, what evidence you need, and what cheapest feasible prototype to build in each cycle to validate or discard assumptions before scaling delivery.

What is the difference between planned design iteration and unplanned development rework?

Planned design iteration spends cheap effort early through structured build-test-refine loops to learn what users need, whereas costly rework happens later when untested design assumptions fail during development.

How do I scope an MVP using an iteration cycle?

Scoping an MVP with an iteration cycle requires defining each cycle's learning question, using the cheapest feasible experiment to expose work to users, and deciding explicit next-cycle actions based on observed outcomes.

Why does my product design drift from its original vision during development?

Product design drift occurs when untested assumptions accumulate without repeated design-build-test-refine cycles, causing the project to diverge from its original vision and requiring diagnostic iteration to realign delivery.

Can I use iteration to plan a user testing research cadence?

Yes, you can apply iteration to plan a research cadence by scheduling repeated cycles of defining learning questions, exposing the cheapest feasible prototypes to user testing, and refining the design process based on observed data.