feat: Update standup and work item documentation for clarity and story prioritization

This commit is contained in:
2026-04-10 07:42:03 -06:00
parent dcd2bcf3cc
commit 26f54ed302
6 changed files with 47 additions and 6 deletions

View File

@@ -37,6 +37,9 @@ Before drafting:
- update workspace memory if the refreshed context introduced clear high-confidence project facts
- prefer existing memory when the latest context is ambiguous
- mention Jira IDs and approved titles when they map cleanly to yesterday's work
- prioritize story-based updates over side questions, memory refreshes, or manager-only context
- if documentation or root cause updates directly support a story, roll them into that story's update instead of listing them separately
- exclude items that are not directly tied to a story unless they are true blockers
Return a standup that is:
@@ -44,4 +47,9 @@ Return a standup that is:
- concise
- grounded in the latest context
- safe to send without overstating certainty
- written in natural US English that Jeff could forward without rewriting
- written in natural US English that can be sent externally without rewriting
- written as David's progress report
- free of any mention of Jeff by name
- free of any mention of Mattermost, since it is internal-only communication
- uses bullet points for each item
- uses `JIRA-ID - Title` or `JIRA-ID Title` formatting instead of comma-separated ID/title formatting