david.delagneau/fidelity-ai-workspace
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

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

Browse Source
This commit is contained in:
David Delagneau
2026-04-09 16:34:35 -06:00
parent ba7553c68b
commit bbb549f033
8 changed files with 75 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
prompts/manager-update.md
View File

@@ -1,8 +1,8 @@
# Manager Update Prompt
Use the current state, today's log, and `ai/context/people/manager.md`.
Use the current state, today's log, `ai/context/people/manager.md`, and `ai/context/people/jeff-dewitte.md`.
Draft a Mattermost update for the current manager or stakeholder in concise professional English.
Draft a Mattermost update for the current manager or stakeholder in concise, natural, professional US English.
Requirements:
@@ -11,4 +11,8 @@ Requirements:
- Clarify whether the issue is external behavior or regression
- Mention auth state when relevant
- Preserve the original technical meaning
- Rewrite awkward or literal wording completely when needed
- Separate the current issue from unrelated bugs, workarounds, and follow-up work unless the user explicitly wants them combined
- Prefer evidence-backed phrasing when the context includes screenshots, logs, comparisons, or repro details
- Make ownership explicit when relevant
- Keep the message direct and short

6
prompts/mattermost-translation.md
View File

@@ -9,6 +9,12 @@ Requirements:
- Prefer concise wording
- Keep the tone professional and direct
- If the draft lacks context, infer only from workspace files and do not invent facts
- Rewrite into natural US English; do not preserve awkward ESL or literal-translation phrasing
- Make the message sound like it was written by a fluent senior engineer
- Separate the main issue from unrelated bugs, workarounds, and follow-up work unless the user explicitly wants them combined
- If relevant, make ownership clear: XFlow vs consumer app vs service/configuration vs other framework
- Prefer explicit statements over vague reassurance; use concrete evidence when the notes include it
- If a sentence could confuse a manager or stakeholder, rewrite it for clarity before returning it
Output:

5
prompts/standup.md
View File

@@ -1,6 +1,6 @@
# Standup Prompt
Use `ai/state/current.md`, `ai/state/work-items.md`, `ai/context/project.md`, `ai/context/people/manager.md`, yesterday's log, today's log if present, and the latest available Mattermost context.
Use `ai/state/current.md`, `ai/state/work-items.md`, `ai/context/project.md`, `ai/context/people/manager.md`, `ai/context/people/jeff-dewitte.md`, yesterday's log, today's log if present, and the latest available Mattermost context.
Generate a standup update for an iOS engineer working on Fidelity.
@@ -13,6 +13,9 @@ Requirements:
- Mention Jira IDs and approved titles when they are available and clearly tied to the reported work
- Prefer story-based reporting when the work maps clearly to a Jira item
- Avoid vague phrases and generic progress language
- Separate the main issue from unrelated follow-up work unless both are explicitly relevant today
- Prefer evidence-backed statements over assumptions
- Write in natural US English that Jeff can forward without rewriting
- Keep it concise and ready to send
Format: