Organise project notes with AI
Trace recurring decisions back to their sources and keep a dated record of how your thinking changed across a COG workspace.
If you organise project notes with AI after a busy delivery, ask where a proposed lesson came from. The knowledge-consolidation workflow builds working principles from a selected period of notes in a COG vault. Each one needs a source. A conclusion that seemed sensible after one difficult handover may look different beside a second project that went well.
The result can include a framework, a pattern note or a timeline. It also changes the vault: processed source notes gain metadata and backlinks, and superseded guidance can move to the archive with an explanation. Choose a workspace appropriate for these edits.
What it does
- Locate an idea that appears across several project notes.
- Check a proposed principle against an exception in an earlier entry.
- Document when a particular decision rule is worth using.
- Trace a change in direction through dated sources.
- Retain the route from an archived guide to its replacement.
Install and use
- Enable the skill in a file-capable assistant with permission to read and edit the relevant COG folders. Choose the period and authorised documents.
- Ask, “Review last month’s delivery notes. Which handover problems recurred, and what evidence is there for changing our process?”
- Inspect the source links, revised status fields and archive moves. Amend any inference the original notes do not support.
FAQ
Source
Made by Huy Tieu. Original skill: knowledge-consolidation, published on GitHub under the MIT licence.
View on GitHub