feat: Update communication prompts and rules for clarity and professionalism in US English
This commit is contained in:
@@ -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
|
||||
|
||||
@@ -13,6 +13,8 @@ Read:
|
||||
@prompts/standup.md
|
||||
@ai/AGENTS.md
|
||||
@ai/context/project.md
|
||||
@ai/context/people/manager.md
|
||||
@ai/context/people/jeff-dewitte.md
|
||||
@ai/state/current.md
|
||||
@ai/state/work-items.md
|
||||
@knowledge/communication-rules.md
|
||||
@@ -42,3 +44,4 @@ 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
|
||||
|
||||
@@ -1,8 +1,13 @@
|
||||
---
|
||||
description: Translate rough engineering notes into Mattermost-ready English
|
||||
description: Rewrite rough engineering notes into natural Mattermost-ready US English
|
||||
---
|
||||
|
||||
Translate and tighten the following rough notes into concise Mattermost-ready English:
|
||||
Rewrite and tighten the following rough notes into concise, natural, Mattermost-ready US English.
|
||||
|
||||
Do not translate literally.
|
||||
Rewrite fully when needed so the result sounds like a fluent senior engineer wrote it.
|
||||
|
||||
If the notes mix multiple issues, separate the main issue from unrelated bugs or follow-up work unless the user clearly wants them combined.
|
||||
|
||||
$ARGUMENTS
|
||||
|
||||
|
||||
Reference in New Issue
Block a user