gaia-edit-prd

To edit a PRD without breaking downstream artifacts, you need cascade-aware editing that checks architecture, epics, stories, and test plans for impact. This ensures downstream artifacts reflect changes and maintain traceability across planning artifacts.

Cascade impact analysis in product management documentation verifies that updates to a PRD propagate correctly to architecture.md, epics-and-stories.md, and test-plan.md, ensuring versioning notes and traceability are maintained across all planning artifacts.

Maintaining consistency between epics, stories, and test plans during updates requires delegating PRD edits to a pm subagent and running cascade checks to validate downstream artifacts, ensuring all planning documents remain aligned after changes.

Your product requirements document should be located at docs/planning-artifacts/prd.md to use automated editing workflows, which load the file from this path to verify its structure and dependencies before initiating the edit workflow.

To add version notes to a PRD after modifying product requirements, apply stepwise editing workflows that delegate changes to a pm subagent and produce an updated PRD with a version note attached to track the modification history.

Yes, the PRD editing workflow supports validation gates for downstream test plans by applying dependency checks like validate-gate to ensure downstream artifacts reflect changes and maintain traceability across all planning artifacts.