What problem does it solve?
Complex, ambiguous, or cross-cutting engineering changes often fail because implementation begins before the existing system, domain model, and lifecycle behavior are understood. This Skill structures collaboration so assumptions are tested against real code and lifecycles before momentum locks in a flawed design.
Core Features & Use Cases
- Shared Model Building: Establishes understanding of existing abstractions, tests, and lifecycle behavior before proposing or implementing designs.
- Proposal Evaluation: Treats designs as working models to be challenged, connecting abstract proposals to concrete lifecycles like creation, correction, reversal, and mixed old/new data.
- Bounded Increments and Resets: Breaks large changes into reviewable semantic increments and defines when to stop, reset, and rebuild from trusted assumptions.
- Use Case: When asked to refactor a billing entitlement lifecycle in a large codebase, use this Skill to first map current behavior and edge cases, present a testable design proposal, and implement in coherent increments with explicit review points.
Quick Start
Use the iterative-engineering-design skill to plan and implement this cross-cutting change, validating the design against existing system behavior before writing code.
