skills.rest
michalo1334
michalo1334COMMUNITY
Explore all skills by this author →
GitHub

maintaining-scenario-index

Synchronizes scenario index, diagrams, and validator scripts when scenario-facing code changes.

Updated May 16, 2026
Search Tags:#documentation#validation#maintenance#impact analysis#diagrams#scenario index
One-click install
npx skills add https://github.com/michalo1334/ScenarioImpactDSL --skill maintaining-scenario-index-michalo1334
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: maintaining-scenario-index
Source: https://github.com/michalo1334/ScenarioImpactDSL/tree/main/.opencode/skills/maintaining-scenario-index
Command: npx skills add https://github.com/michalo1334/ScenarioImpactDSL --skill maintaining-scenario-index-michalo1334

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When scenario-relevant slices, tests, diagrams, or validation rules change, the scenario navigation package can drift out of sync, leaving stale index entries, broken diagram links, and outdated validators. ## Core Features & Use Cases - Coordinated Updates: Keeps the module-scenario map index, scenario diagram files, validator script, and validator tests updated together as one unit. - Validation Enforcement: Runs the scenario index validator against the index and diagram directory to confirm structural integrity after edits. - Surgical Editing Guidance: Prevents broad rewrites and unrelated reformatting by scoping edits to affected scenario entries only. - Use Case: After adding a new business-flow scenario to the shipping system, update the index entry and its diagram, adjust the validator if link rules changed, and run the validation command to confirm everything passes. ## Quick Start Update the scenario index and diagrams for the new payment-capture scenario, keep the validator and its tests in sync, and run the validation command to confirm the package is consistent.

Frequently Asked Questions about maintaining-scenario-index

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

FAQPage Schema
How do I update a scenario index when business-flow code changes?▼

Update the affected entries in the module-scenario map index and the corresponding scenario diagram files together. If anchors, link targets, or validation rules changed, also update the validator script and its tests, then run the validation command to confirm consistency.

How do I validate a scenario index and diagram structure?▼

Run the validator script with the index file and diagram directory as arguments: python3 scripts/validate_scenario_index.py with the --index and --diagram-dir flags. It checks that index entries and diagram files conform to the required structure.

When should the scenario validator tests be updated?▼

Update validator tests in the same task whenever validation rules, anchors, link targets, or required structure change. Changing validation logic without updating its tests leaves the package inconsistent and can hide regressions.

What are common mistakes when maintaining scenario documentation?▼

Common mistakes include updating docs but skipping the validator run, changing validation rules without updating tests, syncing code without scenario docs, and broadly rewriting unrelated scenario files instead of making surgical edits.

Related Skills

Explore More Software Engineering Skills→
MDLDev-siteMDLDev-site

gitnexus-impact-analysis

Map code change blast radius and identify affected callers and execution flows.

Official
Advanced
mindfold-aimindfold-ai
14.4k

gitnexus-impact-analysis

Analyzes code change blast radius using GitNexus dependency graphs and execution flows.

Official
Intermediate
FaysilAlshareefFaysilAlshareef
4

diagram-gen

Generate Mermaid diagrams for architecture, event flows, and sequence diagrams.

Community
Intermediate
angrysky56angrysky56

ingest-agent

Ingest raw inbox files into a wiki knowledge base and Neo4j graph database.

Community
Advanced