iterate
Iterate
Coordinate refinement and implementation in one living development workflow. An increment is a coherent change validated against agreed behavior. Group related decisions into a batch, implement it, and let the result decide what comes next. Settle decisions just in time: the ones the current batch needs, and no further. The application evolves in place from its first runnable batch; replacing it is a consequential decision for the user.
The project documents and their rules are in project-documents.md; its terms (authorized, obligation, lazy, pointer) apply throughout. This workflow runs on the backlog, working state, and the changelog with light records, and links existing requirements and specifications where they apply.
1. Establish the starting point
Read applicable repository instructions, startup and verification configuration, relevant requirements and specifications, and the project documents. Inspect code and decisions before asking questions the workspace can answer.
When working state names an approved focus, resume it with its constraints and prerequisites.
For a new project, establish who will use it, where it runs, whether it keeps important data, and the first useful interaction. Ask only what choosing an approach and the first batch requires. For an existing project, keep its current approach and recover the pending batch.
When competing capabilities, unclear scope, or cross-cutting dependencies make choosing a useful batch premature, choose a focus first following prioritize.md, with the known direction, constraints, and document pointers, and tell the user why. Implement once the user approves its recommended focus and material deferrals. A clear small change goes straight on. Return to this branch when priorities or dependencies block the next batch; each new outcome needs its own approval.
Completion: project-documents.md was read, the backlog, working state, and changelog were read or noted as absent, and intended use, immediate constraints, and the next decisions are explicit. Unrelated future behavior may remain open.