What problem does it solve?
Keeps scenario change paths localized, cheap, and low-risk by auditing existing structure, identifying primary axes of change, and guiding refactors so future edits avoid shotgun surgery.
Core Features & Use Cases
- Change Axis Discovery: Read the scenario requirements and seams documentation to identify the workflows, integrations, policies, and UI flows most susceptible to evolution.
- Change Topography Mapping: Inspect the current implementation to reveal which files and modules each axis currently touches, highlighting dispersed responsibilities and fragile cross-cutting concerns.
- Structural Localization: Introduce clear extension points, mapping tables, or focused handlers so each axis has obvious change targets and stable cores remain untouched.
- Test and Documentation Hardening: Create behavior-driven tests that capture variation across axes and update the Change Axes documentation so engineers understand where to edit safely.
- Use Case: Before modifying a prompt manager scenario, run this audit to document how each proposed workflow or integration change can be confined to dedicated modules.
Quick Start
Run a change axis and evolution resilience audit by reviewing the scenario seams doc, tracing current implementation impact, and documenting clear extension points.