tech-selection
Tech Selection
Choose technologies by architectural fit and operational consequence, not by habit or trend.
Context
Tech selection turns a structural design into a concrete stack. The right decision makes implementation straightforward and operations predictable. The wrong decision can hard-code skill gaps, cost surprises, and migration pain into the program.
Use this skill when the architecture is stable enough to evaluate real options. If the team skips explicit selection, those choices get made implicitly under delivery pressure and become harder to revisit.
Inputs
- requirements-doc -- The functional and non-functional requirements that constrain viable technology choices.
- architecture-doc -- The architecture drivers, boundaries, deployment model, and quality constraints the technologies must satisfy.
Process
Step 1: Define the Decision Surface
More from yknothing/prodcraft
system-design
Use when reviewed requirements or specifications are ready and the team must decide high-level architecture, component boundaries, integration seams, or brownfield coexistence strategy before API design, technology selection, or task planning.
6ci-cd
Use when a reviewed implementation slice needs an automated build, test, and deployment pipeline, especially when brownfield rollback, release-boundary checks, contract/integration gates, and staged delivery must be explicit before shipping.
6intake
The mandatory gateway for all new engineering work. Triage and route new products, apps, features, migrations, tech-debt, or any 'not sure where to start' request to the correct lifecycle path. Use before starting design or implementation. Do not use for ongoing tasks, specific debugging, or PR reviews.
6feature-development
Use when a reviewed task slice has tests or acceptance targets and the team must turn it into a small, mergeable implementation increment without expanding scope, breaking contracts, or hiding release-boundary risk.
6monitoring-observability
Use when a live service or newly delivered release needs actionable telemetry, dashboards, and alerts that expose real user-impactful boundaries, especially when brownfield coexistence rules, unsupported-flow safety, rollback health, or queue/backfill behavior must be visible before incidents escalate.
6incident-response
Use when a live production issue needs coordinated containment, severity triage, stakeholder communication, and evidence capture, especially when a recent release, brownfield coexistence rules, rollback decisions, or unresolved contract boundaries must be handled before root-cause work.
6