Weekly Team Sync
Meeting notes with front-matter properties, a decision callout, an agenda table and action items, two of them ticked off after the meeting and one decision commented on.
`note.write` lays down the notes in Obsidian-flavoured Markdown: properties for the date, attendees and project, an agenda table, a decision callout and a task list with owners. After the meeting `task.toggle` ticks two actions, `property.set` marks the notes as reviewed and `comment.add` starts a thread on the decision. The inspection counts the tasks, tables and callouts and the open comment thread.
Steps
6 commandssteps:
- command: note.write
params:
markdown: |
---
date: 2026-11-09
project: Tidewater app
attendees: [Noor, Bastian, Ilse, Keoni]
status: draft
---
# Weekly Team Sync
Monday stand-up for the **Tidewater** tide-tables app. Notes by Ilse; next sync on the 16th.
## Agenda
| Topic | Lead | Minutes |
| :-- | :-- | --: |
| Beta feedback round-up | Noor | 10 |
| Offline mode estimate | Bastian | 15 |
| Store listing copy | Keoni | 5 |
## Decisions
> [!IMPORTANT] Offline mode ships in 2.3
> We cache the next fourteen days of tide data per saved harbour. Older data is dropped on launch.
> [!NOTE] Beta feedback
> 41 replies so far. The most requested change is a larger font on the chart labels.
## Action items
- [ ] Noor: group the beta replies by theme and share the top five
- [ ] Bastian: spike the cache size for 50 harbours
- [ ] Keoni: draft the store listing in English and Welsh
- [ ] Ilse: book the usability session with the sailing club
- [ ] Everyone: try the nightly build on a real boat this weekend
## Parking lot
- Dark mode for night sailing
- Widget for the lock screen
- { command: tasks.list, as: before }
- { command: task.toggle, params: { line: $before.tasks.0.line, done: true }, as: first }
- { command: task.toggle, params: { line: $before.tasks.3.line, done: true }, as: second }
- { command: property.set, params: { key: status, value: reviewed } }
- { command: comment.add, params: { quote: "Older data is dropped on launch.", body: "Should we keep the last viewed day so the app is never empty offline?", author: Noor }, as: thread }Checks
10 checks on every buildinspect.heading= "Weekly Team Sync"inspect.headings= 5inspect.tables= {"count":1,"all":{"columns":3,"rows":4}}inspect.callouts= 2inspect.tasks= {"done":2,"open":3}inspect.properties= {"count":4,"any":{"key":"attendees","type":"list"}}inspect.comments= {"open":1}results.before.tasks= {"count":5}- Diagnostics: none, the kit's own check finds nothing wrong
- The saved document opens again, and its thumbnail matches
thumb.pngwithin the render tolerance
Related
More Note samplesDaily Journal Entry
A daily note with typed properties for mood, sleep and weather, a morning intention, highlighted thoughts, a quote and a short habit tracker.
Spanish Study Notes
Spanish vocabulary notes for a beginner's course, with words, word types and meanings in a table, example sentences in callouts and a review task list.
Lakeside Camping Checklist
A packing checklist for a three-night canoe camping trip, with tasks nested under each bag, half of them already packed and one section moved to the top.
Mechanics Revision Formulas
A revision sheet of mechanics formulas set as display and inline LaTeX math, with a worked example in a callout and a symbol table.