skills.rest
fengqiliu
fengqiliuCOMMUNITY
Explore all skills by this author →
GitHub

technical-decision

Clarify technology decisions with structured problem definition and ADR documentation.

2|Updated Mar 30, 2026
Search Tags:#architecture#technology#ADR#decision-making#system-design#risk-analysis#vendor-analysis
One-click install
npx skills add https://github.com/fengqiliu/PM-Skills --skill technical-decision-fengqiliu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: technical-decision
Source: https://github.com/fengqiliu/PM-Skills/tree/main/plugins/architect-plugin/skills/technical-decision
Command: npx skills add https://github.com/fengqiliu/PM-Skills --skill technical-decision-fengqiliu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clarify technology decisions.

Core Features & Use Cases

It applies to architecture reviews, vendor comparisons, and risk analysis across software projects. It satisfies the requirements for structured problem definition, option generation, evaluation criteria, and ADR documentation.

Quick Start

Ask it to produce an ADR draft for the new microservice, including problem statement, options, and recommended decision.

Frequently Asked Questions about technical-decision

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

FAQPage Schema
How do I write an ADR for a new microservice architecture?▼

A vendor comparison evaluates technology options against structured evaluation criteria to clarify technology decisions. It defines the problem, generates viable vendor options, and documents the recommended decision with supporting rationale.

What is the best way to document system-design risk analysis?▼

The best way to document system-design risk analysis is through an Architecture Decision Record (ADR). ADRs structure the problem definition, option evaluation, and risk analysis into a clear, recommended technical decision.

Can I use this for architecture reviews without prior ADR experience?▼

Yes, you can use this for architecture reviews without prior ADR experience. It guides you through structured problem definition, option generation, and evaluation criteria to produce a clear ADR draft.

How does structured problem definition improve technology decision-making?▼

Structured problem definition improves technology decision-making by clarifying the exact issue before generating options. This ensures evaluation criteria and risk analysis directly address the core architecture problem, leading to a justified ADR.

When should I not use an ADR for vendor analysis?▼

You should not use an ADR for vendor analysis when the technology decision is trivial or reversible. ADRs are intended for significant architecture choices requiring structured risk analysis and permanent documentation.

Related Skills

Explore More Software Engineering Skills→
jamestorrevillasjamestorrevillas
3

research-synthesis

Synthesize research on frameworks and tools into a decision memo.

Community
Advanced
AIMFllysAIMFllys
3

architecture

Convert requirements into justified architecture decisions with ADR documentation.

Community
Intermediate
fmoda3fmoda3
42

decision-critic

Critique architectural, technology, and strategic decisions via a Python scripted workflow.

Community
Intermediate
flight505flight505
4

architecture-research

Evaluate technology options and document decisions with Architecture Decision Records.

Community
Advanced