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

prompts/standup.md

@@ -11,11 +11,20 @@ Requirements:
 - Mention debugging findings only if they materially changed understanding
 - Clarify auth-dependent behavior when relevant
 - Mention Jira IDs and approved titles when they are available and clearly tied to the reported work
+- Prefer including story titles whenever a reported update maps clearly to a Jira item
 - Prefer story-based reporting when the work maps clearly to a Jira item
+- Prefer updates directly tied to active work items over side questions, context refreshes, or manager-only reminders
+- If documentation or root cause updates directly support a story, group that work under the related story instead of reporting it as a separate unrelated item
 - Avoid vague phrases and generic progress language
 - Separate the main issue from unrelated follow-up work unless both are explicitly relevant today
+- Omit standup items that are not directly related to a story unless they are a real blocker
 - Prefer evidence-backed statements over assumptions
-- Write in natural US English that Jeff can forward without rewriting
+- Write in natural US English that can be forwarded externally without rewriting
+- Write the standup as David's external progress report
+- Do not mention Jeff by name
+- Do not mention Mattermost because it is internal-only communication
+- Use bullet points for each item
+- When pairing a Jira ID with a title, prefer `ID - Title` or `ID Title`; do not use commas between them
 - Keep it concise and ready to send
 
 Format: