dogent-release-planning

Coordinate release planning inside a repo by outlining sprint design, sprint plans, and UAT artifacts within repository docs to keep context intact and ensure traceable decisions.

Updating sprint design and sprint plan docs involves processing requirement updates and mirroring them across planning artifacts in a dependency-ordered, testable manner to ensure aligned design.

Conflict detection for underspecified requirements works by identifying contradictions in planning docs and prompting for clarification before editing to prevent scope creep and misaligned design.

Yes, you can update dev/sprint_uat.md without modifying source code, as the workflow ensures updates are reflected only in planning docs and never edits source code outside these artifacts.

No external dependencies are needed to manage sprint design and repo planning docs, as the workflow operates entirely within the repository using standard markdown planning artifacts.

Maintaining release requirements in dev/requirement.md prevents context loss by keeping decisions traceable, aligned, and directly accessible inside the repository planning docs.