gaia-edit-ux

To edit an existing UX design safely, you need a cascade-impact check across architecture.md, epics-and-stories.md, and test-plan.md. This orchestrates multi-step edits while delegating reasoning to a subagent to evaluate change impact and validate consistency.

Cascade impact assessment in UX design editing evaluates how changes to ux-design.md affect downstream artifacts like architecture.md, epics-and-stories.md, and test-plan.md. It enforces consistency by validating that structural updates do not invalidate dependent planning documents.

You apply surgical edits by specifying the exact changes and confirming their cascade implications. The system loads the existing ux-design.md, applies the validated edits, and writes a versioned update back to the same path with memory-backed state history.

Editing a UX design document requires an existing ux-design.md file at docs/planning-artifacts/ux-design.md. While it enforces cascade-aware consistency checks against architecture.md, epics-and-stories.md, and test-plan.md, the primary precondition is the presence of the UX design artifact itself.

UX design changes cause inconsistencies when edits bypass cascade-aware validation across epics-and-stories.md and test-plan.md. Without enforcing a multi-step edit flow that assesses downstream impact, structural modifications to the UX artifact silently invalidate dependent planning documents.

You can preserve existing content structure during a UX design update by enforcing deterministic load and write operations. The system emits a versioned update after every edit session, ensuring the original artifact structure remains intact while applying the specified surgical changes.