Vault Ops

Vault Operations Skill

Core operations for reading, writing, and managing files in a PM-Kit vault.

Vault Structure

Copy code
pm-kit/
├── CLAUDE.md           # Vault context (read first)
├── _core/              # config.yaml, MANIFESTO.md, PROCESSING.md
├── _templates/         # Note templates (ALWAYS USE)
├── 00-inbox/           # Unprocessed captures
├── 01-index/           # Project MOCs
├── daily/              # YYYY-MM-DD.md (multi-project)
├── docs/{project}/     # PRDs, specs
├── decisions/{project}/ # Decision records
├── blockers/{project}/  # Active blockers
├── meetings/           # Meeting notes
├── reports/            # Generated reports
│   └── previews/       # HTML previews (/preview, /report --preview)
└── _archive/           # Archived by YYYY-MM/

Naming Conventions (Naming-as-API)

Strict filename patterns enable glob queries without a database:

File Operations

Creating Notes

1. Check if note already exists (naming-as-API enables fast lookup)
2. Load appropriate template from _templates/
3. Replace template variables (Handlebars syntax)
4. Add YAML frontmatter with type, project, status, date, tags
5. Insert wiki-links to related notes
6. Write to correct folder per naming convention

Editing Notes

• Preserve YAML frontmatter structure
• Maintain existing wiki-links
• Use consistent heading hierarchy
• Apply standard tag format

Wiki-Link Format

markdownCopy code
[[Note Name]]                    # Simple link
[[Note Name|Display Text]]       # Link with alias
[[Note Name#Section]]            # Link to heading
[[folder/Note Name]]             # Link with path

Template Variables

When processing templates, replace Handlebars syntax:

• {{date}} → Today's date (YYYY-MM-DD)
• {{project}} → Project ID
• {{project_name}} → Project display name
• {{title}} → Note title
• {{slug}} → URL-safe slug

YAML Frontmatter

All notes require frontmatter:

yamlCopy code
---
type: [daily|doc|decision|blocker|meeting|inbox|index]
project: {project-id}
status: {per note_types in config.yaml}
date: YYYY-MM-DD
tags: []
---

Auto-Linking Rules

Archive Rules

Move to _archive/YYYY-MM/ when:

• Blocker status → resolved
• Doc status → shipped
• Decision status → superseded