What problem does it solve?
It prevents slow, failure-prone iteration cycles when building the next version of a NestJS/Next.js feature by moving the critical scope, guardrails, and correctness checks to the main thread before parallel agent implementation.
Core Features & Use Cases
- API mode iteration: Builds the next iteration by adding domain entities, endpoints, and load-bearing business logic on top of a minimal NestJS scaffold, with RED-first tests written before delegation.
- Frontend mode iteration: Builds the next iteration of a Next.js/Vite UI from HTML/image mockups while consuming the existing API surface, focusing on state-machine/client logic where load-bearing behavior exists.
- Iteration-aware deltas: Detects whether v1 or v2+ already exists and applies changes as deltas rather than rewrites.
- Simplicity governor: Aggressively cuts ceremony by default (e.g., avoiding config modules, DI tokens, validation pipes, UI kits) unless the plan explicitly says otherwise.
Quick Start
Use the command /iteration-impl and describe the iteration you want to build (or provide a problem statement after /launch-light), then type go when prompted to lock ambiguities and start the RED-test phase.
