Claude Cowork workflow — turn the weekly pile of notes, transcripts, and Slack threads into structured knowledge-base entries. ~3 hours per week saved.
TL;DR. Take the pile of notes, transcripts, and Slack threads accumulating each week and turn them into structured KB entries — decisions, processes, FAQs, glossary additions. About 3 hours per week saved for a knowledge-ops lead. KB workflows are easy to start and hard to sustain; the discipline is in the weekly review and merge.
Turn weekly notes into structured knowledge-base entries with cross-links and a change log.
Knowledge ops, EAs, chief of staff, ops lead.
inbox/)#output/)#kb-additions-log.md summarising what was added or updated this weekRead /inbox/notes-[period]/.
For each note, classify into entry type per /CLAUDE.md/taxonomy.
For each classified item, produce one markdown file matching
/CLAUDE.md/kb-style.
Place the file in the correct section of /output/kb-staging/.
Cross-link new entries to existing entries where relevant.
Append a one-line entry per output to /output/kb-additions-log.md.
Plan first; ask before adding any new section.
About 3 hours per week for a knowledge-ops lead.
weekly-kb-sweep skill scheduled Friday.KB workflows are easy to start, hard to sustain. The discipline isn't the prompt — it's the weekly review and merge so the KB doesn't bloat. Build the merge step into the cadence: every fourth weekly run, do a clean-up pass that consolidates near-duplicates. Without that, the KB doubles in size every six months and nobody can find anything.
Book a 30-minute call. We'll ask where you are, what your team needs, and which systems Cowork should touch.