design-research

Creating a design document requires structured research planning that enforces a four-phase process: Request Understanding, Repository Analysis, Solution Exploration, and Recommendation. This approach ensures objectives, scope, and initial design options are clearly documented before any implementation begins.

Planning architectural changes requires a structured design process that includes codebase analysis and stakeholder requirement definition. By exploring multiple solutions and producing a documented research report, you ensure viable design options are evaluated before committing to complex refactors.

Repository analysis identifies existing codebase patterns by examining the current architecture during the design research phase. This analysis informs the solution exploration process, ensuring any proposed design options align with established requirements and technical constraints.

Yes, a structured design process manages stakeholder requirements and risk by enforcing documented frontmatter entries and clear success criteria during request understanding. This approach ensures all stakeholder needs are captured before architectural changes are recommended.

You need to write a research report when facing complex refactors or new features that require risk management and codebase analysis. Producing this report before implementation prevents rework by ensuring viable design options are fully explored and documented.