@@ -283,6 +283,19 @@ The Engineering DRI works with the Product Designer throughout the `workflow:in
If we find that solutions are consistently not matching the agreed upon design, we will hold a retrospective with the DRI, designer, and product manager to discuss where the gaps in communication are so that we can improve. It may be necessary to begin requiring a UX approval for merge requests on certain issues to help the Engineering DRI meet the requirements.
#### Issue closure with Feature Flag rollouts
While the [official guidance](/handbook/product-development/how-we-work/product-development-flow/feature-flag-lifecycle/#flowchart) allows flexibility, our team's default is to **keep feature issues open until flag removal is complete**.
This approach:
1. Makes it easier for users to understand the availability of features/fixes
1. Keeps remaining work (rollout monitoring, FF removal) visible for planning
This is not a hard rule: For example, a low-priority issue with imminent rollout completion
can be closed earlier at your discretion. But the easy default to avoid having to make any
judgement calls is to keep the issue open until the removal has concluded.
#### Duo Agentic Chat Prompts
See [Duo Prompts](/handbook/engineering/devops/verify/pipeline-authoring/duo-prompts/).
