justify-decision

Justify architectural and design decisions with evidence, context, and consequences.

1|Updated Mar 5, 2026

Search Tags:#architecture #decision making #design patterns #technical debt #ADR #justification

Ready to run

npx skills add https://github.com/baphled/dotopencode --skill justify-decision

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: justify-decision
Source: https://github.com/baphled/dotopencode/tree/main/skills/justify-decision
Command: npx skills add https://github.com/baphled/dotopencode --skill justify-decision

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured, evidence-based justification for architectural and design decisions, moving beyond opinion to defensible rationale.

Core Features & Use Cases

Architectural Decision Records (ADRs): Assists in creating well-documented ADRs by focusing on evidence, context, and consequences.
Technology Selection: Helps in choosing between libraries, frameworks, or tools by outlining supporting data and trade-offs.
Stakeholder Communication: Provides clear explanations for complex technical choices, making them understandable and defensible.

Quick Start

Use the justify-decision skill to provide evidence-based justification for choosing Elixir/Phoenix over Node.js for handling 10k concurrent WebSocket connections.

Frequently Asked Questions about justify-decision

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

FAQPage Schema

How do I write an Architectural Decision Record with evidence-based justification?▼

To write an Architectural Decision Record with evidence-based justification, structure the context, consequences, and reversibility of your choice to provide defensible rationale. This approach distinguishes between high, medium, and low confidence decisions based on supporting data and industry practices.

What is the best way to justify technology selection and evaluate technical trade-offs?▼

The best way to justify technology selection is to outline supporting data and trade-offs for each framework or library. By evaluating technical debt and distinguishing confidence levels, you provide a defensible rationale that makes complex technical choices understandable to stakeholders.

How do you communicate architectural design decisions to stakeholders clearly?▼

Communicating architectural design decisions to stakeholders requires clear explanations that make complex technical choices understandable and defensible. By focusing on context, consequences, and evidence-based rationale, you move beyond personal opinion to structured justification.

When do I need to document architectural decisions and technical debt?▼

You need to document architectural decisions and technical debt when choosing between libraries, frameworks, or tools and require defensible rationale. Structured justification is essential when distinguishing between high, medium, and low confidence decisions based on data and industry practices.

Can I use structured justification for choosing between web frameworks like Elixir and Node.js?▼

Yes, you can use structured justification for choosing between web frameworks like Elixir and Node.js by outlining supporting data and trade-offs. This evaluates technology selection by focusing on context, consequences, and reversibility to provide defensible architectural rationale.