bee:pre-dev-trd-creation

To create a TRD, define how and where solutions will be architected by mapping component boundaries and data flows first. You then enforce design validation prerequisites for UI features before loading relevant Bee Standards to finalize the tech stack.

Technology-agnostic TRDs prevent vendor lock-in and premature coupling by focusing on architectural patterns instead of concrete products. This approach provides maximum flexibility and maintainability compared to committing early to specific databases or frameworks.

The technology stack is defined by auto-detecting or prompting for the primary technology to load relevant Bee Standards. This happens only after the technology-agnostic architecture patterns, component boundaries, and data flows are fully established.

You should avoid technology-agnostic architecture patterns when your project requires immediate implementation with a pre-selected, fixed technology stack, as the TRD process deliberately delays concrete product choices to prevent premature coupling and vendor lock-in.