david.delagneau
b82194bc55
- Created daily log entries for April 13-16, 2026, capturing standup contexts, Mattermost syncs, and ongoing work items. - Established a daily logs index for easy navigation of daily entries. - Introduced templates for daily notes, decisions, meeting notes, people, systems, and work items to standardize documentation. - Developed maps for AI workspace core, current work, Fidelity domain, and work items to enhance workspace navigation. - Implemented base configurations for daily notes, decisions, people, systems, work items, and workstreams to streamline data management. - Added a placeholder for attachments to facilitate file organization.
53 lines
1.8 KiB
Markdown
53 lines
1.8 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
|
|
@ai/AGENTS.md
|
|
@vault/01-current/current-work.md
|
|
@vault/01-current/work-items.md
|
|
@vault/03-context/project.md
|
|
@vault/03-context/workstreams/index.md
|
|
@vault/03-context/process/context-maintenance.md
|
|
@ai/context/index.md
|
|
@ai/context/project.md
|
|
@ai/context/workstreams/index.md
|
|
@ai/context/process/context-maintenance.md
|
|
@ai/work-items/index.md
|
|
@ai/state/current.md
|
|
@ai/state/work-items.md
|
|
@knowledge/agent-memory-rules.md
|
|
@knowledge/memory-promotion-rules.md
|
|
|
|
Today's existing log, if present:
|
|
|
|
!`if [ -f vault/06-daily/$(date +%F).md ]; then cat vault/06-daily/$(date +%F).md; elif [ -f ai/logs/$(date +%F).md ]; then cat ai/logs/$(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 `vault/06-daily/$(date +%F).md`
|
|
- Use `ai/logs/$(date +%F).md` only as temporary compatibility fallback
|
|
- 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
|