npx claudepluginhub sehoon787/my-claude --plugin my-claudeThis skill uses the workspace's default tool permissions.
Manage the `.briefing/` directory as a persistent, Obsidian-compatible knowledge base.
Provides persistent Obsidian vault memory for coding agents. Auto-orients sessions with TODOs and project overviews, supports lookup of notes/patterns, and writes discoveries using commands like init, lookup, note.
Manages Obsidian vault as developer knowledge base: create/search/update notes with standard frontmatter, organize by projects/technologies/Claude Code, auto-capture commits/tasks/components.
Integrates Claude with Obsidian vaults for note creation, task management, knowledge organization, and project docs using CLI (1.12+), MOCs, properties.
Share bugs, ideas, or general feedback.
Manage the .briefing/ directory as a persistent, Obsidian-compatible knowledge base.
When starting a new vault (first time in a project):
.briefing/
├── INDEX.md
├── sessions/
├── decisions/
├── learnings/
├── references/
└── agents/
.briefing/INDEX.md:---
date: <today>
type: index
tags: [project, index]
---
# <Project Name> Knowledge Base
## Overview
<Brief project description>
## Recent Decisions
<!-- Auto-updated by agents -->
## Open Questions
<!-- Track unresolved items -->
## Key Links
- [[sessions/]] — Session logs
- [[decisions/]] — Architecture decisions
- [[learnings/]] — Patterns and solutions
.briefing/ to .gitignoresessions/YYYY-MM-DD-topic.md)---
date: YYYY-MM-DD
type: session
tags: [session]
related: []
---
# Session: <Topic>
## Goal
<What was requested>
## Actions
- <What was done>
## Results
- <Outcomes>
## Decisions Made
- [[decisions/decision-name]] — <brief>
## Learnings
- [[learnings/learning-name]] — <brief>
## Next Steps
- <Follow-up items>
decisions/name.md)---
date: YYYY-MM-DD
type: decision
tags: [architecture|design|tooling]
status: accepted|superseded|deprecated
related: []
---
# Decision: <Title>
## Context
<Why this decision was needed>
## Options Considered
1. <Option A> — pros/cons
2. <Option B> — pros/cons
## Decision
<What was chosen and why>
## Consequences
<Impact of this decision>
learnings/name.md)---
date: YYYY-MM-DD
type: learning
tags: [pattern|gotcha|solution]
related: []
---
# <Title>
## Problem
<What went wrong or was non-obvious>
## Solution
<What fixed it>
## Why It Works
<Root cause explanation>
references/name.md)---
date: YYYY-MM-DD
type: reference
source: <URL or source description>
tags: [reference, topic]
related: []
---
# <Title>
## Source
<URL or citation>
## Key Points
- <Main finding 1>
- <Main finding 2>
## Context
<Why this reference is relevant>
## Raw Notes
<Verbatim excerpts or detailed notes>
Use Grep to search .briefing/ by keyword:
# Search by content
grep -r "keyword" .briefing/ --include="*.md"
# Search by tag
grep -r "tags:.*architecture" .briefing/ --include="*.md"
# Search by type
grep -r "type: decision" .briefing/ --include="*.md"
.briefing/ as an Obsidian vault[[wiki-links]]