Decision Framework FAQs

Question 1

When should I use this skill during development?

Accepted Answer

Activate this skill whenever you face a fork in the road, such as choosing between two frameworks, deciding on an architectural pattern, or weighing the pros and cons of a specific implementation. It is ideal for any 'Should I...' or 'Which is better?' scenarios.

Question 2

What specific capabilities does it provide?

Accepted Answer

The skill provides automated KPI identification, probabilistic outcome forecasting (e.g., '60% chance of faster shipping'), sensitivity analysis for critical assumptions, and a dedicated '/decide' command for deep-dive logging of major project decisions.

Question 3

What does the Decision Framework skill do?

Accepted Answer

It reframes subjective questions (like 'should I use this library?') into structured forecasting problems. Instead of giving opinions, it uses explicit Key Performance Indicators (KPIs) and quantified probabilities to help you evaluate different decision paths based on data.

Question 4

How does this skill improve my workflow?

Accepted Answer

It reduces AI sycophancy by forcing Claude to provide numeric predictions rather than just agreeing with your ideas. This approach encourages 'mechanism thinking,' surfaces hidden assumptions, and creates a logged trail of logic that you can refer back to as your project evolves.

Question 5

Will Claude still give me a direct recommendation?

Accepted Answer

No. The framework is designed to separate values (your KPIs) from facts (the forecasts). It will tell you 'If you value Speed, Option A is 70% likely to succeed,' allowing you to make the final choice based on your specific priorities.

Decision Framework

Decision Framework

主な機能

ユースケース

主な機能

ユースケース