skills.rest
daddia
daddiaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

write-tech-stack

Document technology stack choices and trade-offs into tech-stack.md from product.md and solution.md.

1|Updated Apr 25, 2026
Search Tags:#architecture#documentation#adr#cloud#engineering#tech-stack#decision-records
One-click install
npx skills add https://github.com/daddia/space --skill write-tech-stack
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-tech-stack
Source: https://github.com/daddia/space/tree/main/.agents/skills/write-tech-stack
Command: npx skills add https://github.com/daddia/space --skill write-tech-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architects and engineering teams often struggle to capture and communicate technology decisions for a product or domain, leading to misalignment and long-term maintenance challenges.

Core Features & Use Cases

  • Define technology domains and chosen tools with explicit rationales and trade-offs to guide implementation.
  • Align architecture decisions with ADRs and product constraints, ensuring traceability across cycles.
  • Produce a concise tech-stack.md that can be reviewed by engineers, ops, and stakeholders.

Quick Start

Generate a tech-stack.md for your product by running this skill with your current project scope.

Frequently Asked Questions about write-tech-stack

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

FAQPage Schema
How do I document technology stack decisions for a new product architecture?▼

Document tech stack choices by defining architecture domains with rationales and trade-offs across standard categories. This approach ensures alignment with product constraints and produces a structured tech-stack.md file for engineering and stakeholder review.

What is the best way to align architecture decisions with ADRs?▼

Align architecture decisions with ADRs by generating a tech-stack.md that references decision records alongside categorized tool choices. This ensures traceability between engineering implementation and documented product constraints.

When do I need to document tech choices for cloud engineering projects?▼

Document tech choices at project start or when adopting significant new technology. Capturing these decisions explicitly prevents misalignment and mitigates long-term maintenance challenges across cloud engineering teams.

Can I generate a tech-stack document if I only have product.md available?▼

Yes, you can generate a tech-stack document by consuming product.md as the primary input scope. If solution.md is also available, it will be incorporated to further refine the architecture domains and categorized technology choices.

Why does my engineering team struggle with technology stack traceability?▼

Engineering teams struggle with technology stack traceability when architects fail to capture and communicate technology decisions clearly. Producing a concise tech-stack.md with categorized choices and ADR references resolves this misalignment.

Related Skills

Explore More Software Engineering Skills→
daddiadaddia
1

plan-delivery

Plan the Phase-0 artefact sequence and generate a delivery-plan.md.

Community
Intermediate
LetPeopleWorkLetPeopleWork
16

architecture-patterns

Document architecture decisions and patterns using ADR templates.

Official
Basic
UnlimitedxIQUnlimitedxIQ

cto-advisor

Analyze architecture decisions and guide debt remediation for engineering organizations.

Community
Advanced
melikhanmutlumelikhanmutlu

architecture-decision-records

Create and manage architecture decision records using MADR templates and adr-tools.

Community
Advanced