technical-decision

Analyze technical options and draft an Architecture Decision Record.

1|Updated Sep 17, 2025
One-click install
npx skills add https://github.com/mpazaryna/agentic-factory --skill technical-decision
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: technical-decision
Source: https://github.com/mpazaryna/agentic-factory/tree/main/dev/codebase-analysis/skills/technical-decision
Command: npx skills add https://github.com/mpazaryna/agentic-factory --skill technical-decision

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps users make informed decisions when faced with technical choices by providing a structured framework for analysis, comparison, and documentation.

Core Features & Use Cases

  • Structured Analysis: Guides users through defining decision context, evaluation criteria, and researching options.
  • Comparative Scoring: Facilitates objective comparison of different options using a weighted matrix.
  • Recommendation Generation: Produces a clear recommendation with rationale and identified tradeoffs.
  • ADR Drafting: Automatically generates a draft Architecture Decision Record (ADR) for documentation.
  • Use Case: When deciding between using a microservices architecture or a monolithic approach for a new project, this Skill can help weigh the pros and cons against project-specific criteria.

Quick Start

Use the technical-decision skill to analyze the choice between using React or Vue for a new web application.

Frequently Asked Questions about technical-decision

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

FAQPage Schema
How do I make a technical decision between different architecture patterns?

Making a technical decision involves defining the decision context, establishing evaluation criteria, researching alternatives, and scoring them in a comparison matrix to generate a recommendation with rationale.

What is an Architecture Decision Record and when do I need one?

An Architecture Decision Record (ADR) is a document capturing technical decisions. You need an ADR when selecting technologies or architecture patterns to ensure informed choices and maintain project documentation.

How do I compare technology options using a weighted evaluation matrix?

Comparing technology options requires establishing evaluation criteria, researching alternatives, and scoring them in a comparison matrix to objectively evaluate options and produce a clear recommendation.

Can I use a structured analysis for both technology selection and implementation approach decisions?

Structured analysis applies to technology selection, architecture decisions, and implementation approach selections. Defining context and scoring alternatives ensures informed technical decisions across different project scopes.

What is the best way to document technical tradeoffs when choosing a framework?

The best way to document technical tradeoffs is by drafting an Architecture Decision Record (ADR). An ADR captures the decision context, comparative scoring, recommendation, and rationale for future reference.

Why do I need to define decision context before selecting a technology?

Defining decision context before selecting a technology ensures alternatives are evaluated against project-specific criteria. This prevents misalignment and produces a recommendation with identified tradeoffs.