update-second-brainlisted

Capture the current agent session's work into the Obsidian "second brain" vault and publish it: append to today's daily note, revise the project docs the session moved, propose and promote engineering practice notes, then commit and push. Runs from inside the working repo; the vault lives elsewhere. Use when the user says update second brain, update my second brain, capture this session, log this to second brain, second brain this, publish second brain, commit the vault, push practices, or backfill project docs.
dimeloper/second-brain-workflow · ★ 6 · AI & Automation · score 71

Install: claude install-skill dimeloper/second-brain-workflow

# Update second brain Turns "what I just did in this session" into vault updates, then publishes them. This is the **only** write path into the vault: capture → **publish the capture** → propose → promote → commit → push. The capture is today's daily note plus any project doc the session moved. The capture ships before the proposal on purpose — a daily note held back for approval is one another session can lose. You are usually invoked from a *different* repo (the one worked on); the vault is never the current working directory. `obsidian-knowledge-base` is the read side — consult it when you need vault practices *during* work. It does not write. ## Paths - Vault: `$SBW_VAULT` if set, else `~/vaults/second-brain` - Practices: `practices/{frontend,backend,app,cross-cutting}/` - Daily notes: vault root, `YYYY-MM-DD.md` (local date) - Projects: `projects/<project>/` — one **directory** per long-running initiative, revised in place: - `_project.md` — the stable overview: what it is, who, constraints, direction, open questions about the project itself - `features/<feature>.md` — one file per slice of work: current state, dated decisions, open questions, and an outcome when it closes - `context/<topic>.md` — product-scoped and optional: audience, voice, brand. Written by `extract-product-context`, re-checked by `check-context-freshness.py` (Step 4a-ii) - Templates: `_templates/{practice-note,daily-note,project,feature}.md` - Which project a repo belongs