dev-workflow

A scoped development workflow requires reading docs and architecture references first, then proposing a small design that limits code changes to 1–3 files per iteration. This approach ensures modifications remain safe, properly documented, and aligned with the project roadmap.

The best way to plan feature implementation is to read docs/roadmap.md and related architecture references, identify affected modules, and outline a concise 1–3 file change plan using the standard development workflow before writing any code.

To limit code changes during refactoring, enforce a strict 1–3 file change limit per iteration and propose a small scoped design based on roadmap documentation. This keeps iterations safe by verifying affected modules before coding and maintaining proper documentation.

A lean development workflow requires reading docs/roadmap.md and architecture references first to propose properly scoped, well-documented changes. Reading documentation before coding ensures you adhere to roadmap scope and verify affected modules accurately.

Yes, you need to check docs/roadmap.md before modifying functionality to respect version scope and verify affected modules. A standard development workflow requires reading related architecture references to propose a small scoped design before coding.

The 1–3 file change limit restricts iterations to small scoped changes, preventing large refactors in a single pass. This constraint ensures safety and proper documentation but requires breaking down feature implementation into multiple smaller iterations aligned with the roadmap.