flowing-abyss/obsidian-vault-skills/project

Projects

A project is a finite unit of work with a clear objective, a deliverable that defines "done", and an end. System notes (categories, meta-notes, problems, hierarchies) never end; a project always does.

For project tasks use the task-note skill.

Commands

Run from the vault root: V="python3 .claude/_engine/vault.py"

The engine reads the vault manifests, fills fixed values, defaults, created and updated, and takes the note body scaffold from the type's template. It refuses invalid input, writes nothing, and says what to fix. Correct the input. Never work around an error by writing frontmatter by hand.

• Repeat --set key=value to build a list. Link fields take plain note names.
• Pass only what you know. Skip a field instead of guessing a value.
• Edit the note body directly. A hook validates every edit; without hooks run check.

Choosing values

• No category fits: ask the user. If the user asked for the closest one, pick it and say which one you picked. Never invent a category.
• Set priority, start and end only when the user gave them.

Choosing a type

types project describes each. In short: single for compact work in one note, longform for a long work split into scenes, short for one short published piece.

A longform project is placed in its own folder projects/<Title>/<Title>.md. A scene is placed in that folder and added to the project's scene list. Both are done by the engine; do not move files or edit the longform block by hand.

Heading and scene statuses

Headings inside a project body and longform scenes carry a status emoji:

⬛ abandoned, 🟥 todo, 💡 idea, 🧠 brainstorming, 🔎 research, 🟦 in progress, 📋 revising, 🖍 editing, 🟩 completed, 📦 preparation, 📢 distributed.

# 🟦 Drafting
## 🔎 References
## 🟩 Final structure