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.
43 lines
1.6 KiB
Markdown
43 lines
1.6 KiB
Markdown
---
|
|
description: Update today's log from rough notes or contextual notes
|
|
---
|
|
|
|
Use this command for quick same-day note capture.
|
|
|
|
Read:
|
|
|
|
@README.md
|
|
@core/README.md
|
|
@core/memory/operational-memory.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
|
|
@agent-memory/memory/context-maintenance.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`
|
|
|
|
Incorporate these new rough notes into today's log:
|
|
|
|
$ARGUMENTS
|
|
|
|
Instructions:
|
|
|
|
- use `workspace-memory-curation` when available
|
|
- Update or create `project-knowledge/06-daily/$(date +%F).md`
|
|
- Maintain daily-note frontmatter for Obsidian Bases: `date`, `focus`, `work-items`, `blockers`, and `updated`
|
|
- Preserve concrete technical meaning
|
|
- Capture both technical findings and communication context when relevant
|
|
- Keep the log concise but reusable for later standups and manager updates
|
|
- If the notes are ambiguous, normalize them without inventing facts
|
|
- If a note clearly corrects or sharpens existing current memory, update the corresponding canonical file as well
|
|
- If a note reveals durable system, workstream, process, or people context, update the relevant canonical file instead of only appending to the log
|
|
- Prefer `sync-context` for broader memory updates; use this command for fast daily capture
|
|
|
|
After editing, respond with:
|
|
|
|
1. What was added or clarified
|
|
2. Whether any broader memory was also updated
|