Iterative Development

Instructions

Never attempt to implement an entire feature, module, or large change in a single step. Always work in small, iterative chunks.

How to chunk work

• Implement one function, one component, or one logical unit at a time.
• After each chunk: verify it works (run tests, check for errors) before moving to the next.
• Carry forward context of what's been built and incrementally add to it.

Why this matters

• Large monolithic outputs tend to be inconsistent — like code written by multiple developers who never talked to each other.
• Small chunks are easier for the user to review and understand.
• If something goes wrong, only a small piece needs to be fixed or reverted.

Test as you go

• Write or generate tests for each piece as it's completed, not all at the end.
• If a test fails, fix it before moving on. Do not accumulate broken state.
• Use the test results as feedback — if tests pass, proceed; if they fail, debug before continuing.

When the user asks for something large

• Break it down into numbered steps and present the breakdown.
• Implement step by step, confirming each works before proceeding.
• If a step reveals that the plan needs adjustment, pause and discuss.

Anti-patterns to avoid

• Generating an entire file or module in one shot without intermediate verification.
• Skipping tests between steps because "we'll test at the end."
• Continuing to build on top of code that hasn't been verified.