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

feat: Update standup prompt and related documentation for clarity and improved context handling

Browse Source
This commit is contained in:
David Delagneau
2026-04-21 08:11:07 -06:00
parent f68fd4da9c
commit b264d380bc
5 changed files with 107 additions and 28 deletions
Download Patch File Download Diff File Expand all files Collapse all files

68
prompts/standup.md
View File

@@ -1,41 +1,67 @@
# Standup Prompt
Use `project-knowledge/01-current/current-work.md`, `project-knowledge/01-current/work-items.md`, the relevant files under `project-knowledge/02-work-items/`, `project-knowledge/03-context/project.md`, `project-knowledge/03-context/workstreams/index.md`, `project-knowledge/03-context/process/communication.md`, `project-knowledge/04-people/manager.md`, the previous workday Mattermost context, today's daily note if present, and the latest available Mattermost context.
Use `project-knowledge/01-current/current-work.md`, `project-knowledge/01-current/work-items.md`, the detailed files referenced from that active-work summary, `project-knowledge/03-context/project.md`, `project-knowledge/03-context/workstreams/index.md`, `project-knowledge/03-context/process/communication.md`, `project-knowledge/04-people/manager.md`, the previous workday Mattermost context, today's daily note if present, and the latest available Mattermost context.
Generate a standup update for an iOS engineer working on Fidelity.
Requirements:
## Output contract
- Return exactly three sections in this order: `Yesterday:`, `Today:`, `Blockers:`
- Return Markdown that is ready to copy/paste directly into Mattermost
- Use one top-level bullet per Jira item
- Use indented sub-bullets only when they improve clarity
- Prefer one concise sub-bullet when nearby events are part of the same continuous context
- Keep sub-bullets in chronological order within each Jira item
- Keep the whole standup concise and ready to send
## Selection rules
- Use the most recent context only
- Be specific about what was worked on during the previous workday, not necessarily the previous calendar day
- `Yesterday` must describe work that actually happened on the previous workday, not older status changes that still appear in current memory
- On Mondays, use Friday's work context unless a later prior day has Mattermost activity
- If the previous calendar day has no work activity or is OOO/weekend, use the latest prior day with Mattermost activity
- Mention debugging findings only if they materially changed understanding
- Clarify auth-dependent behavior when relevant
- Treat the previous workday communication context as the primary source for `Yesterday`
- Use current memory to disambiguate, not to backfill unrelated older events
- Prefer updates directly tied to active work items over side questions, context refreshes, or manager-only reminders
- Exclude items that are not directly tied to a story unless they are true blockers
- Do not mention stories assigned to a future sprint unless they are a real blocker for today's work
- Do not include `Today` items that are known not to be worked on today
## Story handling rules
- 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
- If documentation, root-cause analysis, or implementation analysis directly supports a story, group that work under the related story instead of listing it separately
- When one Jira item has multiple concrete updates, keep them under one top-level `JIRA-ID - Title` bullet
- When pairing a Jira ID with a title, prefer `ID - Title` or `ID Title`; do not use commas between them
## Writing rules
- Write in natural US English that can be forwarded externally without rewriting
- Write the standup as David's external progress report
- For standups that will also be sent to Teams, prefer plain outcome language over internal implementation jargon; avoid terms like `fallback` unless they are explained well enough for a broader audience
- Be specific, concise, and evidence-backed
- Avoid vague phrases and generic progress language
- Mention debugging findings only if they materially changed understanding
- Clarify auth-dependent behavior when relevant
- Separate external issues from regressions when that distinction matters
- For standups that may also be sent to Teams, prefer plain outcome language over internal implementation jargon; avoid unexplained terms like `fallback`
- If a release or propagation step is waiting on approvals or pipeline work, make the parallel work explicit instead of sounding like the day is blocked on waiting alone
- Do not mention Jeff by name
- Do not mention Mattermost because it is internal-only communication
- Use bullet points for each item
- When one Jira item has multiple concrete updates, use one top-level Jira bullet and indented markdown sub-bullets instead of repeating the same Jira ID/title multiple times
- When pairing a Jira ID with a title, prefer `ID - Title` or `ID Title`; do not use commas between them
- Keep the sub-bullets in chronological order within each Jira item
- Do not mention stories assigned to a future sprint unless they are a real blocker for today's work
- Do not include "today" items that are known not to be worked on today
- Return Markdown that is ready to copy/paste directly into Mattermost
- Prefer one concise sub-bullet when nearby events are part of the same continuous context; split into multiple sub-bullets only when separation improves clarity
- Keep it concise and ready to send
## Compression rules
- Combine closely related events into one sentence when they share the same context and timeline
- Split into multiple sub-bullets only when separation improves accuracy or readability
- Prefer direct chronological phrasing such as `Started by...`, `Then...`, `Later...` when that keeps one bullet accurate and concise
## Anti-patterns to avoid
- Do not report a story as worked yesterday just because it is now `Done`
- Do not pull old closure events from durable memory into a new standup unless they happened on the previous workday
- Do not mention next-sprint work in `Today` when today's plan is already known and different
- Do not turn context notes into fake progress lines
Format: