decision-check

Pressure-tests a single pending decision through five structured trade-off questions.

1|Updated Jun 30, 2026
One-click install
npx skills add https://github.com/Lia-Creative/lia-plugins --skill decision-check-lia-creative
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: decision-check
Source: https://github.com/Lia-Creative/lia-plugins/tree/main/lia-tools/skills/decision-check
Command: npx skills add https://github.com/Lia-Creative/lia-plugins --skill decision-check-lia-creative

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams commit to fast answers under pressure without naming what they are trading away, and the pull toward the quick option is invisible from inside the decision. This Skill applies a short, structured check to one decision before it is locked in, surfacing hidden costs and reversibility. ## Core Features & Use Cases - Five-question check: Names the incentive pulling toward the fast answer, states the fast choice plainly, identifies what is being traded, tests reversibility (one-way vs two-way door), and checks what the choice is optimising for. - Scope discipline: Distinguishes real decisions from tasks (if nothing is traded, it is a task) and tells you to move fast on cheap, reversible calls instead of over-analysing them. - Advisory boundary: Sharpens the call for the person who owns it without making the decision for them, and labels any recommendation plainly. - Use Case: A team lead is about to pick a vendor under deadline pressure. Run the check to name the deadline incentive, state the fast pick, surface the migration cost being traded, confirm it is a one-way door, and verify the choice optimises for the right thing. ## Quick Start Ask the agent to pressure-test the decision you are about to make using decision-check before you commit to it.

Frequently Asked Questions about decision-check

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

FAQPage Schema
How do I pressure-test a decision before committing to it?▼

Run the five-question check: name the incentive pulling toward the fast answer, state the fast choice plainly, identify what is being traded, test whether it is a one-way or two-way door, and check what the choice is optimising for.

What is the difference between a one-way door and two-way door decision?▼

A one-way door is expensive or impossible to reverse and deserves slow, careful thought. A two-way door is cheap to undo and deserves less agonising; the common failure is labouring reversible calls while sleepwalking irreversible ones.

When should I not use a decision pressure-test?▼

Skip it when nothing is being traded, because that is a task rather than a decision, and when the call is cheap and reversible and has already had a few minutes of thought. Running the full check on trivial calls wastes the attention it exists to protect.

Does decision-check make the decision for me?▼

No. It sharpens the call so the person who owns it can decide, surfacing the real trade and the one or two options that genuinely differ. When a recommendation is worth giving, it is given plainly labelled as one.

How is decision-check different from an architecture review or decision record?▼

Decision-check is the pass before a call is committed, not the record written after it settles. Technical decisions with system consequences go to an architecture review; this skill covers the general shape underneath any kind of call.