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

@@ -49,6 +49,8 @@ Before drafting:
- exclude items that are not directly tied to a story unless they are true blockers
- when one Jira item has multiple concrete updates, group them under one top-level `JIRA-ID - Title` bullet with indented markdown sub-bullets instead of repeating the same Jira line
- use `vault/03-context/workstreams/flow-page-references.md` to preserve real flow/page identifiers when shorthand appears in logs or messages
- for standups that will also be sent to Teams, prefer plain language over internal implementation jargon; avoid unexplained terms like `fallback`
- if work is in release-process waiting state, show the parallel story work explicitly instead of implying idle waiting
Return a standup that is: