What problem does it solve? Cross-feature regression flows are usually tied to a single feature and get lost or duplicated, leaving no global, compiled, runnable record of end-to-end user behavior across an implemented product. ## Core Features & Use Cases - Journey lifecycle management: Create, edit, list, inspect, and impact-check global User Journeys v2 stored under .specs/journeys/ with decision and changelog evidence. - Bootstrap from existing code: Scan implemented features, specs, Gherkin, tests, routes, and Penflow contracts to propose journey candidates for already-built functionality. - Compile-once, run-native execution: Compile journeys on create or edit, then run compiled artifacts deterministically without recompilation, including XCUITest generation via xcodegen. - Use Case: After shipping several features, run $spec-journey bootstrap --from-existing to propose cross-feature regression journeys, accept candidates, and run them as non-regression tests. ## Quick Start Ask the AI to create a new cross-feature user journey with $spec-journey create and confirm the inferred features and acceptance criteria before it writes the journey.
