Practical overview
When it fits
Use it when you want Claude Code to work within an Obsidian planning system that connects daily activity to projects and longer-term goals, with recurring reviews to check progress.
Who it is for
- Obsidian users who want daily planning linked to long-term goals and active projects.
- People who use Claude Code and want structured daily, weekly, and monthly review workflows.
- Existing-vault users seeking a documented way to map their folder structure into the kit.
Documented uses
- Surface a priority and active-project next-actions when creating a daily note.
- Review daily notes and project status, then plan the next week.
- Check monthly progress against quarterly milestones and yearly goals.
- Create projects linked to goals and inspect project status.
- Use specialized agents for goal alignment, weekly reflection, note organization, and inbox processing.
Requirements & limits
The repository is public, identifies the project as MIT-licensed, and documents setup for Unix-like shell use and Windows batch setup. The primary workflow requires Obsidian, the Claude Code CLI, and Git.
- The kit is an Obsidian and Claude Code starter system, not a standalone hosted planning service.
- The README describes bash and Markdown implementation with zero dependencies, and lists Shell as the primary language.
- The documented daily, weekly, and monthly commands organize planning around a linked goal hierarchy.
- Existing vaults have a separate
/adoptpath; the README says adoption preserves the vault structure. - The repository lists an MIT license.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Set up the starter vault
Clone and configure the kit, then open it in Obsidian and start Claude Code.
Before you start
- Obsidian installed
- Claude Code CLI installed
- Git installed
Steps
Clone the repository and change into its directory.
Run
chmod +x scripts/setup.sh && ./scripts/setup.sh.Open the vault in Obsidian, change to the vault location in a terminal, and run
claude.Run
/onboardto personalize the vault with your name, preferred review day, and goal areas.
Expected outcome
A configured vault with onboarding completed, ready for the documented planning workflow.
Guide limitations
- The instructions require the listed software; they do not document a verification procedure for a particular system.
Add the workflow to an existing vault
Use the adoption skill to map an existing Obsidian vault and generate configuration for its folder structure.
Before you start
- An existing Obsidian vault
- Obsidian installed
- Claude Code CLI installed
Steps
Open a terminal at the root of the existing vault.
Start Claude Code by running
claude.Enter
/adoptand follow its interactive folder-mapping process.
Expected outcome
The kit generates configuration scoped to the vault’s directory names; the README says the existing vault structure stays untouched.
Guide limitations
- The documented adoption process does not describe subsequent workflow execution in detail.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 10 October 2026
- Original website title
- ballred/obsidian-claude-pkm · Official homepage title · retained in its source language