decision-maker_skill

Overview

This skill helps engineering teams make better technical choices by applying structured decision frameworks: trade-off evaluation, reversibility analysis, and second-order thinking. It focuses on classifying decisions, speeding reversible choices, documenting rationale, and surfacing downstream consequences. The goal is faster learning, fewer irreversible mistakes, and clearer accountability.

How this skill works

The skill classifies each decision as reversible (two-way door) or irreversible (one-way door) and recommends an appropriate process. It evaluates trade-offs across cost, time, risk, and learning velocity, applies reversibility analysis to estimate undo cost and timeframe, and prompts second-order thinking to expose downstream impacts. It produces concise guidance, a recommended owner, and a focused rationale that can be recorded for future review.

When to use it

• Choosing between alternative architectures, frameworks, or services
• Deciding whether to invest effort in a long-lived platform change
• Evaluating if a prototype should be productionized or iterated
• Determining which feature to prioritize under scarce resources
• Assessing vendor lock-in, migration risk, or rollout strategy

Best practices

• Classify the decision first: reversible vs irreversible to pick a process
• Favor speed for reversible choices: decide, measure, and iterate quickly
• Document the 'why' and key assumptions, not an exhaustive narrative
• Identify the owner who can make the call and be accountable
• Think two steps ahead: enumerate likely second-order effects and mitigations

Example use cases

• Pick between managed DB vs self-hosted: weigh short-term speed vs long-term control and migration cost
• Decide whether to adopt a new observability tool: assess trial cost and rollback path
• Choose a deployment strategy (blue/green vs canary): map risk, rollback time, and monitoring needs
• Prioritize between platform refactor and feature delivery: compare business impact and reversibility
• Evaluate using a paid SaaS for authentication vs building in-house: consider lock-in horizon and undo complexity