thinking-reversibility

Classifies decisions by undo cost and matches deliberation depth to reversibility.

Updated May 24, 2026
One-click install
npx skills add https://github.com/MWest2020/skill-forge --skill thinking-reversibility-mwest2020
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: thinking-reversibility
Source: https://github.com/MWest2020/skill-forge/tree/main/skills/thinking-reversibility
Command: npx skills add https://github.com/MWest2020/skill-forge --skill thinking-reversibility-mwest2020

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams routinely over-deliberate cheap, reversible choices and under-deliberate expensive, irreversible ones. This Skill provides a structured procedure to classify any decision by its undo cost before committing analysis effort, so process depth always matches actual risk. ## Core Features & Use Cases - Reversibility Classification: Scores decisions as Type 2 (undo in days), Type 1.5 (undo in weeks), or Type 1 (months or effectively irreversible) based on effort, money, reputation, and dependents. - Asymmetric Downside Analysis: Compares the recoverable cost of acting wrong against the permanent losses of not acting, such as closing windows or path lock-in. - Option-Preserving Redesign: Converts irreversible commitments into reversible experiments using pilots, feature flags, versioning, and time-boxed terms. - Use Case: Before migrating a production database to a new vendor, classify the move, identify the concrete rollback path, and stage the commitment behind an abstraction layer so only the residual irreversible core gets full deliberation. ## Quick Start Ask the agent to apply the reversibility framework to a decision you are facing, for example whether to adopt a new vendor or rewrite a service, and request the classification and recommended process depth.

Frequently Asked Questions about thinking-reversibility

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

FAQPage Schema
How do I decide how much analysis a decision deserves?

Classify the decision by its undo cost first. Decisions reversible in days deserve fast commitment, while those taking months to reverse warrant full deliberation. Match process depth to the classification rather than applying uniform analysis to everything.

What is the difference between Type 1 and Type 2 decisions?

Type 2 decisions can be undone in days at low cost, so they should be decided quickly. Type 1 decisions take months to reverse or are effectively irreversible, so they deserve documented assumptions, opposing arguments, and staged commitment.

How can I make an irreversible decision more reversible?

Redesign the move to preserve options using pilots, feature flags, interface abstractions, versioning, or time-boxed vendor terms. This converts irreversible surface area into reversible experiments, leaving only a small core that needs deep deliberation.

When should I not use reversibility classification?

Skip it for trivial two-way calls where deciding is cheaper than classifying, externally forced moves with no optionality, and correctness gates like security or data integrity that require the right answer regardless of speed.

Why does over-deliberation happen on reversible decisions?

Teams treat all decisions as equally risky and apply committee-style process to low-blast-radius choices. The fix is to name the concrete undo path and cost; if reversal is cheap, decide fast and monitor instead of analyzing further.