tech-selection

Identify technology stacks that satisfy architecture drivers and document trade-offs.

1|Updated Mar 17, 2026

Search Tags:#architecture #risk-mitigation #system-design #decision-record #technology-stack #tech-selection

Ready to run

npx skills add https://github.com/yknothing/prodcraft --skill tech-selection

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tech-selection
Source: https://github.com/yknothing/prodcraft/tree/main/skills/02-architecture/tech-selection
Command: npx skills add https://github.com/yknothing/prodcraft --skill tech-selection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aligns technology choices with architecture drivers to prevent drift and ad hoc tooling, reducing risk and rework.

Core Features & Use Cases

Define a clear decision surface that enumerates eligible categories (languages, frameworks, datastores, deployment platforms).
Compare options against architecture drivers, team capability, and operational burden.
Record consequences, trade-offs, and triggers for revisiting decisions.

Quick Start

Run tech-selection once architecture drivers are defined to pick the minimal, justified tech stack.

Frequently Asked Questions about tech-selection

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

FAQPage Schema

How do I choose the right technology stack for my system design?▼

To choose the right technology stack, compare eligible languages, frameworks, and datastores against known architecture drivers, team capability, and operational burden to document explicit choices with rationale and trade-offs.

What is the best way to align technology choices with architecture drivers?▼

The best way to align technology choices with architecture drivers is to define a clear decision surface that compares options against operational burden and team capability to prevent drift and ad hoc tooling.

How do I document trade-offs when selecting a tech stack?▼

You document trade-offs in technology stack selection by recording consequences, explicit choices, and triggers for revisiting decisions, ensuring the rationale behind each option is compared against architecture drivers.

When do I need a formal decision record for my tech stack?▼

You need a formal decision record for your tech stack when architecture drivers are known and teams must commit to concrete languages, frameworks, datastores, or deployment platforms to prevent drift and rework.

How do I evaluate operational burden when picking a deployment platform?▼

You evaluate operational burden by comparing eligible deployment platforms against known architecture drivers and team capability, ensuring the selected technology stack minimizes risk and reduces rework.