10x-tech-stack-selector

To choose a tech stack from a PRD, the system reads on-disk product requirements and applies a language-aware starter registry with quality gates. It matches your framework and toolchain to deployment and CI/CD constraints, outputting a structured hand-off file for scaffolding.

Yes, you can use a custom framework choice when no vetted default exists. The system runs a custom selection flow that performs bounded residual questioning to gather specific tech preferences, deployment targets, and CI/CD shapes, ensuring your custom stack meets quality standards.

Constraints needed to narrow tech stack candidates include feature audit, team profile, tech preferences and avoids, deployment target, CI/CD shape, framework variant, and an optional testing runner. These inputs ensure the recommended starter aligns with your project's operational environment.

The starter registry handles known framework friction options by applying agent-friendly quality gates. When you choose a high-friction toolchain, it surfaces specific tradeoffs and provides compensation guidance to help you navigate potential integration or deployment issues.

Yes, the tech stack selection output works directly with scaffolding tools by writing a context/foundation/tech-stack.md file. This structured hand-off document follows a required schema so downstream bootstrapper agents can reliably scaffold your greenfield project.

You should not use an automated tech stack selector for projects that are not greenfield or lack an on-disk PRD. The tool requires defined product requirements and frontmatter priors to initiate either a default or custom selection flow successfully.