Name: Obsidian
Author: madundead

When to use me

When working on Personal Obsidian vault notes.

Execution & Boundaries (CRITICAL)

Step-by-Step Approval: For any operation involving multiple files, folder restructuring, or system commands, you MUST:
1. Present a numbered list of EVERY planned action.
2. Wait for explicit approval for the next step(s).
3. Never perform "bonus" or "implied" tasks outside the approved scope.
Backups: Before performing structural changes, remind the user to backup or offer to run the NAS backup command.
Read-Only First: Always perform a read-only analysis (grep/glob) before proposing a plan.

Location: Assume the current working directory is the Personal Vault root.
PARA structure: Follow the 00_Inbox, 05_Journal, 10_Projects, , , , hierarchy. Note: Daily notes are stored directly in .

When working on Personal Obsidian vault notes.

Step-by-Step Approval: For any operation involving multiple files, folder restructuring, or system commands, you MUST:
1. Present a numbered list of EVERY planned action.
2. Wait for explicit approval for the next step(s).
3. Never perform "bonus" or "implied" tasks outside the approved scope.
Backups: Before performing structural changes, remind the user to backup or offer to run the NAS backup command.
Read-Only First: Always perform a read-only analysis (grep/glob) before proposing a plan.

Location: Assume the current working directory is the Personal Vault root.
PARA structure: Follow the 00_Inbox, 05_Journal, 10_Projects, , , , hierarchy. Note: Daily notes are stored directly in .