---
description: Consolidate, promote, or restructure vault notes — plan mode only, requires human approval
---

**Plan mode only.** This skill proposes changes for human review before executing. Never reorganize vault structure without an approved plan.

## When to trigger

- **Duplicate coverage:** two or more notes cover the same concept with overlapping content
- **Promotion candidate:** a `scope/project` fact has recurred across 2+ clients — promote to `scope/global`
- **Oversized note:** a note has grown beyond ~200 lines or has drifted from a single concept

## Procedure

1. **Identify candidates** — list notes that meet one or more triggers above
2. **Propose a plan** — for each candidate, propose one of:
   - **Merge:** combine into a single note (specify target)
   - **Split:** extract distinct concepts into separate notes
   - **Promote:** change `scope/project` → `scope/global`, broaden client tag
   - **Rename:** update title/filename for clarity
3. **Await human approval** — do not execute until the plan is confirmed
4. **Execute edits** — make the approved changes
5. **Force rebuild:** after any reorganization that removes, renames, or restructures notes, run:
   ```bash
   # vault_path and ollama_model from ~/.claude/plugins/os-vault/config.yaml
   graphify extract <vault-path> --backend ollama --model <configured-model> --force
   ```

## Why --force after reorganization?

`graphify update --file` does **not** prune deleted or renamed nodes — ghost nodes accumulate. Only `--force` clears the graph completely and rebuilds clean. Always use `--force` after restructuring, not `--update`.
