skills.rest
datamonsterr
datamonsterrCOMMUNITY
Explore all skills by this author →
GitHub

speckit-whatif-analyze

Simulate requirement changes and report complexity, effort, and task deltas.

Updated Apr 12, 2026
Search Tags:#planning#architecture#requirements#simulation#risk#impact#what-if
One-click install
npx skills add https://github.com/datamonsterr/mycoai_projects --skill speckit-whatif-analyze
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-whatif-analyze
Source: https://github.com/datamonsterr/mycoai_projects/tree/main/.agents/skills/speckit-whatif-analyze
Command: npx skills add https://github.com/datamonsterr/mycoai_projects --skill speckit-whatif-analyze

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Preview the downstream impact of requirement changes on complexity, effort, and task breakdown, before committing to them.

Core Features & Use Cases

  • Read-only What-if Simulation: simulate changes without touching any files.
  • Impact metrics: compute complexity, effort, and task deltas for stakeholder reporting.
  • Use Case: When a proposal arises, simulate its effects to decide if a change should proceed.

Quick Start

Provide a What-if Scenario describing the proposed requirement change to start the simulation.

Frequently Asked Questions about speckit-whatif-analyze

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

FAQPage Schema
How do I simulate requirement changes to see their impact before committing?▼

To preview requirement changes, you provide a what-if scenario describing the proposed modification to run a read-only simulation without touching project files, generating a report with impact metrics on complexity and effort.

What is a what-if analysis for software architecture and planning?▼

A what-if analysis for software architecture simulates proposed requirement changes to compute downstream impact on complexity, effort, and task breakdown, enabling stakeholders to make informed go/no-go decisions before implementation.

Can I analyze the downstream impact of a requirement change without modifying project files?▼

Yes, you can analyze downstream impact without modifying files by providing a what-if scenario, which runs a read-only simulation against loaded project artifacts to compute effort and complexity deltas.

How do I calculate effort and complexity deltas for a proposed requirement change?▼

You calculate effort and complexity deltas by loading project artifacts and applying a what-if scenario, which outputs a structured, decision-ready report with impact metrics and recommended actions.

When do I need to run a what-if simulation for software requirements?▼

You need to run a what-if simulation when a new proposal arises during planning, allowing you to preview effects on task breakdown and complexity to decide if the requirement change should proceed.

Does the what-if simulation output support go/no-go decisions for implementation tasks?▼

Yes, the what-if simulation outputs a structured, decision-ready report containing impact metrics and recommended actions, directly supporting go/no-go decisions for implementation and testing tasks.

Related Skills

Explore More Software Engineering Skills→
dallaydallay

sdd-spec

Generate ADDED, MODIFIED, and REMOVED requirement sections with Given/When/Then scenarios.

Official
Advanced
DanielShuguangDanielShuguang

openspec-archive-change

Archive completed experimental changes and synchronize incremental specifications with main specifications.

Community
Advanced
Vivekmano27Vivekmano27

estimation-skill

Estimate feature effort with story points and time ranges.

Community
Advanced
B0yZ4kr14B0yZ4kr14

speckit-scope-compare

Compare two Specify spec versions and quantify requirement scope changes.

Community
Intermediate