feat: Update standup guidelines for clarity and audience accessibility

This commit is contained in:
2026-04-17 07:40:31 -06:00
parent a1cec956ab
commit 335f1c1273
5 changed files with 16 additions and 2 deletions

View File

@@ -23,6 +23,8 @@ Requirements:
- Prefer evidence-backed statements over assumptions
- Write in natural US English that can be forwarded externally without rewriting
- Write the standup as David's external progress report
- For standups that will also be sent to Teams, prefer plain outcome language over internal implementation jargon; avoid terms like `fallback` unless they are explained well enough for a broader audience
- If a release or propagation step is waiting on approvals or pipeline work, make the parallel work explicit instead of sounding like the day is blocked on waiting alone
- Do not mention Jeff by name
- Do not mention Mattermost because it is internal-only communication
- Use bullet points for each item