Scenario & Usecase Navigation

PowerX combines Scenarios (SCN) and Usecase Seeds to turn product intent into executable specifications that drive implementation, testing, and operations.

Overview

• Specification-Driven: We follow GitHub Spec Kit’s Specification-Driven Development (SDD). Specs are the single source of truth; code, tests, and operational scripts are derived from them.
• Scenarios Tell the Story: Scenario docs describe the end-to-end journey—participants, prerequisites, flow, and acceptance criteria are unified in one place.
• Usecase Seeds Deliver: Seeds break scenarios into minimal deliverables, enabling cross-team collaboration and reuse.
• Docmap Orchestrates: docs/_data/docmap.yaml maintains the mapping between scenarios and Seeds. It is the canonical source for generation, indexing, and publishing.
• Further Reading: For step-by-step instructions see Scenario Usage Guide together with the authoring guide and Seed generation guide referenced below.

Scenario Catalog

The sidebar automatically lists every scenario registered in docmap.yaml and groups entries by SCN_ID. Child scenarios and Seeds appear beneath each item for direct navigation. Maintenance tips:

• Edit the source files in docs/scenarios/** first, then use the automation scripts to sync into docs/website/**. Avoid manual copy/paste that can drift from the source of truth.
• When adding a new scenario, remember to update docmap, generate Seeds, and rebuild the index so the catalog stays in sync.
• Useful references:
  • Scenario Usage Guide
  • Scenario Authoring Guide
  • Generate Usecase Seeds
  • Usecase Seed Index Maintenance
  • Standards Distribution Guide