Files
fidelity-ai-workspace/.opencode/commands/log-note.md
david.delagneau 374991a568 Refactor workspace structure and documentation
- 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.
2026-04-16 16:28:30 -06:00

1.5 KiB

description
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 @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

Today's existing log, if present:

!if [ -f vault/06-daily/$(date +%F).md ]; then cat vault/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 vault/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