note-todos

Action items from non-meeting notes are extracted by scanning the note content and routing tasks to scope-specific to-do files. The skill processes class notes, book notes, podcasts, and transcripts, automatically assigning owner tags and wikilinks to each extracted task.

The best way to route extracted to-dos to different scopes is to use scope-aware routing based on signals within your notes. The skill directs tasks to personal, team, or consulting to-do files as configured in your vault, ensuring tasks reach the correct scope-specific destination.

Yes, you can use wikilinks and owner tags when capturing tasks from podcasts and transcripts. The skill enforces a self-contained-task rule, ensuring each extracted task includes anchors like file paths, wikilinks, or URLs, and annotates the source note after writing the task.

This workflow explicitly applies to class notes and panel writeups rather than only meeting notes. It generalizes the meeting-todos workflow to non-meeting notes, enabling consistent task capture and routing from sources like book notes, podcasts, and transcripts.

To ensure routed tasks are self-contained and traceable, the skill enforces that each task includes anchors such as file paths, wikilinks, or URLs. It also annotates the source note after writing the task to the scope-specific to-do file, maintaining bidirectional traceability.