iterative-engineering

A collection of development workflows that guide brainstorming, research, design exploration, technical planning, code review, test-driven development, and pull-request feedback. TDD means writing tests around expected behavior while developing the code.

In plain words
What is it for?
Use it to explore designs, make implementation plans, develop with tests, run reviews using multiple agents, and resolve pull-request feedback.
Why use it?
It gives developers structured steps and specialist reviews for moving from an idea to tested, reviewable changes.

Plugin for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add plugins/tmchow/tmc-marketplace/iterative-engineering
Claude Code
/plugin marketplace add tmchow/tmc-marketplace
Clone the repo
git clone --depth 1 https://github.com/tmchow/tmc-marketplace

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

iterative-engineering scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/iterative-engineering/.claude-plugin/plugin.json · 23 lines

What it actually says

{
  "name": "iterative-engineering",
  "version": "1.16.1",
  "description": "Iterative development workflows. 13 agents, 12 skills for brainstorming, research, design exploration, tech planning, multi-agent reviews, TDD execution, and PR feedback resolution.",
  "author": {
    "name": "Trevin Chow",
    "url": "https://trev.in"
  },
  "repository": "https://github.com/tmchow/tmc-marketplace",
  "license": "MIT",
  "keywords": [
    "workflow",
    "brainstorming",
    "research",
    "design-exploration",
    "planning",
    "code-review",
    "tdd",
    "multi-agent",
    "iterative"
  ]
}
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 23 lines scan A 0b24228fd6ce

Subscribe to this mod's changes

iterative-engineering is a plugin published in the GitHub repository tmchow/tmc-marketplace (22 stars, last pushed 5mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.