Appearance
Real Examples
~6 minutes. What the KB actually produces — meeting notes, people profiles, work boards, and what emerges over time.
These examples show real output formats from the system. Names are fictional, but the structure and depth are representative of what you get after a few weeks of use.
Meeting Notes
After running /process-meeting on a transcript, you get a structured markdown file like this:
Notice the [[wiki-links]] — these connect the meeting to people profiles, project pages, and decision logs automatically.
People Profiles
People files build up over time as you process meetings. After 5-10 meetings with someone, their profile looks like this:
You never write this file directly. It builds itself as you process meetings. After 3 meetings with Elaine, you get basic info. After 8, you have communication patterns, position tracking with strength indicators, and a timeline of interactions.
Work Board
The _System/Work-Board.md file is your at-a-glance view of what's in progress. Skills update it as they process meetings and capture action items.
The /start-day skill reads this board and gives you a morning briefing. The /end-day skill helps you update it. Action items from processed meetings land here automatically.
What Emerges Over Time
The individual files are useful on their own. But the real value comes from what emerges when they accumulate:
🧵
Cross-Meeting Threading
Ask "What happened with the caching discussion?" and Claude traces it across 4 meetings over 3 weeks — from Kramer's initial proposal, through Elaine's skepticism, to the team's decision to defer.
🧠
Stakeholder Memory
Before a difficult conversation with George, Claude surfaces: he's pushed for faster timelines 3 times, he committed to the platform sign-off 5 days ago and hasn't delivered, and he tends to agree in meetings but delay in execution.
🔬
Research Synthesis
File 3 strategy documents over a month. Ask for a synthesis and Claude identifies the common themes, contradictions between them, and which recommendations overlap with your active projects.
⚖️
Decision Archaeology
"Why did we choose approach A over approach B?" Claude finds the original discussion, who advocated for what, what trade-offs were considered, and what's changed since then.
📈
Pattern Recognition
After 40+ meetings, Claude spots patterns you might miss: "You've discussed scope creep in 6 of the last 8 project meetings. The common factor is that requirements aren't locked before design starts."
Unexpected Use Cases
People who've used the system for a few months report use cases they didn't anticipate:
Leadership Self-Coaching
"Summarize how I've handled conflict across the last 10 meetings." Claude reviews your meeting notes and surfaces patterns in how you respond to pushback, disagreements, and difficult conversations. Not therapy — just data about your own behavior.
Live Data During Meetings
While in a meeting, quickly ask Claude: "What did we decide about the latency budget last time?" Instead of scrolling through notes or asking the group, you get an instant answer with the date and context.
Research-to-Brief Pipeline
File a strategy document, two competitor analyses, and a market report over a week. Then: "Build me a brief comparing these three sources against our current roadmap." Claude synthesizes the filed documents with your project context.
Stakeholder Memory Before Difficult Conversations
"What has George committed to in the last month, and what has he actually delivered?" Claude pulls from meeting action items and follow-up notes to give you a factual picture — useful for performance conversations or accountability discussions.
Next: Power Tips — Custom skills, community marketplace, CLAUDE.md best practices, and debugging common issues.