defining-tech-stack

To define a tech stack from an MVP PRD, ingest the document alongside a frontend blueprint to extract constraints. The skill guides architecture decisions through one-question-at-a-time prompts to determine appropriate backend technologies and outputs a finalized stack-definition.md.

Choosing backend technologies for frontend compatibility requires applying constraints for scalability, security, and hosting. The skill detects these constraints from your frontend blueprint and PRD, avoiding speculative or trendy technology choices to finalize the stack.

Document architecture decisions during the requirements-gathering stage by resolving ambiguities through targeted clarifications. The skill processes your draft PRD to confirm supporting technologies and publishes the final stack in a single source of truth file named stack-definition.md.

Yes, you can finalize a tech stack even with unresolved ambiguities in your MVP PRD. The skill runs constraint detection and asks one question at a time to resolve these gaps before confirming the appropriate backend and supporting technologies.

You should avoid trendy technologies for project architecture when defining a stack at the requirements-gathering stage. The skill explicitly avoids speculative choices, ensuring your backend and supporting technologies satisfy constraints for frontend compatibility, scalability, and security instead.