New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Iteration Design Vs Development

by hashgraph-online in hashgraph-online/awesome-codex-plugins

A skill your agent uses when reviewing where in the project lifecycle iteration is happening — desirable iteration during design vs.

Apache-2.0Auto-check passedProduct & Project Management

Install Iteration Design Vs Development

skills CLI
$ npx skills add hashgraph-online/awesome-codex-plugins --skill iteration-design-vs-development -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install hashgraph-online/awesome-codex-plugins iteration-design-vs-development --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/HDeibler/universal-design-principles/plugins/process-and-robustness-principles/skills/iteration-design-vs-development .claude/skills/iteration-design-vs-development && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
iteration-design-vs-development
GitHub stars
1.3k
Token cost
~1.6k tokens
SKILL.md length
777 words
Files
2 (incl. references)
Skills in repo
714
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when reviewing where in the project lifecycle iteration is happening — desirable iteration during design vs.

  • Works in 3 steps: The "where did we discover this issue?"… → The fidelity-vs-question check. For each… → The engineering-pairing audit. Across…
  • Reviewing where in the project lifecycle iteration is happening — desirable iteration during design vs
  • SKILL.md covers Why the distinction matters, Healthy design iteration, Costly development iteration and Causes of excess development…, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Iteration Design Vs Development is an agent skill from hashgraph-online/awesome-codex-plugins. Use this skill when reviewing where in the project lifecycle iteration is happening — desirable iteration during design vs. costly rework during development. Trigger when a project keeps slipping due to "design changes during build," when scoping how much design work to do before engineering begins, or when retrospectives reveal that issues were caught too late. Sub-aspect of iteration; read that first.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/cost-of-late-change.md`).

It sits in Product & Project Management, covering Retrospectives. The repository describes itself as: A curated list of awesome OpenAI Codex / ChatGPT plugins, skills, and resources. The 1 Codex Marketplace. See live plugins at: https://hol.org/plugins/best-codex-plugins. The licence is Apache-2.0.

When your agent uses it

  • Reviewing where in the project lifecycle iteration is happening — desirable iteration during design vs
  • A project keeps slipping due to design changes during build
  • Scoping how much design work to do before engineering begins
  • Retrospectives reveal that issues were caught too late

Example prompts

  • “design changes during build,”
  • “/iteration-design-vs-development”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. The "where did we discover this issue?" retrospective. After each project, list the issues that were discovered. For each, ask where it…
  2. The fidelity-vs-question check. For each design decision, ask: what's the cheapest prototype that answers this? Use that.
  3. The engineering-pairing audit. Across recent projects, was engineering involved during design? Projects where they weren't usually had…

What it can do on your machine

Read from SKILL.md and the folder at commit 9e7b281. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Iteration Design Vs Development loads about 1.6k tokens when it runs, and up to ~2.3k if it reads all its reference files. Until then it costs about 110 tokens; SKILL.md has 777 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~110
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from hashgraph-online/awesome-codex-plugins at commit 9e7b281, republished under its Apache-2.0 licence (© hashgraph-online). 777 words, ~1,600 tokens.

Download SKILL.mdSave it as .claude/skills/iteration-design-vs-development/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
iteration-design-vs-development
description
Use this skill when reviewing where in the project lifecycle iteration is happening — desirable iteration during design vs. costly rework during development. Trigger when a project keeps slipping due to "design changes during build," when scoping how much design work to do before engineering begins, or when retrospectives reveal that issues were caught too late. Sub-aspect of `iteration`; read that first.

Design iteration vs. development iteration

The book makes a useful distinction: design iteration is the planned cycles that happen during the design phase; development iteration is the unplanned rework during build that means design wasn't iterated enough up front. The first is healthy; the second is expensive.

Why the distinction matters

Cost per iteration cycle rises sharply as the project moves from design to development to deployment:

Sketch / wireframe       1x cost
Interactive prototype    3-5x
Coded MVP                10-30x
Production-shipped       50-200x
Production-deployed-to-customers  200-1000x

A change discovered during sketch costs a few hours; the same change discovered after deployment to customers can cost weeks of engineering, customer-trust damage, and emergency response.

The principle: do as much iteration as possible at the cheapest fidelities. By the time the design moves to engineering, the fundamental questions should be answered.

Healthy design iteration

Cycles measured in days to weeks; outputs include:

  • Sketches and wireframes
  • Interactive prototypes (Figma, Framer, code prototypes)
  • User interviews and usability tests
  • Design critiques
  • Stakeholder reviews
  • Refined specifications

Each cycle has explicit purpose and known criteria for completion.

Costly development iteration

Symptoms:

  • "We need to refactor that whole module — turns out the design didn't work."
  • "Engineering says they can't build it as designed."
  • "We discovered a fundamental issue in QA."
  • "We shipped, users complained, we're rolling back."

Each is evidence that design iteration didn't catch what it should have.

Causes of excess development iteration

  • Insufficient design iteration. Skipping prototyping; rushing past user testing.
  • Engineering-design isolation. Designers and engineers don't talk during design; engineering discovers issues during build.
  • Untested assumptions. "I think users will want X" untested until users encounter X in production.
  • Premature high fidelity. Polishing pixels before structure is right. The pixels then have to be re-done.
  • Spec-and-throw. Designers spec without engineering input; engineering builds; result doesn't match the spec's intent.

Reducing development iteration

Bring engineering into design earlier

Pair designers with engineers during early design phases. Engineers see implementation issues that designers miss; designers see UX issues that engineers miss. Catching either early is cheap.

Prototype with the same primitives as production

A Figma prototype is fast but doesn't reveal performance issues, accessibility issues, or implementation complexity. A code prototype using your actual component library reveals those issues at the design phase, when they're cheap.

Test with users at low fidelity

Paper prototypes and clickable wireframes catch most fundamental issues. The fancier the prototype, the more users react to the prototype's polish rather than its structure.

Define "done with design" criteria

Don't move to development until specific questions are answered. "Users can complete the core task in the prototype" is a clearer gate than "design looks good."

Maintain feedback channels during build

Engineers building the design should be able to flag issues quickly to designers. Async tools (Slack, design-review channels, weekly syncs) preserve this without slowing engineering.

Show full SKILL.md (325 more words)Show less

When development iteration is unavoidable

Some projects unavoidably need development iteration:

  • Performance-discovered issues (the design is correct but real data revealed scale problems).
  • Cross-browser bugs (the design is correct but rendering differs).
  • Accessibility findings during audit.
  • Stakeholder feedback after seeing the build.

For these, the goal isn't zero development iteration; it's minimizing it. A well-designed project has few surprises during build.

Worked example: a feature that went well

A team designs a new dashboard:

  • Week 1: sketches, structural review.
  • Week 2: clickable Figma prototype, 5 user interviews. Surfaces that one widget is misunderstood; redesign.
  • Week 3: refined prototype, engineering pairing session. Engineers identify a data-fetching constraint; design adapts.
  • Week 4: design handoff with documented edge cases.
  • Week 5–6: engineering build. Two minor design tweaks during build (acceptable rework).
  • Week 7: ship. Beta cohort happy.

The 4 weeks of design iteration prevented what would have been 4–8 weeks of development rework if the team had skipped to engineering.

Worked example: a project that went poorly

The same team rushes a feature:

  • Week 1: high-fidelity Figma mockup of the "final design."
  • Week 2–4: engineering build.
  • Week 5: QA finds the user can't complete the core task. Major redesign.
  • Week 6–10: rebuild. Ships.
  • Week 11: users report it's confusing. Patch ships.
  • Week 12+: ongoing churn.

The "saved" 3 weeks of design iteration cost 8+ weeks of development iteration plus user-trust damage.

Heuristics

  1. The "where did we discover this issue?" retrospective. After each project, list the issues that were discovered. For each, ask where it could have been caught cheaply. Patterns emerge.
  2. The fidelity-vs-question check. For each design decision, ask: what's the cheapest prototype that answers this? Use that.
  3. The engineering-pairing audit. Across recent projects, was engineering involved during design? Projects where they weren't usually had more development iteration.
  • iteration (parent).
  • iteration-prototype-fidelity — picking the right fidelity for each cycle.
  • prototyping — the technique that enables design iteration.
  • weakest-link — early iteration finds the weakest link cheaply.

© hashgraph-online, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in plugins/HDeibler/universal-design-principles/plugins/process-and-robustness-principles/skills/iteration-design-vs-development of hashgraph-online/awesome-codex-plugins.

  • SKILL.md
  • references/cost-of-late-change.md

Open the folder on GitHubat commit 9e7b281

Compare with similar skills

Iteration Design Vs Development next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Iteration Design Vs Development compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Iteration Design Vs Development this skillhashgraph-online/awesome-codex-plugins1.3k—~1.6kAutomated safety check: PassApache-2.0
Weekly Engineering Retrogarrytan/gstack136k—~2.4kAutomated safety check: PassMIT
Dough Execute Planterryyin/lizard2.6k—~4.3kAutomated safety check: PassCustom licence
Oral Paper SkillAdkid-Zephyr/oral-paper-skill350—~1.9kAutomated safety check: PassNone
Deck Retroasheshgoplani/agent-deck1k—~1.8kAutomated safety check: PassMIT
Dough Execution Retrospectiveterryyin/lizard2.6k—~4kAutomated safety check: PassCustom licence

Similar skills

  • Weekly Engineering Retro

    garrytan/gstack

    Builds a weekly engineering retrospective from git history: commit counts, per-person contributions, work patterns and code quality numbers over a chosen window.

    136k GitHub stars~2.4k tokensUpdated today
    Product & Project ManagementAuto-check passed

  • Dough Execute Plan

    terryyin/lizard

    Executes one selected story or bounded retrospective correction through an executable plan, or one authorized planless slice from a selected simple story or a contextual instruction, with…

    2.6k GitHub stars~4.3k tokensUpdated 2 days ago
    Product & Project ManagementAuto-check passed

  • Oral Paper Skill

    Adkid-Zephyr/oral-paper-skill

    Help authors learn from exemplary ICLR, ICML, and NeurIPS papers through source-linked manuscript comparisons, concrete writing and experiment suggestions, and guided reflection.

    350 GitHub stars~1.9k tokensUpdated 21 days ago
    Product & Project ManagementAuto-check passed

  • Deck Retro

    asheshgoplani/agent-deck

    Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs.

    1k GitHub stars~1.8k tokensUpdated 3 days ago
    Product & Project ManagementAuto-check passed

  • Dough Execution Retrospective

    terryyin/lizard

    Reviews planned, completed planless quick, or quick-to-planned execution against original intent, aggregate commits, current whole-product architecture, and tests, including after cleanup.

    2.6k GitHub stars~4k tokensUpdated 2 days ago
    Product & Project ManagementAuto-check passed

  • Criticism Self Criticism

    HughYau/qiushi-skill

    批评与自我批评：在工作完成、阶段验收、收到批评或同类错误反复出现时，对成果和过程做诚实、具体、基于事实的审视，输出可执行的改进项，并处理外来批评而不辩解。触发信号包括 review、复盘、审查、"帮我看看有没有问题"、"你确定吗"；任务刚开始或只是单步查询时不触发。

    3.8k GitHub stars~423 tokensUpdated 8 days ago
    Product & Project ManagementAuto-check passed

More from hashgraph-online/awesome-codex-plugins

All 714 skills in this repo

  • Anime Reaction Gif

    hashgraph-online/awesome-codex-plugins

    Create original anime-style reaction stickers as looping GIFs and MP4 previews, using generated character pose sheets and timed key poses.

    1.3k GitHub stars~922 tokensUpdated today
    Auto-check passed

  • Calibredb

    hashgraph-online/awesome-codex-plugins

    Manage and query Calibre libraries with the calibredb CLI (local paths or Calibre Content server URLs).

    1.3k GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Rust API Test Harness

    hashgraph-online/awesome-codex-plugins

    A skill your agent uses when adding, changing, testing, or debugging Rust HTTP APIs and services, especially when Codex needs black-box integration tests, random-port app startup, real database test…

    1.3k GitHub stars~1.7k tokensUpdated today
    Auto-check passed

  • Art

    hashgraph-online/awesome-codex-plugins

    Make a studio's game look like something at build time — a cover from a real frame of the game (free), painted covers, backdrops, textures and character plates from image models through the…

    1.3k GitHub stars~2.4k tokensUpdated today
    Auto-check passed

  • Calle

    hashgraph-online/awesome-codex-plugins

    Use CALL-E from Codex through the calle CLI. An agent skill from hashgraph-online/awesome-codex-plugins.

    1.3k GitHub stars~2.9k tokensUpdated today
    Auto-check passed

  • Game Balance Economy

    hashgraph-online/awesome-codex-plugins

    Balance game difficulty, resources, rewards, probability, progression, economies, and dominant strategies.

    1.3k GitHub stars~618 tokensUpdated today
    Auto-check passed

Categories

Questions about Iteration Design Vs Development

What does Iteration Design Vs Development do?

A skill your agent uses when reviewing where in the project lifecycle iteration is happening — desirable iteration during design vs. Iteration Design Vs Development is an agent skill from hashgraph-online/awesome-codex-plugins. Use this skill when reviewing where in the project lifecycle iteration is happening — desirable iteration during design vs.

When should I use Iteration Design Vs Development?

Iteration Design Vs Development fits situations like: reviewing where in the project lifecycle iteration is happening — desirable iteration during design vs; A project keeps slipping due to design changes during build; scoping how much design work to do before engineering begins; retrospectives reveal that issues were caught too late.

How do I install Iteration Design Vs Development in Claude Code?

Run `npx skills add hashgraph-online/awesome-codex-plugins --skill iteration-design-vs-development -a claude-code`. Or copy the skill folder (plugins/HDeibler/universal-design-principles/plugins/process-and-robustness-principles/skills/iteration-design-vs-development in hashgraph-online/awesome-codex-plugins) into .claude/skills/iteration-design-vs-development in your project. Claude Code loads it when a task matches its description.

How do I install Iteration Design Vs Development in Codex?

Run `npx skills add hashgraph-online/awesome-codex-plugins --skill iteration-design-vs-development -a codex`. Or copy the skill folder (plugins/HDeibler/universal-design-principles/plugins/process-and-robustness-principles/skills/iteration-design-vs-development in hashgraph-online/awesome-codex-plugins) into .agents/skills/iteration-design-vs-development in your project. Codex loads it when a task matches its description.

Can I use Iteration Design Vs Development in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hashgraph-online/awesome-codex-plugins --skill iteration-design-vs-development -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/iteration-design-vs-development, .gemini/skills/iteration-design-vs-development, .github/skills/iteration-design-vs-development and .opencode/skills/iteration-design-vs-development in your project.

What does Iteration Design Vs Development need to run?

SKILL.md names no scripts, command-line tools or credentials: Iteration Design Vs Development is instructions for the agent only.

Does Iteration Design Vs Development access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Iteration Design Vs Development safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Iteration Design Vs Development use?

Iteration Design Vs Development is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Iteration Design Vs Development use?

About 1.6k tokens (SKILL.md is roughly 6.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 668 tokens, read only when the agent opens those files.

What are the alternatives to Iteration Design Vs Development?

Skills that share tags, products or a category with Iteration Design Vs Development: Weekly Engineering Retro (garrytan/gstack, 136k stars), Dough Execute Plan (terryyin/lizard, 2.6k stars), Oral Paper Skill (Adkid-Zephyr/oral-paper-skill, 350 stars) and Deck Retro (asheshgoplani/agent-deck, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Iteration Design Vs Development?

hashgraph-online (a GitHub organization) maintains it in hashgraph-online/awesome-codex-plugins, which has 1,255 GitHub stars. The repository holds 714 skills in this directory. The repository was last updated on October 9, 2026.

Source: hashgraph-online/awesome-codex-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.