Technical Decision Framework

Document architecture decisions using ADR templates with context and trade-offs.

17|2|Updated Oct 19, 2025

Search Tags:#template #architecture #documentation #adr #consultation #decision-record

Ready to run

npx skills add https://github.com/kcwoodfield/LifeOS-OSS --skill technical-decision-framework

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Technical Decision Framework
Source: https://github.com/kcwoodfield/LifeOS-OSS/tree/main/.claude/skills/tech-decision
Command: npx skills add https://github.com/kcwoodfield/LifeOS-OSS --skill technical-decision-framework

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill provides a structured approach to capturing architecture decisions using ADR templates, ensuring context, rationale, and traceability are preserved for future reference.

Core Features & Use Cases

Structured ADR generation: Guides users through the ADR sections (Context, Decision, Options, Rationale, Consequences, Implementation, Validation, References).
Sequential numbering & organization: Automatically assigns ADR-XXX numbers and stores them under decisions/.
Agent integration & templates: Integrates with domain-specific agents to gather inputs and fill templates consistently.

Quick Start

Create an ADR in decisions/ for a defined decision using the standard ADR template.

Frequently Asked Questions about Technical Decision Framework

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

FAQPage Schema

How do I document architecture decisions to capture context and trade-offs?▼

You document architecture decisions by generating an Architecture Decision Record (ADR) that captures context, options, rationale, consequences, implementation, and validation for future traceability.

What sections should be included in an ADR template for software engineering?▼

An ADR template should include context, decision, options, rationale, consequences, implementation, validation, references, and notes to satisfy the full ADR framework requirements for architecture decisions.

How do I create and organize architecture decision records sequentially?▼

You create architecture decision records in a decisions/ directory, where the framework automatically assigns sequential ADR-XXX numbers to organize and store each documented architecture decision.

Can I use ADR documentation for both frontend and backend architecture decisions?▼

Yes, ADR documentation applies to backend, frontend, and cross-cutting architecture decisions, supporting iterative refinement and consultation with domain experts to capture trade-offs accurately.

What is the best way to capture rationale and consequences for architecture decisions?▼

The best way to capture rationale and consequences is through a structured ADR template that guides you through documenting context, options, and trade-offs to preserve traceability for future reference.

Does this ADR framework support consultation with domain experts during decision recording?▼

Yes, the ADR framework supports consultation with domain-specific experts and integrates with agents to iteratively refine inputs and consistently fill architecture decision templates.