Technical Decision Patterns FAQs

Question 1

Where are the technical decisions saved?

Accepted Answer

Decisions are structured and saved into a research.md file, providing a centralized location for all architectural research and finalized choices.

Question 2

What is an ADR in this context?

Accepted Answer

An ADR (Architecture Decision Record) is a document that captures a significant architectural decision, including its context, rationale, and consequences for future maintainers.

Question 3

How does this skill help with technical choices?

Accepted Answer

It implements a three-phase workflow (Evaluate, Decide, Document) that forces a comparison of at least 2-3 alternatives against criteria like cost, security, and scalability.

Question 4

What is 'Brownfield Alignment'?

Accepted Answer

It is a check included in the skill to ensure that new technology choices align with your existing codebase and ecosystem, prioritizing reuse over introducing unnecessary new dependencies.

Question 5

Can this skill prevent 'Shiny Object Syndrome'?

Accepted Answer

Yes, by requiring detailed justifications, pros/cons, and evaluation of team familiarity, it discourages picking new technologies without a proven technical benefit.

Technical Decision Patterns

주요 기능

사용 사례

Technical Decision Patterns

주요 기능

사용 사례