scenario-spread

Explore and validate multiple design scenarios for high-impact technical decisions.

6|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/markacianfrani/armor --skill scenario-spread
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scenario-spread
Source: https://github.com/markacianfrani/armor/tree/main/skills/scenario-spread
Command: npx skills add https://github.com/markacianfrani/armor --skill scenario-spread

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents decision paralysis and ego-driven development by forcing the exploration of multiple distinct approaches before committing to a high-stakes technical path.

Core Features & Use Cases

  • Ego Guard: Explicitly separates your personal attachment to an idea from the objective evidence gathered through testing.
  • Comparative Analysis: Guides you to sketch three distinct shapes for a solution and evaluate them against real-world feedback.
  • Use Case: Use this when designing a new public API or choosing a core dependency to ensure you are picking the best technical solution rather than the first one that came to mind.

Quick Start

Ask the AI to perform a scenario spread analysis on your current architectural design to identify potential alternatives and validate your preferred approach.

Frequently Asked Questions about scenario-spread

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

FAQPage Schema
How do I reduce cognitive bias in software architecture decisions?

To reduce cognitive bias in software architecture, mandate the parallel exploration of multiple design scenarios before committing. This approach requires generating distinct solution shapes and applying objective feedback loops to validate the optimal technical path.

What is the best way to avoid premature commitment to a technical design?

Avoid premature commitment by performing a scenario spread analysis that sketches three distinct solution shapes. This comparative analysis evaluates each architecture against real-world feedback, separating personal attachment from objective evidence.

When should I use multi-option testing for software design?

Use multi-option testing for software design during high-impact, non-reversible technical decisions. It is specifically designed for scenarios like designing a new public API or choosing a core dependency to prevent ego-driven development.

How do I validate my preferred approach when choosing a core dependency?

Validate your preferred approach by generating distinct alternative solution shapes and evaluating them against real-world feedback. This comparative analysis ensures you select the best technical solution rather than the first idea that came to mind.

Can I use scenario spread analysis for low-impact technical decisions?

Scenario spread analysis is intended for high-impact, non-reversible technical decisions. Applying it to low-impact choices is unnecessary, as the method specifically mitigates decision paralysis and ego-driven development for major architectural paths.