feature-design

Collaborative feature design is facilitated through structured discussions, clarifying questions, and requirement capture to align team goals and prevent design drift. It produces a design document containing the problem statement, requirements, and trade-offs.

You need to create an ADR for feature design when starting a new feature or undertaking a major refactor that requires upfront exploration and trade-off analysis. ADR-driven decisions enforce gate checks to ensure architectural alignment before implementation.

The best way to capture requirements and prevent design drift is by enforcing gate checks and generating a formal design document during collaborative sessions. This approach forecloses misalignment by explicitly recording problem statements and trade-offs before coding.

You manage gates and context for downstream planning and implementation by applying ADR documentation and context loading during the design phase. This preparation ensures the transition into the plan, implement, and validate phases is guided by approved artifacts.

Yes, feature design works for both new features and major refactors that require upfront exploration and trade-off analysis. It facilitates the structured design conversations and ADR-driven decisions necessary to guide implementation in either scenario.