shape

A design brief is generated by running a structured discovery interview to gather context on goals, stakeholders, and constraints, then codifying that output into actionable design direction and requirements for implementation.

A discovery interview is needed before planning UX to establish design direction, understand constraints, and define strategy, ensuring all product, design, and engineering teams have aligned requirements before any code is written.

The best way to plan UI before coding is to use a structured discovery phase that produces a design brief, guiding implementation by defining strategy and constraints upfront.

Yes, you can use this to gather context for UX planning by invoking a discovery interview that collects goals and constraints to inform the final design brief output.

Yes, planning a design brief requires invoking /impeccable to properly gather context and produce the final design brief for implementation.

You should not use a structured design brief approach if your feature planning phase is already complete or if implementation has already begun, as this process is designed to establish direction before any code is written.