david.delagneau
dbc1894e27
- Introduced new maps for navigating project knowledge, including "Current Work," "Fidelity Domain," "Fidelity Apps," "Work Items," and "People." - Created base files for daily notes, decisions, people, systems, work items, and workstreams with defined properties and views. - Developed templates for daily notes, decisions, meeting notes, persons, systems, work items, and workstreams to standardize documentation. - Updated scripts and prompts to reflect the new project-knowledge directory structure. - Removed outdated onboarding and start-here documents, consolidating relevant information into the new maps. - Ensured all references in workflows and scripts point to the new project-knowledge paths.
54 lines
2.2 KiB
Markdown
54 lines
2.2 KiB
Markdown
---
|
|
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, manager-ready US English.
|
|
|
|
Use `professional-communication` when available.
|
|
|
|
Read:
|
|
|
|
@prompts/manager-update.md
|
|
@project-knowledge/01-current/current-work.md
|
|
@project-knowledge/01-current/work-items.md
|
|
@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
|
|
@project-knowledge/04-people/index.md
|
|
|
|
Today's log, if present:
|
|
|
|
!`if [ -f project-knowledge/06-daily/$(date +%F).md ]; then cat project-knowledge/06-daily/$(date +%F).md; else echo "No daily note exists for today yet."; fi`
|
|
|
|
Latest Mattermost context, if available:
|
|
|
|
!`if [ -s ai/inbox/mattermost-latest.md ]; then cat ai/inbox/mattermost-latest.md; elif [ -s scripts/mattermost/generated/mattermost_context.jsonl ]; then cat scripts/mattermost/generated/mattermost_context.jsonl; else echo "No Mattermost context available."; fi`
|
|
|
|
Detailed active work item files, if available:
|
|
|
|
!`if [ -d project-knowledge/02-work-items ]; then for f in project-knowledge/02-work-items/*.md; do case "$f" in *README.md|*index.md) continue;; esac; echo "\n### $f"; cat "$f"; done; else echo "No work item files available."; fi`
|
|
|
|
User draft or rough notes:
|
|
|
|
$ARGUMENTS
|
|
|
|
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
|
|
- Keep the result short enough for Mattermost
|
|
|
|
Return:
|
|
|
|
1. Final message
|
|
2. One-line note with any assumption you had to make
|