optionality-review

Assess decisions and architecture for reversibility, resilience, and future value.

1|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/charly-vibes/wai --skill optionality-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: optionality-review
Source: https://github.com/charly-vibes/wai/tree/main/.agents/skills/optionality-review
Command: npx skills add https://github.com/charly-vibes/wai --skill optionality-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you critically evaluate decisions, code, and architecture to ensure they preserve future flexibility and resilience, preventing costly lock-ins and enabling adaptability.

Core Features & Use Cases

  • Decision Classification: Distinguishes between reversible (Type 2) and irreversible (Type 1) decisions.
  • Option Space Analysis: Maps out alternative approaches and their impact on future choices.
  • Risk Assessment: Identifies exit costs, failure modes, and fallback plans.
  • Use Case: Before committing to a new microservice architecture, use this Skill to assess the reversibility of key design choices, identify potential vendor lock-ins, and evaluate fallback strategies if the chosen technology proves unsuitable.

Quick Start

Review the attached design document 'microservices-architecture.md' for strategic optionality.

Frequently Asked Questions about optionality-review

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

FAQPage Schema
What is strategic optionality in architecture review?

Strategic optionality in architecture review evaluates decisions to maximize future flexibility by classifying them as reversible or irreversible. It assesses exit costs and failure modes to prevent costly vendor lock-ins and preserve adaptability.

How do I assess the reversibility of a microservice design decision?

Assess the reversibility of a microservice design by mapping alternative approaches and calculating exit costs. This identifies potential vendor lock-ins and evaluates fallback strategies if the chosen technology proves unsuitable.

When do I need an optionality assessment for project planning?

You need an optionality assessment before committing to irreversible architecture decisions. It identifies failure modes, calculates exit costs, and ensures your strategic plan maintains future value creation and resilience.

Can I evaluate product strategy decisions for future flexibility?

Yes, you can evaluate product strategy decisions for future flexibility by analyzing decision types, alternative paths, and future value creation. This yields a comprehensive optionality score and actionable recommendations.

What's the best way to minimize vendor lock-in in software architecture?

Minimize vendor lock-in in software architecture by mapping the option space of alternative approaches and identifying exit costs. Reviewing decisions through strategic optionality ensures you maintain fallback plans and adaptability.