save-to-obsidian

Save the best available content from the current session into an Obsidian vault as a design note.

Parse $1 as an optional vault override and $2 as an optional topic override (both optional — see resolution rules below). $1/$2 are name/topic strings, not file paths — this command never takes an explicit source file; content is always auto-discovered from the session.

Vaults on iCloud storage cannot be written with the Write tool — ~/Library/Mobile Documents/iCloud~md~obsidian/Documents/<vault> is TCC-protected; only the Obsidian app (via the obsidian CLI) can touch it, even with the sandbox disabled. Step 5 below always writes through the CLI — never write directly to a resolved vault path with the Write tool, even for a small note. (Write is only used in this command to stage the note in a scratch temp file before handing it to the CLI script.)

Step 1: Discover content

Run the discovery script, resolved relative to the plugin root:

DISCOVERY=$(bash "${CLAUDE_PLUGIN_ROOT}/scripts/discover-spec-content.sh" 2>&1)

If it exits non-zero, check stderr for {"error": "..."} and report the error (jq not installed, not in a git repository).

Parse the JSON output:

SOURCE=$(echo "$DISCOVERY" | jq -r '.source')
PRIMARY=$(echo "$DISCOVERY" | jq -r '.primary')
SECONDARY=$(echo "$DISCOVERY" | jq -r '.secondary')
SPECS=$(echo "$DISCOVERY" | jq -r '.candidates.specs[]' 2>/dev/null)
PLANS=$(echo "$DISCOVERY" | jq -r '.candidates.plans[]' 2>/dev/null)

superpowers

If PRIMARY is non-empty, read it as $BODY.

If PRIMARY is empty, multiple candidates need disambiguation — use AskUserQuestion with the SPECS/PLANS candidates to pick the file. Read the chosen file as $BODY.

If SECONDARY is non-empty (a related plan), you may append a short "Implementation plan: <path>" reference line to the note rather than inlining the whole plan.

claude-plan

PRIMARY already points to the plan file. Read it as $BODY.