Agent skill · writing content · jeremylongshore
obsidian-project-documentation
Document technical projects in Obsidian vault. Use when the User mentions "document this", "close out", "wrap up", "update notes", "track progress", "where are we at", or asks about project docs.
Why this skill is useful
Adds specific commands and structured workflows for documenting projects in Obsidian that the AI wouldn't reliably generate on its own.
What it needs
About 5k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Obsidian Project Documentation Assistant This skill helps maintain project documentation in an Obsidian vault while working with Claude Code. It automatically captures project progress and insights into structured, consistent notes. Architecture: This skill acts as a lightweight launcher that detects project context, asks clarifying questions if needed, then launches an agent to handle the documentation work in the background. How This Works Three situations trigger this skill, falling into two execution paths: Situation Trigger Path --------- ------- ---- 1 — New session start User opens a project and says hello, or Claude Code starts Path A — read-only context load 2 — Mid-session documentation "document this", "update notes", "track progress", etc. Path B — full documentation run 3 — Session end "wrap up", "close out", "we're done for today", etc. Path B — full documentation run Path A is read-only. It must never launch the documentation agent or write to the vault. Path B launches the agent. It performs context detection and spawns the manager agent to write vault notes. Shared Step: Load Configuration Before following either path, load the config: Step 1: Load Configuration Expected format: If config doesn't exist (first-run setup): Use AskUserQuestion to ask the User for their Obsidian vault path: Then write the config to ~/.claude/obsidian-project-assistant-config.json: Confirm the config was written, then follow the appropriate path below. Path A: Session Start (Situation 1) Read-only. Do not launch the agent. Do not write to the vault. Step A1: Detect Project Name Use the same detection logic as Step B2 (git repo name → directory name) to determine which vault note to load. Step A2: Read Project Context Also read CLAUDE.md from the current working directory if it exists. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/obsidian-project-documentation