A self-organizing Obsidian vault that gives AI coding agents persistent memory.
TypeScript ai-agentsclaude-codecodex-cligemini-cliknowledge-managementobsidianobsidian-vaultpersistent-memorysecond-braintemplate
Add performance graph: competency notes, graph-native linking, review structure
Brenno Ferraria7c2da75c611
diff --git a/CLAUDE.md b/CLAUDE.mdindex 7f07d01..6361c66 100644--- a/CLAUDE.md+++ b/CLAUDE.md@@ -18,9 +18,10 @@ This vault has [obsidian-skills](https://github.com/kepano/obsidian-skills) inst|--------|---------|-----------|| `work/` | Work notes, project tracking | `Index.md` (MOC) || `perf/` | Performance reviews, brag doc | `Brag Doc.md`, `Review Template.md` |+| `perf/competencies/` | Atomic competency notes (link targets for work notes) | One note per competency || `claude/` | Claude-facing context | `Memories.md`, `Skills.md`, `North Star.md` || `thinking/` | Claude's scratchpad for drafts and reasoning | Named `YYYY-MM-DD-topic.md` |-| `templates/` | Obsidian templates | `Work Note.md`, `Decision Record.md`, `Thinking Note.md` |+| `templates/` | Obsidian templates | `Work Note.md`, `Decision Record.md`, `Thinking Note.md`, `Competency Note.md` |## Obsidian CLI@@ -61,6 +62,7 @@ Before wrapping up a session where meaningful work was done:3. Update `perf/Brag Doc.md` if wins or impact were achieved4. Offer to update `claude/North Star.md` if goals shifted or new focus emerged5. Verify all new notes link to at least one existing note+6. If work demonstrates competencies, add competency links to the work note's `## Related`Skip steps that don't apply. The goal is transferring durable knowledge from conversation to vault state.@@ -79,11 +81,18 @@ Use `thinking/` for drafts, reasoning, and analysis before writing final notes.1. **Always use YAML frontmatter** with at minimum `date`, `description` (~150 chars), `tags`, and type-specific fields.2. **Use templates** from `templates/`. Fill `{{placeholders}}` with real values.-3. **Place files correctly**: work notes and decisions in `work/`, drafts in `thinking/`, perf content in `perf/`, Claude context in `claude/`. Nothing in vault root except this file.+3. **Place files correctly**: work notes and decisions in `work/`, drafts in `thinking/`, perf content in `perf/`, competency notes in `perf/competencies/`, Claude context in `claude/`. Nothing in vault root except this file.4. **Name files descriptively.** Use the note title as filename.### Linking -- This Is Critical+**Graph principle**: This vault is a graph, not a wiki. A note's value comes from its connections, not its length. Link FROM evidence TO concepts -- never curate evidence lists inside concept notes. Let backlinks do the work.++Note types have graph roles:+- **Evidence nodes** (work notes, decisions): add outbound links to concepts they demonstrate+- **Concept nodes** (competencies, patterns): stay definitional -- evidence arrives via backlinks+- **Index nodes** (Index, Brag Doc, Memories): actively curate links -- they're navigational+Every new note must link to at least one existing note. Proactively suggest connections.- `[[Note Title]]` -- standard wikilink@@ -95,7 +104,10 @@ Every new note must link to at least one existing note. Proactively suggest conn#### When to Link- **Work note <-> Decision**: bidirectional links+- **Work note -> Competency**: in `## Related`, link to competencies demonstrated with a brief annotation (e.g., `[[Competency Name]] -- what was demonstrated`)- **Brag Doc -> Work note**: every entry links to evidence+- **Brag Doc -> Competency**: in `#### Competency Evidence` per quarter, link both competency and evidence work note+- **Review Template -> Competency + Work note**: per-competency assessment row with evidence links- **Memories -> Source**: every memory links to where it was learned- **Skills -> Usage**: skills link to notes where used- **Index -> Everything**: `work/Index.md` links to all work notes@@ -135,7 +147,7 @@ When significant work is completed, add to `perf/Brag Doc.md` with links to theUse tags in frontmatter (not inline):-- **Type**: `work-note`, `decision`, `claude`, `perf`, `thinking`, `north-star`+- **Type**: `work-note`, `decision`, `claude`, `perf`, `thinking`, `north-star`, `competency`- **Index**: `index`, `moc`- **Status** (frontmatter field): `active`, `completed`, `archived`, `proposed`, `accepted`, `deprecated`- **Project**: as needed, e.g. `project/my-project`diff --git a/README.md b/README.mdindex e4d3ccd..650873c 100644--- a/README.md+++ b/README.md@@ -17,11 +17,12 @@ A ready-to-use vault structure that makes Claude Code productive from session on## Vault Structure```-work/ Work notes, project tracking, decision records-perf/ Brag doc, performance review templates-claude/ Claude context: memories, skills, goals (North Star)-thinking/ Claude's scratchpad for drafts and reasoning-templates/ Obsidian templates with YAML frontmatter+work/ Work notes, project tracking, decision records+perf/ Brag doc, performance review templates+perf/competencies/ One note per competency (link targets for work notes)+claude/ Claude context: memories, skills, goals (North Star)+thinking/ Claude's scratchpad for drafts and reasoning+templates/ Obsidian templates with YAML frontmatter```### Key Files@@ -53,11 +54,12 @@ A hook in `.claude/settings.json` injects the vault file listing into every Clau### Templates-Three templates with YAML frontmatter including a `description` field for progressive disclosure:+Four templates with YAML frontmatter including a `description` field for progressive disclosure:- **Work Note** — date, description, project, status, tags- **Decision Record** — date, description, status (proposed/accepted/deprecated), tags- **Thinking Note** — date, description, context, tags+- **Competency Note** — date, description, current-level, target-level, proficiency table### Session Workflow@@ -77,6 +79,18 @@ The vault is built around **wikilinks**. Every note links to related notes, builClaude maintains the indexes (`work/Index.md`, `claude/Memories.md`, `perf/Brag Doc.md`) as notes are created, so the graph stays navigable.+## Performance Graph++The vault includes a performance tracking system built on the same graph principles:++- **Competency notes** in `perf/competencies/` represent skills from your organization's competency framework+- **Work notes** link to competencies in `## Related` — annotated with what was demonstrated+- **Brag Doc** aggregates evidence per quarter in `#### Competency Evidence` sections+- **Review Template** structures self-assessment around Impact, Competencies, and Principles+- **Backlinks accumulate automatically** — review prep becomes reading the backlinks panel on each competency note++To get started: create competency notes using the `Competency Note` template, then link your work notes to them as you complete projects.+## CustomizationThis is a starting point, not a straitjacket. Adapt it to how you work:diff --git a/perf/Brag Doc.md b/perf/Brag Doc.mdindex 0397285..ff3ab6e 100644--- a/perf/Brag Doc.md+++ b/perf/Brag Doc.md@@ -12,6 +12,9 @@ A running log of impact, wins, and growth. Link to work notes as evidence -- bac### Q1+#### Competency Evidence+-+#### Impact & Deliverables-diff --git a/perf/Review Template.md b/perf/Review Template.mdindex 0a08a60..9d232e8 100644--- a/perf/Review Template.md+++ b/perf/Review Template.md@@ -11,16 +11,33 @@ tags:## SummaryOne paragraph overview of the period.-## Key Accomplishments+## Impact -- "What was delivered?"++Key accomplishments linked to work notes.+1.2.3.-## Areas of Growth--+## Competencies -- "How knowledge and skills were applied"++Per-competency self-assessment. Link to competency notes and work note evidence.++| Competency | Rating | Evidence |+|------------|--------|----------|+| | | |++## Principles -- "How delivery happened"++How you embodied your organization's principles. Specific examples.-## Goals for Next Period--## Evidence & Links+## Growth Plan++Areas of growth and goals for next period. Link to competencies to develop.+-++## Related+- [[Brag Doc]]diff --git a/perf/competencies/README.md b/perf/competencies/README.mdnew file mode 100644index 0000000..920ab2c--- /dev/null+++ b/perf/competencies/README.md@@ -0,0 +1,22 @@+# Competencies++This folder holds one note per competency from your organization's competency framework.++## How it works++1. **Create** a competency note using the `Competency Note` template+2. **Link** work notes to competencies in their `## Related` section+3. **Evidence accumulates via backlinks** -- open any competency note and check the backlinks panel to see all work that demonstrates it+4. **Brag Doc** aggregates evidence per quarter in `#### Competency Evidence` sections+5. **Review Template** structures self-assessment around competencies++## Frontmatter fields++- `current-level` -- your assessed level for this competency+- `target-level` -- where you're aiming next++## Tips++- Don't maintain evidence lists manually in competency notes -- let backlinks do the work+- Use annotations when linking: `[[Competency Name]] -- what was demonstrated`+- Review competency backlinks when preparing for performance reviewsdiff --git a/templates/Competency Note.md b/templates/Competency Note.mdnew file mode 100644index 0000000..56f04fc--- /dev/null+++ b/templates/Competency Note.md@@ -0,0 +1,28 @@+---+date: "{{date}}"+description:+current-level:+target-level:+tags:+ - perf+ - competency+---++# {{title}}++## Definition++What this competency means for your role.++## Proficiency Levels++| Level | Description |+|-------|-------------|+| ... | ... |++## Growth Notes++What are you doing to grow this? What should you focus on?++## Related+-