10x-tech-stack-selector

Recommends a starter template and tech stack from a PRD via a curated registry.

Updated May 23, 2026
One-click install
npx skills add https://github.com/BMS-kmusial/bms-stream-monitor --skill 10x-tech-stack-selector-bms-kmusial
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 10x-tech-stack-selector
Source: https://github.com/BMS-kmusial/bms-stream-monitor/tree/main/.claude/skills/10x-tech-stack-selector
Command: npx skills add https://github.com/BMS-kmusial/bms-stream-monitor --skill 10x-tech-stack-selector-bms-kmusial

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Choosing a tech stack for a greenfield project is slow and error-prone, especially when the choice must also work well with AI coding agents. This Skill turns a written PRD into a vetted starter recommendation and a machine-readable hand-off file that a downstream bootstrapper can consume to scaffold the project. ## Core Features & Use Cases - PRD-driven recommendation: Reads context/foundation/prd.md frontmatter (product_type, target_scale, timeline_budget) and functional requirements as decision priors, refusing to run without the file on disk. - Two decision paths: A standard path that short-circuits to a vetted recommended default for the (product_type, language_family) cell, and a custom path that walks a residual interview covering features, team profile, preferences, deployment, CI/CD, and a five-point self-check. - Quality-gated registry: Reasons over a language-aware starter registry (JS, Python, Ruby, Java, Go, Rust, PHP, .NET, Dart) applying four agent-friendly gates: typed, convention-based, popular in training data, and well-documented. - Use Case: After finishing a PRD for a solo SaaS MVP, invoke the Skill to get a recommended starter (e.g., an Astro + Supabase + Cloudflare stack), confirm deployment and CI choices, and receive a tech-stack.md hand-off ready for scaffolding. ## Quick Start Ask the assistant to pick a tech stack for your project based on the PRD at context/foundation/prd.md.

Frequently Asked Questions about 10x-tech-stack-selector

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose a tech stack for a new project from a PRD?

Invoke the Skill after writing your PRD at context/foundation/prd.md. It reads the PRD's product type, scale, and timeline, then either offers a vetted recommended starter for your product type and language family or walks a short interview to design a custom stack.

What starters and frameworks does the registry cover?

The registry covers about 25 starters across nine language families, including Next.js, Astro, T3, Hono, Fastify, Django, FastAPI, Rails, Spring Boot, Laravel, Go, Axum, Tauri, Flutter, Expo, and .NET, each with quality-gate booleans and deployment defaults.

Can I use it without a PRD file on disk?

No. The PRD is a hard precondition. If context/foundation/prd.md is absent, the Skill stops and redirects you to run the shape and PRD skills first; it does not fall back to conversation context for substitute priors.

What are the agent-friendly quality gates?

Each starter is assessed on four criteria: typed contracts, convention-based structure, popularity within its language family's training data, and current documentation. Candidates failing any gate are excluded from unprompted recommendations, though users can override with a recorded quality_override flag.

What happens after the stack is selected?

The Skill writes context/foundation/tech-stack.md containing the starter_id, package manager, project name, and hints such as deployment target, CI provider, and feature flags. It then points you to run the bootstrapper skill, which consumes that file to scaffold the project.

When should I not use this stack selection skill?

Skip it when working mid-implementation on an existing codebase, such as adding a library or replacing a single dependency. It is designed only for greenfield stack selection after a PRD exists, not for incremental technology decisions.