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.
67 lines
3.2 KiB
Markdown
67 lines
3.2 KiB
Markdown
---
|
|
description: Update workspace memory from new facts, corrections, or contextual notes
|
|
---
|
|
|
|
Use this command when new information should become part of the persistent workspace context.
|
|
|
|
Read:
|
|
|
|
@README.md
|
|
@project-knowledge/00-start/start-here.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/systems/index.md
|
|
@project-knowledge/03-context/workstreams/index.md
|
|
@project-knowledge/03-context/workstreams/flow-page-references.md
|
|
@agent-memory/memory/context-maintenance.md
|
|
@project-knowledge/04-people/manager.md
|
|
@project-knowledge/04-people/index.md
|
|
|
|
Today's existing 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`
|
|
|
|
New information to incorporate:
|
|
|
|
$ARGUMENTS
|
|
|
|
Instructions:
|
|
|
|
- use `workspace-memory-curation` when available
|
|
- Treat direct user corrections and learning-session updates as memory sources.
|
|
- For learning-session updates, prefer durable project understanding over transient ticket status.
|
|
- Route durable learning to architecture/process/system/workstream notes; route only truly current operational state to `project-knowledge/01-current/` or `project-knowledge/06-daily/`.
|
|
- If the new information corrects the agent's uncertainty handling or recurring behavior, update the command, prompt, agent, skill, or process rule that controls that behavior.
|
|
- Decide whether the new information belongs in:
|
|
- today's daily note: `project-knowledge/06-daily/$(date +%F).md`
|
|
- current work: `project-knowledge/01-current/current-work.md`
|
|
- work items: `project-knowledge/02-work-items/*.md`
|
|
- active work summary: `project-knowledge/01-current/work-items.md`
|
|
- project overview: `project-knowledge/03-context/project.md`
|
|
- systems: `project-knowledge/03-context/systems/`
|
|
- workstreams: `project-knowledge/03-context/workstreams/`
|
|
- process: `project-knowledge/03-context/process/`
|
|
- manager mapping: `project-knowledge/04-people/manager.md`
|
|
- people roster: `project-knowledge/04-people/index.md`
|
|
- people notes: `project-knowledge/04-people/*.md`
|
|
- decisions: `project-knowledge/05-decisions/`
|
|
- `.opencode/commands/*.md`
|
|
- `prompts/*.md`
|
|
- `.opencode/agents/*.md`
|
|
- `.opencode/skills/*/SKILL.md`
|
|
- Update the appropriate files directly
|
|
- When updating a canonical project note, maintain frontmatter properties used by Obsidian Bases, including `updated`, `systems`, `workstreams`, `people`, `related`, `focus`, `work-items`, and `blockers` when applicable
|
|
- If an existing statement became stale, replace or refine it
|
|
- If the new information changes how this workspace should behave, update the linked command, prompt, agent, skill, or knowledge file that enforces that behavior
|
|
- Do not invent missing facts
|
|
- Keep uncertain information in the daily log instead of promoting it to stable context
|
|
- Do not ask for promotion confirmation when the correct destination is already clear
|
|
- Prefer correcting canonical memory over appending duplicate summaries
|
|
|
|
After editing, respond with:
|
|
|
|
1. Updated files
|
|
2. What changed in the persistent context
|
|
3. Any uncertainty that remains
|