tech-stack-skill

Enforce approved technology choices and log exceptions against the company tech catalog.

Updated Mar 2, 2026

Search Tags:#architecture #governance #tech-stack #decision-tracking #approved-technologies #exception-process

Ready to run

npx skills add https://github.com/dacy/architect-skill --skill tech-stack-skill

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tech-stack-skill
Source: https://github.com/dacy/architect-skill/tree/main/.claude/skills/tech-stack-skill
Command: npx skills add https://github.com/dacy/architect-skill --skill tech-stack-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps teams align technology choices with the company-approved stack to avoid drift and rework during technology decisions.

Core Features & Use Cases

Tech stack guidance: Refers to the approved catalog and captures exceptions when needed.
Decision traceability: Documents runtime language, framework, API style, databases, caching, infrastructure, CI/CD, and observability decisions with appropriate tiers.
Use Case: When evaluating a language or framework, consult the skill to verify alignment and record exception requests if necessary.

Quick Start

Review a project’s tech decisions against the approved stack and log any required exceptions following the stated process.

Frequently Asked Questions about tech-stack-skill

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

FAQPage Schema

How do I enforce approved technology choices to prevent architecture drift?▼

To track tech stack decisions with traceability, document runtime languages, frameworks, API styles, messaging, databases, caching, UI, infrastructure, CI/CD, and observability choices with appropriate tiers. This skill captures these decisions and records exception requests when needed.

How do I request an exception for a technology not in the approved stack?▼

Tech stack governance covers runtime languages, frameworks, API styles, messaging, databases, caching, UI, infrastructure, CI/CD, and observability. This scope ensures all architectural layers across projects are evaluated for alignment with company standards.

What is the best way to review a project's technology decisions against company standards?▼

The best way to review tech decisions is to compare runtime, framework, database, and infrastructure choices against the approved stack catalog. This skill verifies alignment across all architectural tiers and logs any required exceptions following the documented process.

When do I need to document an exception for an unapproved framework or database?▼

You need to document an exception when a project requires a framework or database outside the approved tech stack. This skill captures exception requests during technology evaluation to maintain traceability and prevent untracked architecture drift.