prd-v05-technical-stack-selection

To decide on tech stack components, evaluate each required capability against Build, Buy, Integrate, or Research options using a structured decision framework. This generates TECH- entries documenting rationale, trade-offs, and cost estimates to guide architecture design.

A technical stack selection framework systematically determines the optimal technology for a product based on features and constraints. It codifies judgments across frontend, backend, database, auth, and infrastructure to ensure consistent architecture choices during PRD reviews.

You document technology trade-offs and cost estimates by generating structured TECH- entries. These entries link decisions to FEA- features and SCR- screens artifacts, capturing the rationale needed to align stakeholders on architecture choices during PRD milestones.

You should use a structured decision framework during the v0.5 Risk Discovery phase of a PRD review. Applying it at this stage ensures every product capability is evaluated with consistent criteria before downstream architecture design begins.

Yes, the technical stack selection process applies to AI, infrastructure, frontend, backend, database, and auth decisions. It categorizes options with clear criteria to evaluate Build, Buy, Integrate, or Research choices for any required product capability.

Technical stack selection links directly to existing PRD artifacts like FEA- features and SCR- screens. Having these product workflow artifacts ensures the technology decisions align with defined PRD milestones and feed properly into architecture design.