david.delagneau
1ad707373a
- Created daily log entries for May 13, 14, 18, 19, 20, and 21, capturing work done, findings, and next steps. - Established a daily logs index for easy navigation of daily notes. - Developed templates for daily logs, decisions, meeting notes, people, systems, and work items to standardize documentation. - Introduced base files for filtering and displaying various types of project knowledge, including daily notes, decisions, people, systems, work items, and workstreams. - Added maps for current work, fidelity apps, and fidelity domain to enhance project navigation and context.
19 lines
1.2 KiB
Markdown
19 lines
1.2 KiB
Markdown
# Manager Update Prompt
|
|
|
|
Use the current state, today's daily note, `workspaces/fidelity/project-knowledge/01-current/work-items.md`, the relevant files under `workspaces/fidelity/project-knowledge/02-work-items/`, `workspaces/fidelity/project-knowledge/03-context/project.md`, `workspaces/fidelity/project-knowledge/03-context/process/communication.md`, `workspaces/fidelity/project-knowledge/04-people/manager.md`, and `workspaces/fidelity/project-knowledge/04-people/index.md`.
|
|
|
|
Draft a Mattermost update for the current manager or stakeholder in concise, natural, professional US English.
|
|
|
|
Requirements:
|
|
|
|
- Structure around Context, Observation, and Action
|
|
- Make scope explicit
|
|
- 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
|