Provide guidance for status updates on deliverables in Duo Chat group

- **8 - Extra large** This is going to take some time and research and probably more than one engineer to complete within the milestone. At this size, we should be looking at how we can split this into smaller issues/tasks.

- **13+ - Too large** This issue is far too complex, large, or under-defined. Anything with a weight of this size should go back to `~workflow::refinement` to be refined and split into more manageable chunks.

### Status updates

To keep stakeholders informed and support async collaboration, all status updates for deliverables in the **current milestone** must be reported directly in the deliverable's issue using the standard template below.

Keeping updates in the issue ensures there is a single source of truth for each deliverable's progress. It avoids status scattered across Slack threads or stand-ups, makes it easy for anyone to catch up asynchronously, and creates a traceable history of how the deliverable evolved throughout the milestone.

#### When to post an update

Post an update whenever there is a meaningful change in status — for example, when work begins, when a risk is identified, when scope changes are being considered, or at regular check-in points during the milestone. At minimum, you should post one update every week.

#### Template

Use the following template when posting your update as a comment in the issue:

```markdown

## Async issue update

- Current status: <describe the deliverable's status>.

- Shipping this milestone: <yes/no>

- Scope reduction opportunities: <yes/no>

/health_status <on_track|at_risk>

/cc <stakeholders for this deliverable>

```

- **Current status** — Briefly describe where things stand. Include what has been completed, what is in progress, and any blockers or dependencies that may affect delivery.

- **Shipping this milestone** — Indicate `yes` if the deliverable is on track to ship within the current milestone, or `no` if it will slip. If the answer is `no`, add a short explanation in the current status field.

- **Scope reduction opportunities** — Indicate `yes` if there are parts of the deliverable that could be descoped to meet the milestone deadline, or `no` if the current scope is the minimum viable delivery. If `yes`, briefly describe what could be reduced.

- **`/health_status`** — Apply `on_track` if the deliverable is progressing as expected, or `at_risk` if there is uncertainty around shipping on time or at full scope.

- **`/cc`** — Tag any team members or stakeholders who should be notified of this update (e.g., PM, EM, designer, downstream teams).

## Troubleshooting Duo Chat

You can find a comprehensive runbook for troubleshooting Duo Chat issues in our [Duo Chat Runbook Page](https://gitlab.com/gitlab-com/runbooks/-/blob/master/docs/duo-chat/README.md?ref_type=heads).