tech-decision

Document technology choices and rationale in Architecture Decision Records with enforced templates.

309|58|Updated Apr 16, 2026

Search Tags:#architecture #documentation #adr #traceability #decision-record #tech-selection

Ready to run

npx skills add https://github.com/bkywksj/knowledge-base --skill tech-decision-bkywksj

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tech-decision
Source: https://github.com/bkywksj/knowledge-base/tree/main/.claude/skills/tech-decision
Command: npx skills add https://github.com/bkywksj/knowledge-base --skill tech-decision-bkywksj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The tech decision recording skill enables teams to systematically capture, discuss, and preserve rationale behind technology choices, ensuring consistent decisions across projects.

Core Features & Use Cases

Architecture Decision Records (ADR) templates for recording context, constraints, alternatives, decisions, and impact.
Versioned decision logs with traceability to stakeholders, dates, and outcomes.
Use Case: For new projects, platform migrations, or toolchain changes where architecture decisions must be audited and revisited.

Quick Start

Create an ADR entry to capture the rationale, alternate options, and expected impact of choosing a new logging framework.

Frequently Asked Questions about tech-decision

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

FAQPage Schema

How do I document architecture decisions to maintain traceability across software projects?▼

You can document architecture decisions using Architecture Decision Records to capture context, constraints, alternatives, decisions, and impact, ensuring traceability across software architectures. This approach systematically preserves the rationale behind technology choices for auditing and revisiting.

What is an Architecture Decision Record and when do I need one for tech selection?▼

An Architecture Decision Record is a formal log entry capturing the rationale, alternatives, and expected impact of a technology selection. You need an ADR for new projects, platform migrations, or toolchain changes where architecture choices must be audited and consistently recorded.

How do I create an ADR entry to capture the rationale and alternatives for a new framework?▼

To create an ADR entry, apply the enforced template to document the background, constraints, alternatives, decision, and impact of choosing a new framework. This ensures consistent recording of the rationale and expected outcomes for stakeholders.

Can I use ADRs for platform migrations and toolchain changes to track decision outcomes?▼

Yes, you can use Architecture Decision Records for platform migrations and toolchain changes. They enforce versioned decision logs with traceability to stakeholders, dates, and outcomes, allowing teams to systematically capture and revisit technology choices during major architecture transitions.

What is the best way to ensure consistent architecture decision logs across multiple engineering teams?▼

The best way to ensure consistent architecture decision logs is to enforce a standardized ADR template covering background, constraints, alternatives, decision, and impact. This enables teams to systematically capture, discuss, and preserve the rationale behind technology choices consistently.

What should I include in an ADR template for a formal architecture assessment?▼

An ADR template for a formal architecture assessment should include background, constraints, alternatives, the final decision, and expected impact. This structure enforces consistent recording of technology choices, rationale, and traceability needed for software architecture evaluations.