researching-options-and-decisions

Evaluate architecture choices and document tradeoffs in a decision table.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/michaelkd01/dic-skills --skill researching-options-and-decisions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: researching-options-and-decisions
Source: https://github.com/michaelkd01/dic-skills/tree/main/researching-options-and-decisions
Command: npx skills add https://github.com/michaelkd01/dic-skills --skill researching-options-and-decisions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill stops ad hoc architecture decisions by guiding teams to analyze new ideas, technology choices, and design questions before implementation so every path is well understood and documented.

Core Features & Use Cases

  • Structured Research: Follow a repeatable workflow to gather context, review existing ADRs, and surface relevant conversations or roadmap impacts before recommending a direction.
  • Option Comparison Table: Evaluate two to four viable choices side-by-side with cost, effort, risks, maintenance, and ADR impacts plus a clear recommendation and tradeoff statement.
  • Decision Documentation: After approval, capture updates in the Architecture & Decisions doc, roadmap, task queue, and chat log for full traceability of the recommendation.
  • Use Case: When the team debates adopting a new backend pattern, use this skill to document the discovery, compare alternatives, and preserve the resulting ADR and tasks.

Quick Start

Ask the skill to compare two implementation strategies for the upcoming feature using the decision template.

Frequently Asked Questions about researching-options-and-decisions

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

FAQPage Schema
How do I document architecture decisions and compare technology options?

Document architecture decisions by gathering context, reviewing existing ADRs, and evaluating two to four options side-by-side. This produces a structured comparison table covering cost, effort, and risks, ending with a clear recommendation and tradeoff statement.

What is the best way to evaluate backend architecture tradeoffs before implementation?

Evaluating architecture tradeoffs requires comparing viable choices across cost, maintenance, and risk dimensions. A structured option analysis surfaces roadmap impacts and ADR conflicts before implementation begins, ensuring every design path is fully understood.

How do I create an option comparison table for software technology selection?

Create an option comparison table by analyzing two to four implementation strategies against criteria like effort, cost, and maintenance. This structured decision framework captures context research and yields a documented recommendation with explicit tradeoffs.

Can I use a decision framework for vetting new software ideas and roadmap impacts?

A decision framework supports idea vetting and roadmap impact analysis by documenting discovery and comparing alternatives. It captures the resulting ADR, task queue updates, and chat logs after approval to maintain full recommendation traceability.

When should I use structured option analysis instead of ad hoc architecture decisions?

Use structured option analysis when teams debate adopting new patterns or face roadmap-impacting decisions. It stops ad hoc architecture choices by enforcing context research, risk assessment, and a confirmation step before implementation proceeds.

Does this decision documentation workflow update the task queue and roadmap automatically?

The decision documentation workflow captures updates in the Architecture and Decisions doc, roadmap, and task queue after approval. This ensures full traceability of the recommendation and preserves the resulting tasks for implementation.