/scenario

Generates structured scenario notes for architectural what-if analysis and option evaluation.

49|12|Updated Jan 8, 2026

Search Tags:#architecture #decision making #scenario planning #risk mitigation #what-if analysis #future state

Ready to run

npx skills add https://github.com/DavidROliverBA/ArchitectKB --skill scenario

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: /scenario
Source: https://github.com/DavidROliverBA/ArchitectKB/tree/main/.claude/skills/scenario
Command: npx skills add https://github.com/DavidROliverBA/ArchitectKB --skill scenario

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you create structured notes for exploring potential future states of your architecture, evaluating alternative options, and planning risk mitigation strategies.

Core Features & Use Cases

Scenario Planning: Define and document various future architectural scenarios.
Option Evaluation: Compare different architectural approaches and their implications.
Risk Assessment: Document strategies for mitigating identified risks.
Use Case: You need to decide between migrating your SAP system to a cloud-native solution or a hybrid approach. Use this Skill to create a 'SAP Cloud Migration' scenario, detailing the changes, impacts, and comparing it against a 'SAP Hybrid' alternative.

Quick Start

Create a new scenario note for 'SAP Cloud Migration' with the future-state type.

Frequently Asked Questions about /scenario

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

FAQPage Schema

How do I document architectural what-if analysis for future-state planning?▼

Architectural what-if analysis is documented by generating structured scenario notes that map future-state planning, detailing business, technical, cost, and organizational impacts. This approach captures trade-offs and decision criteria for alternative option evaluation.

What is the best way to compare alternative architectural options and their implications?▼

Comparing alternative architectural options requires structured documentation of each approach's business, technical, and cost impacts. Scenario planning enables direct evaluation of trade-offs and decision criteria to determine the optimal future state.

How do I structure scenario notes for risk mitigation and architecture decision making?▼

Structure scenario notes by generating files with metadata frontmatter and detailed body content. This format facilitates structured documentation of risk mitigation strategies and organizational impacts for architecture decision making.

Can I use this for evaluating a cloud-native versus hybrid system migration?▼

Yes, you can evaluate cloud-native versus hybrid migrations by creating specific scenario notes. You define the future state, detail technical changes, and compare alternatives to document the impacts of each migration strategy.

What should I include in an architectural scenario file to evaluate trade-offs?▼

An architectural scenario file should include frontmatter metadata and body content detailing business, technical, cost, and organizational impacts. Incorporating trade-offs and decision criteria ensures comprehensive alternative option evaluation.