tech-stack-consult

Select an agStack backend profile and write stack.json plus an ADR.

1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/anicdh/agstack --skill tech-stack-consult
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-stack-consult
Source: https://github.com/anicdh/agstack/tree/main/.claude/skills/tech-stack-consult
Command: npx skills add https://github.com/anicdh/agstack --skill tech-stack-consult

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides teams and engineers to select the optimal agStack backend profile before scaffolding, preventing misalignment and wasted work.

Core Features & Use Cases

  • Five-question decision flow that evaluates workload, traffic, language, deployment, and real-time needs.
  • deterministic mapping to one of four profiles (nestjs-only, nestjs-rust, go-only, python-only) and writes the stack.json configuration.
  • Generates an ADR at docs/decisions/000-tech-stack.md to document the rationale for future reference and governance.

Quick Start

Answer the five questions in order to determine the best backend stack, then proceed to confirm and run /setup.

Frequently Asked Questions about tech-stack-consult

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

FAQPage Schema
How do I choose the best backend stack for a new project before writing code?

To choose the best backend stack before scaffolding, teams answer five structured questions evaluating workload, traffic, deployment, and real-time needs. This deterministic mapping process selects the optimal profile and writes the configuration to stack.json to prevent misalignment.

When should I use a NestJS and Rust backend architecture together?

A NestJS and Rust architecture is recommended when the five-question decision flow identifies high traffic, specific language skills, and real-time needs that warrant a hybrid profile. The process deterministically maps these workload and deployment constraints to the nestjs-rust profile.

How do I document the rationale for my tech stack decision?

Documenting tech stack rationale is handled by generating an Architecture Decision Record at docs/decisions/000-tech-stack.md. This ADR captures the governance and reasoning behind the selected profile, ensuring future reference and alignment after the stack.json is written.

Does this backend stack selection process write any application code?

No, the backend stack selection process does not scaffold or write any application code. It strictly enforces deterministic rules to output a stack.json configuration file and an ADR, leaving the actual scaffolding to subsequent setup steps.

What factors determine whether to use a Go or Python-only backend profile?

Go or Python-only backend profiles are determined by answering five questions about workload, traffic, team skills, deployment constraints, and real-time needs. The evaluation enforces deterministic rules to map these specific project requirements to the correct profile.

Can I use this decision flow to select a backend stack for non-agStack projects?

The decision flow is specifically designed to select the optimal backend profile for agStack projects before scaffolding. It writes configurations to .agstack/stack.json and generates an ADR, tailoring the deterministic workflow and output paths to the agStack ecosystem.