Disclaimer
Is this project open source? Yes
Is this project completely free? Yes
Is this project vibe-coded beyond the author’s ability to comprehend how it works? No
Community Directory: N/A - this is a custom vault / workflow showcase, not a plugin or theme.
Hi everyone,
I open-sourced a small custom vault template inspired by Zettelkasten and designed to work as an Obsidian-compatible vault inside a software repository.
The goal is to help AI coding agents and human maintainers keep project context over time without rediscovering everything from scratch.
Instead of one large project document, the template uses small linked notes for:
- requirements
- technical designs
- review handoffs
- architecture notes
- validation runbooks
- gotchas / lessons learned
The basic workflow is:
```text
Task
→ REQ define scope, non-goals, and acceptance criteria
→ TECH confirm the implementation approach
→ Slice implement one bounded change
→ Validate record what was actually checked
→ REVIEW hand off evidence, feedback, and risk
→ Writeback update architecture, gotchas, or runbooks
```
It uses Obsidian-style wiki links like `[[00-governance/ai-workflow]]` for note-to-note navigation, while keeping standard Markdown links and images for GitHub compatibility.
This is not an Obsidian plugin. It is a reusable Markdown vault/workflow template that can be opened in Obsidian, edited in any Markdown editor, and kept in a normal Git repository.
There is also an optional companion skill for Claude/Codex-style agents, but the core project is just Markdown files and folders.
GitHub:
I would appreciate feedback from Obsidian users, especially on whether the folder structure and wiki-link approach feels natural for a project knowledge base.