dogent-story-acceptance

To fix UAT bugs and update sprint documentation, you read the latest issues from dev/sprint_uat.md, implement minimal scoped code fixes, update automated tests, and record retest guidance before closing acceptance statuses.

Marking a sprint story as Accepted requires reading sprint design and UAT docs, resolving all reported issues, updating manual test records in dev/sprint_uat.md, and verifying that every UAT passes before changing the status.

Managing post-UAT issue fixes involves interpreting UAT results from sprint docs, applying targeted code edits, refreshing automated tests, and updating sprint files with clear fix statuses and retest instructions to align stakeholders.

Yes, you can update manual test records directly in dev/sprint_uat.md. After applying minimal scoped fixes, you refresh the test records and append clear retest guidance to ensure stakeholders validate the changes.

If UAT bugs are not fixed, you must not mark the release as accepted. You need to apply targeted fixes, update the sprint documentation with retest guidance, and await successful retest results before closing acceptance.

Yes, it works with existing sprint design and plan documents. It reads sprint design, plan, and UAT docs to drive targeted bugfixes, update tests, and manage acceptance statuses within current Dogent release workflows.