Justify architectural and design decisions with evidence, context, and consequences.
npx skills add https://github.com/baphled/dotopencode --skill justify-decision
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
This Skill provides a structured, evidence-based justification for architectural and design decisions, moving beyond opinion to defensible rationale.
Use the justify-decision skill to provide evidence-based justification for choosing Elixir/Phoenix over Node.js for handling 10k concurrent WebSocket connections.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
petrSimonidesXartEvaluate technical approaches against project constraints with documented evidence.
jwilgerManage Architecture Decision Records and maintain living architecture documentation.
alirezarezvaniAnalyze strategic positions and model financial scenarios for CEO decisions.
adolfoaranaes12Create Architecture Decision Records with context, alternatives, rationale, and consequences.
