scenario-narrative-generator
Scenario narrative generation skill for creating vivid, consistent future scenario descriptions
What this skill does
# Scenario Narrative Generator
## Overview
The Scenario Narrative Generator skill creates vivid, internally consistent narratives for strategic scenarios. It transforms driving forces and uncertainties into compelling stories that help stakeholders envision alternative futures and test strategic options.
## Capabilities
- Driving forces integration
- Consistency checking across scenario elements
- Narrative arc construction
- Key event identification
- Implication extraction
- Headline generation
- Persona-in-scenario development
- Scenario comparison tables
## Used By Processes
- Strategic Scenario Development
- War Gaming and Competitive Response Modeling
- What-If Analysis Framework
## Usage
### Scenario Framework
```python
# Define scenario framework
scenario_framework = {
"focus_question": "What will the enterprise software market look like in 2030?",
"time_horizon": "2030",
"critical_uncertainties": [
{
"name": "AI Adoption Rate",
"dimension": "Technology",
"poles": ["Rapid AI Integration", "Gradual AI Adoption"]
},
{
"name": "Regulatory Environment",
"dimension": "Political",
"poles": ["Tech-Friendly Regulation", "Restrictive Regulation"]
}
],
"scenario_matrix": {
"scenarios": [
{"name": "AI Explosion", "position": ["Rapid AI", "Tech-Friendly"]},
{"name": "Regulated Innovation", "position": ["Rapid AI", "Restrictive"]},
{"name": "Steady Progress", "position": ["Gradual AI", "Tech-Friendly"]},
{"name": "Digital Caution", "position": ["Gradual AI", "Restrictive"]}
]
}
}
```
### Scenario Elements
```python
# Define scenario elements
scenario_elements = {
"scenario_name": "AI Explosion",
"driving_forces": {
"technology": "AI capabilities advance rapidly, with AGI breakthroughs",
"economy": "Massive productivity gains fuel economic growth",
"society": "Workforce disruption creates social tension",
"regulation": "Governments adopt innovation-friendly policies"
},
"key_events": [
{"year": 2025, "event": "First enterprise AGI deployment"},
{"year": 2026, "event": "50% of software written by AI"},
{"year": 2027, "event": "Major productivity leap in white-collar work"},
{"year": 2028, "event": "Traditional software vendors consolidate"},
{"year": 2029, "event": "New AI-native competitors dominate"},
{"year": 2030, "event": "Enterprise software market unrecognizable"}
],
"stakeholder_impacts": {
"customers": "Expect AI-first solutions, willing to pay premium for automation",
"competitors": "AI-native startups disrupt incumbents",
"employees": "Massive reskilling required",
"investors": "Flight to AI leaders, traditional valuations collapse"
}
}
```
### Narrative Generation
```python
# Generate narrative
narrative_config = {
"scenario_name": "AI Explosion",
"style": "journalist_from_the_future",
"length": "1500_words",
"structure": {
"headline": True,
"opening_hook": True,
"timeline_narrative": True,
"stakeholder_vignettes": True,
"implications_summary": True
},
"persona": {
"include": True,
"name": "Sarah Chen",
"role": "CIO of a mid-size manufacturer",
"journey": "How her company navigated this world"
}
}
```
### Consistency Check
```python
# Check narrative consistency
consistency_check = {
"checks": [
{
"type": "causal_logic",
"elements": ["rapid_ai", "workforce_disruption"],
"result": "consistent",
"note": "AI adoption logically leads to job displacement"
},
{
"type": "timeline",
"elements": ["AGI_2025", "software_dominance_2026"],
"result": "plausible",
"note": "12-month gap is tight but possible given premise"
},
{
"type": "contradiction",
"elements": ["innovation_friendly_regulation", "strict_ai_oversight"],
"result": "inconsistent",
"note": "Resolve: clarify regulation is permissive on development, focused on safety"
}
]
}
```
### Comparison Table
```python
# Generate comparison table
comparison_config = {
"scenarios": ["AI Explosion", "Regulated Innovation", "Steady Progress", "Digital Caution"],
"dimensions": [
"Market Size 2030",
"Number of Major Vendors",
"AI Penetration Rate",
"Regulatory Burden",
"Workforce Impact",
"Key Success Factors",
"Strategic Implications"
]
}
```
## Input Schema
```json
{
"scenario_framework": {
"focus_question": "string",
"time_horizon": "string",
"critical_uncertainties": ["object"],
"scenario_matrix": "object"
},
"scenario_elements": {
"driving_forces": "object",
"key_events": ["object"],
"stakeholder_impacts": "object"
},
"narrative_config": {
"style": "string",
"length": "string",
"structure": "object",
"persona": "object"
}
}
```
## Output Schema
```json
{
"narrative": {
"headline": "string",
"body": "string (markdown)",
"word_count": "number"
},
"persona_story": {
"name": "string",
"journey": "string"
},
"key_events_timeline": ["object"],
"implications": {
"strategic": ["string"],
"operational": ["string"],
"capability_gaps": ["string"]
},
"comparison_table": "object",
"consistency_report": "object"
}
```
## Narrative Styles
| Style | Characteristics | Best For |
|-------|-----------------|----------|
| Journalist | News article from the future | Vivid, accessible |
| Historian | Looking back at changes | Analytical, comprehensive |
| Day-in-the-Life | Personal experience | Emotional, relatable |
| Strategic Briefing | Executive summary | Time-efficient, action-oriented |
## Best Practices
1. Make scenarios vivid and memorable with specific details
2. Ensure internal consistency within each scenario
3. Make scenarios sufficiently different from each other
4. Balance plausibility with challenge to conventional thinking
5. Include both opportunities and threats
6. Use personas to make abstract futures tangible
7. Connect scenarios to strategic decisions
## Scenario Quality Criteria
| Criterion | Description |
|-----------|-------------|
| Plausibility | Could this happen given current trends? |
| Consistency | Do elements logically fit together? |
| Relevance | Does it address the focus question? |
| Differentiation | Is it distinct from other scenarios? |
| Usability | Can stakeholders engage with it? |
| Challenge | Does it stretch conventional thinking? |
## Integration Points
- Feeds into War Game Orchestrator for competitive scenarios
- Connects with System Dynamics Modeler for quantification
- Supports Scenario Planner agent
- Integrates with Strategic Options Analyst for strategy testing
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.