tech-decision

Automates multi-faceted decision analysis for IT project planning and resource optimization.

171|23|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/team-attention/hoyeon --skill tech-decision
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-decision
Source: https://github.com/team-attention/hoyeon/tree/main/skills/tech-decision
Command: npx skills add https://github.com/team-attention/hoyeon --skill tech-decision

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill automates multi-source technical decision analysis to guide architecture choices.

Core Features & Use Cases

  • Structured problem definition: Define the decision topic, options, and evaluation criteria to ensure alignment with project context.
  • Parallel information gathering: Simultaneously collect evidence from docs, codebases, community opinions, and expert perspectives to accelerate decision making.
  • Synthesis & final reporting: Produce a concise conclusion-first recommendation with an evidence-backed rationale and a reusable decision template.

Quick Start

  1. Define the decision topic and collect options.
  2. Trigger parallel data gathering using docs-researcher, codebase-explorer, skill-dev-scan, and agent-council.
  3. Run the tradeoff-analyzer and decision-synthesizer to generate the final report.

Frequently Asked Questions about tech-decision

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

FAQPage Schema
What is multi-source technical decision analysis for architecture choices?

Multi-source technical decision analysis evaluates library, framework, and architecture options by gathering evidence from documentation, codebases, and community opinions to produce an evidence-backed recommendation report.

How do I compare frameworks and libraries for my software architecture?

To compare frameworks and libraries, define your decision topic and evaluation criteria, trigger parallel data gathering from multiple sources, and run a tradeoff analyzer to synthesize a conclusion-first recommendation.

Can I use automated analysis for selecting an implementation approach across my software projects?

Yes, automated analysis supports implementation approach selection across software projects by applying structured problem definition, parallel information gathering, and tradeoff synthesis to generate a final evidence-backed report.

What is the best way to structure a tradeoff analysis for software architecture decisions?

The best way to structure a tradeoff analysis is to define the problem and options, gather parallel information from diverse technical sources, and synthesize the evidence into a concise conclusion-first recommendation.

When should I avoid automated multi-source synthesis for tech decisions?

You should avoid automated multi-source synthesis when your software project lacks clearly defined decision criteria, evaluation options, or sufficient documentation and community evidence to support an evidence-backed rationale.