tech-stack

Guides technology selection and documents tech stack decisions using weighted scoring matrices.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/Samind-Samind/projexa --skill tech-stack-samind-samind
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-stack
Source: https://github.com/Samind-Samind/projexa/tree/main/.claude/skills/tech-stack
Command: npx skills add https://github.com/Samind-Samind/projexa --skill tech-stack-samind-samind

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Choosing technologies for a project often relies on guesswork or undocumented assumptions. This Skill enforces a rigorous, human-in-the-loop process for selecting and documenting the Projexa tech stack (Frontend, Backend, Database, File Storage, Auth, AI Integration, Hosting) so every decision is grounded in real project data and explicit user confirmation. ## Core Features & Use Cases - Structured Interviewing: Intensively questions the user about development mode, deployment targets, budget, NFRs, and constraints, never guessing when information is missing from project documents. - Weighted Scoring Analysis: Compares at least 5 technology options per layer using a Weighted Scoring Model / Trade-off Matrix with pros and cons, always showing results for review before writing files. - Document Generation: Delegates finalized decisions to a tech-stack-writer sub agent that writes docs/02-design/02-technical/tech-stack.md, updates the technical index, and optionally syncs section 11 of the system design document. - Use Case: When starting the Projexa technical design phase, run this Skill to interview stakeholders, score database and hosting options against confirmed requirements, and produce a Confirmed/Draft-status decision document. ## Quick Start Ask the assistant to help select and document the tech stack for the Projexa project, comparing options for the layers you specify.

Frequently Asked Questions about tech-stack

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

FAQPage Schema
How do I choose a tech stack for a software project systematically?▼

Use a weighted scoring model: define criteria and weights from confirmed project requirements, score at least five candidate technologies per layer, and compare weighted totals with pros and cons. This Skill enforces that process and records decisions in a tech-stack.md document.

What is a weighted scoring model for technology comparison?▼

A weighted scoring model assigns weights to decision criteria (cost, maintainability, team skill, deployment fit) and scores each technology option against them. The weighted sum ranks options objectively, and the criteria and weights are shown to stakeholders before scoring begins.

How to document technology decisions in a design document?▼

Record each layer's decision with status (Confirmed with date, or Draft suggested), the scoring table, pros and cons per option, and comparison against any prior proposal. This Skill writes that structure to docs/02-design/02-technical/tech-stack.md via a writer sub agent.

Can the AI decide the tech stack without asking the user?▼

No. The Skill forbids guessing when project documents lack information; it must interview the user with multi-option questions. Only if the user explicitly delegates evaluation to the AI may it proceed, and such assessments are labeled as AI-evaluated in the document.

What happens when new analysis conflicts with an existing tech proposal?▼

The Skill compares results against the prior proposal in the system design document and asks the user to choose: update the original table, keep both versions cross-linked, or defer the decision pending formal confirmation.