- 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.
17 lines
773 B
Markdown
17 lines
773 B
Markdown
# Daily Context Sync
|
|
|
|
## Goal
|
|
|
|
Keep this workspace aligned with work happening on another machine so AI output stays current and useful.
|
|
|
|
---
|
|
|
|
## Steps
|
|
|
|
1. Capture the main tasks worked on during the day.
|
|
2. Record key debugging findings and open questions.
|
|
3. Sync or copy relevant communication evidence into the inbox or daily log as summarized notes.
|
|
4. Update `vault/01-current/current-work.md` if priorities or concerns changed.
|
|
5. Add any stable learning to `vault/03-context/`, `vault/04-people/`, or `vault/05-decisions/`; if the learning changes reusable workspace behavior, update `core/`, commands, prompts, skills, agent rules, or `vault/03-context/process/` too.
|
|
6. Before asking AI for a standup or manager update, confirm the log reflects the latest state.
|