david.delagneau
374991a568
- Deleted obsolete files: obsidian-vault.md, onboarding.md, workspace-model.md - Updated opencode.json to remove references to deleted files. - Revised profile.md to clarify the status of legacy paths and communication evidence. - Adjusted prompts to reflect new file paths and improve clarity. - Enhanced daily logs with focus, work-items, and blockers properties. - Updated work-item notes to include systems, workstreams, people, and related properties. - Improved context maintenance guidelines to ensure accurate and durable project knowledge. - Refined base filters to exclude template files and ensure only relevant notes are displayed. - Updated daily templates to ensure proper formatting and consistency. - Modified workflows to align with the new vault structure and improve context synchronization.
19 lines
1005 B
Markdown
19 lines
1005 B
Markdown
# Manager Update Prompt
|
|
|
|
Use the current state, today's daily note, `vault/01-current/work-items.md`, the relevant files under `vault/02-work-items/`, `vault/03-context/project.md`, `vault/03-context/process/communication.md`, `vault/04-people/manager.md`, and `vault/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
|