analysis-technology

Evaluate technology adoption decisions using an IF, WHY, HOW, and SO WHAT framework.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/MaxDehaut/default-repository --skill analysis-technology
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analysis-technology
Source: https://github.com/MaxDehaut/default-repository/tree/main/.claude/skills/analysis-technology
Command: npx skills add https://github.com/MaxDehaut/default-repository --skill analysis-technology

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Applies a structured IF → WHY → HOW → SO WHAT framework to evaluate any technology, tool, library, or technical approach. Use this skill whenever the user asks whether they should adopt, try, drop, or choose between tools — including phrases like "should I use X", "is X worth it", "evaluate this tool", "help me decide between A and B", "is X right for my stack", "what do you think about adopting X", or any question implying a tech adoption decision. Always use this skill for tech evaluation requests, even when phrased casually.

Core Features & Use Cases

  • Structured, opinionated evaluation framework that yields concise, actionable decisions.
  • Clear decision output format (IF/WHY/HOW/SO WHAT) to streamline stakeholder buy-in.
  • Suitable for product and engineering decisions across stacks and vendor comparisons.

Quick Start

Provide a concise TECH DECISION NOTE for the technology you are evaluating.

Frequently Asked Questions about analysis-technology

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

FAQPage Schema
How do I evaluate whether to adopt a new technology or tool for my stack?▼

To evaluate technology adoption, apply a structured IF → WHY → HOW → SO WHAT framework. This method requires a clear problem statement and defined criteria to produce an actionable TECH DECISION NOTE for stakeholder buy-in.

What is the best way to decide between two engineering tools?▼

The best way to decide between engineering tools is using an opinionated evaluation framework. It compares options against your defined criteria, outputting a concise TECH DECISION NOTE that explains the adoption choice and implementation approach.

Can I use a structured framework for casual tech adoption questions?▼

Yes, you can use a structured tech decision framework for casual adoption questions. Even casually phrased queries like 'should I use X' are processed into formal IF → WHY → HOW → SO WHAT evaluations to ensure rigorous engineering decisions.

How do I format an actionable technology stack recommendation?▼

Format a technology stack recommendation as a concise TECH DECISION NOTE. Structure it using the IF → WHY → HOW → SO WHAT sequence to clearly communicate the decision context, rationale, and actionable implementation steps to stakeholders.

What do I need before evaluating a technical approach?▼

Before evaluating a technical approach, you need a clear problem statement and defined evaluation criteria. Providing these inputs ensures the structured framework yields a concise, actionable recommendation suitable for engineering teams.