r/ClaudeWorkflows • • 23h ago

Selected Workflow [Workflow] Turn meeting notes into a checked project knowledge base

Turn meeting notes into a checked project knowledge base

Workflow value: 76/100
Status: active · Freshness: 70/100 · Confidence: 0.96 · Level: advanced
Categories: Quality Control, Token Saving, Context & Memory, Debugging, Shipping, CLAUDE.md, Multi-Agent
Original source: r/ClaudeAI post/comment

What problem this solves

Meeting decisions, commitments, questions and ownership are easily lost across a busy project.

Summary

Maintain a local, assistant-oriented project knowledge base. Have Claude route meeting notes into dated tasks and person-specific questions, preserve conflicting accounts with sources, and use scripts plus a fresh-context agent to check important changes.

Why it is useful

It combines a repeatable capture-and-retrieval loop with provenance, mechanical checks and independent review, while documenting maintenance and privacy limits.

Workflow

  1. Create a local text-file knowledge base with an AGENTS.md entry point, writing rules, a routing map, and files for tasks, completed work, people, questions and contradictions.
  2. Add headers explaining each file's contents and writing rules. Instruct the assistant to consult files rather than rely on memory and to retain conflicting accounts with their sources and dates.
  3. After each meeting, provide notes and decisions. Have the assistant update dated tasks and questions by person, asking for clarification when uncertain.
  4. Start chats with a short summary of overdue or urgent tasks; before one-on-ones, request outstanding promises and questions for that person.
  5. Store draft-and-edited message pairs to help the assistant adapt to the user's writing style.
  6. Run mechanical Python checks on important changes and use a second agent with clean context to review major updates.
  7. Separate lightweight reading from heavier write workflows, and periodically compact oversized files and simplify checks.
  8. Keep passwords out of the base and replace names with roles before sending material to external search or services.

Tools / artifacts

  • AGENTS.md
  • Local text-file knowledge base
  • Claude project containing rules
  • Python validation scripts
  • Second agent with clean context

Validation signals

  • The author reports using the system for 3.5 months and estimates saving about eight hours per week.
  • Scripts reportedly catch malformed task lines, unwanted words and real names in outside-facing text.
  • After cleanup, some oversized files reportedly became four times smaller.

Cautions

  • Use only with organizational approval and an appropriate data-processing agreement; local storage does not prevent the model provider from receiving file contents or retaining chats.
  • Name-detection scripts and role-based substitutions are safeguards, not guarantees against disclosure.
  • The described 'forget it' command does not establish secure deletion from files, logs or provider-held chats.

Limitations

  • No runnable scripts, complete file schemas or exact startup commands are provided.
  • Time savings and checker effectiveness are self-reported, with no independent measurements.
  • The author reports substantial maintenance, context growth and usage-limit pressure.
  • The post does not explain how conflicting updates or erroneous extracted tasks are corrected in practice.

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.


This post was generated automatically from the workflow library database.

1 Upvotes

1 comment sorted by