op

name	op
description	Run the Obsidian Projects workflow — scaffold new projects, create/work/resolve issues, and maintain schema-conformant notes in an Obsidian vault that follows the Projects schema. Use whenever the user invokes /op:* commands or references an Obsidian project by ID prefix (e.g. JB-3, TMB-9, OP-11).

Obsidian Projects (op) — zero-order guidance

This is a stub. The canonical operating manual lives inside the op-obsidian plugin and ships with every plugin release; pull it with obsidian op-get-skill once per session and follow the body it returns. That keeps the skill stable while the workflow logic evolves with the plugin.

Zero-order rules — apply before fetching anything

1. Probe the plugin once per session and cache the result. Every op-* action goes through it; without the plugin you cannot operate. Run obsidian vault first to learn the registered vault name, then probe through that vault explicitly:

   obsidian vault                                                  # list registered vaults; cache the one you'll target
   obsidian vault=<name> eval code='({enabled: app.plugins.enabledPlugins.has("op-obsidian"), version: app.plugins.plugins["op-obsidian"]?.manifest?.version, vault: app.vault.getName()})'
   

   If enabled is false or the eval throws, stop and ask the user to install/enable op-obsidian before going further. Do not improvise with raw obsidian CLI primitives — the plugin owns filename sanitization, ID numbering, frontmatter shape, atomic move-and-trash on resolve, and the JSON response payload at Projects/_scratch/op-last-response.md.