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.
19 lines
1.1 KiB
Markdown
19 lines
1.1 KiB
Markdown
# Manager Update Prompt
|
|
|
|
Use the current state, today's daily note, `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/process/communication.md`, `project-knowledge/04-people/manager.md`, and `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
|