gsd-cc-stack

Document language, framework, database, hosting, and tooling decisions in STACK.md and DECISIONS.md.

3|Updated Mar 23, 2026

Search Tags:#planning #architecture #technology #stack #decision-making #stakeholders

Ready to run

npx skills add https://github.com/0ui-labs/GSD-CC --skill gsd-cc-stack

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-cc-stack
Source: https://github.com/0ui-labs/GSD-CC/tree/main/gsd-cc/skills/stack
Command: npx skills add https://github.com/0ui-labs/GSD-CC --skill gsd-cc-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tech teams struggle to align on technology choices, track rationales, and maintain consistent decisions across projects. This Skill guides a structured discussion, records tradeoffs, and ensures decisions are repeatable.

Core Features & Use Cases

Step-by-step stack discussion covering language, framework, database, hosting, and tooling.
Supports manual and auto-discussion modes with documentation outputs (.gsd/STACK.md and .gsd/DECISIONS.md).
Use during project seeds, architecture reviews, or when decisions must be revisited with stakeholders.

Quick Start

Run /gsd-cc-stack to begin a structured stack discussion and document decisions in .gsd/STACK.md

Frequently Asked Questions about gsd-cc-stack

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

FAQPage Schema

How do I document tech-stack decisions for a software project?▼

Documenting tech-stack decisions involves recording language, framework, database, hosting, and tooling rationales. This Skill guides structured discussions to capture tradeoffs and generates revision-ready STACK.md and DECISIONS.md files for stakeholders.

What is the best way to align stakeholders on technology choices?▼

Aligning stakeholders on technology choices requires structured, explainable decision-making. This Skill supports manual and auto-discussion modes to guide stack discussions, ensuring decisions are repeatable and tradeoffs are recorded for stakeholder reviews.

When do I need a structured architecture review for my project?▼

You need a structured architecture review during project seeds, when revisiting decisions with stakeholders, or when maintaining consistent tech-stack choices. This Skill facilitates these reviews to ensure alignment and tracks rationales across the project lifecycle.

Can I use this for manual and automated stack discussions?▼

Yes, this Skill supports both manual and auto-discussion modes for tech-stack decisions. It guides step-by-step discussions across your stack and updates .gsd/STATE.md alongside generating documentation outputs.

How do I track rationales for framework and database selections?▼

To track rationales for framework and database selections, you record tradeoffs during structured discussions. This Skill generates a DECISIONS.md file that captures the reasoning behind your technology choices, making them repeatable and revision-ready.