wds-3-scenarios

Run the create workflow, which loads your Product Brief and Trigger Map, builds strategic context chains linking business goals to personas, and guides you through an 8-question dialog per scenario. User checkpoints at scope analysis and scenario plan approval ensure alignment before any files are written.

It requires a completed Phase 1 Product Brief and Phase 2 Trigger Map, plus the WDS config.yaml defining project name, output folder, and language settings. The workflow halts with an error if either prerequisite artifact is missing.

Invoke the workflow with the validate flag to run the validation path. It checks strategic context coverage, navigation patterns, outline completeness, and cross-scenario consistency, then generates a report with severity levels for each finding.

Persona-based naming keeps user psychology front-of-mind during design and is enforced by a naming gate in the workflow. Feature-first names like "Emergency Booking Flow" are rejected in favor of formats like "Hasse's Emergency Search".

Each scenario is scored on four dimensions: completeness (minimum 6/7), quality criteria (minimum 5/7), mistakes avoided (all 7 required), and best practices (minimum 2/4). Scenarios failing thresholds must be fixed before the phase completes.

Yes, the scope analysis step applies a selective ignorance strategy for large sites, focusing deep scenario work on the most valuable workflow rather than covering every page. Small and medium sites use comprehensive coverage instead.