david.delagneau
8026da5719
- Introduced new commands and skills for workspace memory curation, professional communication, and status reporting. - Updated existing commands to utilize new skills and improve clarity in instructions. - Created a new workspace context command to load reusable core and active project profile. - Enhanced Mattermost inbox integration with support for generic environment variables. - Established a clear separation between project-independent core logic and project-specific profiles. - Improved documentation across various files to reflect changes in workflow and command usage. - Added operational memory management rules to ensure accurate context promotion and correction. - Updated README and workflow documents to guide users in utilizing the new structure effectively.
47 lines
1.5 KiB
Markdown
47 lines
1.5 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
|
|
@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 ai/logs/$(date +%F).md ]; then cat ai/logs/$(date +%F).md; else echo "No log 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 `ai/logs/$(date +%F).md`
|
|
- 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
|