feat: Update communication prompts and rules for clarity and professionalism in US English

This commit is contained in:
2026-04-09 16:34:35 -06:00
parent ba7553c68b
commit bbb549f033
8 changed files with 75 additions and 6 deletions

View File

@@ -2,7 +2,7 @@
description: Draft or polish a Mattermost update for the current manager or stakeholder
---
Draft a concise Mattermost message for the current manager or stakeholder in natural professional English.
Draft a concise Mattermost message for the current manager or stakeholder in natural, manager-ready US English.
Read:
@@ -10,6 +10,7 @@ Read:
@ai/AGENTS.md
@ai/context/project.md
@ai/context/people/manager.md
@ai/context/people/jeff-dewitte.md
@ai/context/people/index.md
@ai/state/current.md
@ai/state/work-items.md
@@ -33,6 +34,10 @@ Requirements:
- Use Context, Observation, Action
- Clarify scope
- Preserve technical meaning
- Rewrite fully when needed so the result sounds like a fluent senior engineer wrote it
- Separate the current issue from unrelated bugs, workarounds, and follow-up work unless the user clearly wants them combined
- Prefer evidence-backed wording over intuition when context includes concrete findings
- Make ownership explicit when relevant: XFlow vs consumer app vs service/configuration vs another framework
- Mention auth state when relevant
- Mention Jira IDs and approved titles when they materially improve clarity
- Do not label something a regression unless the context supports it