spine-update

Spine Update — Resume and Enrich Existing Docs

Update existing Spine Architecture docs with new context from continued work sessions. Appends timestamped update sections — never overwrites or deletes existing content.

Vault Path Resolution

Resolve the vault path using this config chain:

1. $SPINE_VAULT_PATH environment variable
2. ~/.spine/config.json → read the vaultPath field
3. Default: ~/Documents/SpineVault/

If the vault doesn't exist, tell the user to run /spine-init first.

Detect Current Repo

basename "$(git remote get-url origin 2>/dev/null)" .git

Fall back to the current directory name if no git remote. If {vault}/{repo}/ doesn't exist, tell the user this repo isn't tracked by Spine yet — suggest /spine-init or /spine-capture to set it up.

Mode Selection

If $ARGUMENTS is provided (not empty and not whitespace-only): → Targeted Mode — proceed to "Targeted Mode" section below

If $ARGUMENTS is empty or not provided: → Auto-Detect Mode — proceed to "Auto-Detect Mode" section below

---

Targeted Mode (/spine-update <name>)

Step 1: Resolve Target

Match $ARGUMENTS against docs in {vault}/{repo}/ using this precedence (first match wins):

1. Exact filename match (case-insensitive, with or without .md extension)
2. Exact feature folder name match → resolves to the spine note in that folder (e.g., /spine-update auth matches {vault}/{repo}/auth/auth.md)
3. Substring match on doc title (from title frontmatter field)
4. Substring match on filename

Rules:

• Case-insensitive throughout
• If exactly one match at any precedence level → auto-select that doc
• If multiple matches at the same precedence level → show a numbered pick list and let the user choose
• If no match at any level → tell user "No matching doc found for '{name}'. Did you mean to create a new doc? Try /spine-capture."

Step 2: Read Existing Doc

Load the full content of the resolved doc. Extract: