← ClaudeAtlas

briefing-vaultlisted

Initialize, manage, and search the per-project .briefing/ vault. Obsidian-compatible persistent knowledge base.
sehoon787/my-codex · ★ 16 · AI & Automation · score 77
Install: claude install-skill sehoon787/my-codex
# Briefing Vault Skill Manage the `.briefing/` directory as a persistent, Obsidian-compatible knowledge base. ## Initialize Vault When starting a new vault (first time in a project): 1. Create directory structure: ``` .briefing/ ├── INDEX.md ├── sessions/ ├── decisions/ ├── learnings/ ├── references/ └── agents/ ``` 2. Create `.briefing/INDEX.md`: ```markdown --- 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 ``` 3. Add `.briefing/` to `.gitignore` ## Note Templates ### Session Note (`sessions/YYYY-MM-DD-topic.md`) ```markdown --- 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> ``` ### Decision Note (`decisions/name.md`) ```markdown --- 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 ##