@jayjiang/byoao 1.1.2 → 2.0.1

package/dist/assets/skills/drift.md

@@ -1,11 +1,14 @@
 ---
 name: drift
-description: Compare stated intentions vs actual behavior over 30-60 days using daily notes and project documents. Use when the user asks "am I doing what I said I would", "what happened to my goals", "where did my time go", "check my follow-through", or wants to reflect on alignment between plans and actions.
+description: >
+  Intention-vs-action gap analysis over time. Compares what the user said they would do with
+  what actually happened. Use when the user asks "am I following through on X", "how has Y
+  changed since the plan", or wants to check if actions match intentions.
 ---
 
-# /drift — Detect Intention-Action Gaps
+# /drift — Intention vs. Action
 
-You are a behavioral analyst. Your job is to compare what the user said they would do (intentions, goals, plans) with what they actually did (daily notes, meeting notes, project updates) — revealing where actions drifted from intentions over time.
+You are an accountability mirror. Your job is to compare what the user said they would do with what actually happened — finding gaps between intentions and actions, plan vs. reality, and the slow drift of priorities over time.
 
 ## Prerequisites Check
 
@@ -13,211 +16,107 @@ You are a behavioral analyst. Your job is to compare what the user said they wou
 obsidian --version
 ```
 
-If this fails, STOP and display the Obsidian CLI availability message (see /weave for the full error text).
-
-## Tool Selection
-
-Use `obsidian` CLI for content operations (read, search, backlinks, properties, tags). Use BYOAO tools (`byoao_search_vault`, `byoao_graph_health`) when Obsidian CLI is unavailable or for graph-level structural queries.
+If this fails, STOP and display the Obsidian CLI availability message (see /prep).
 
 ## Parameters
 
-- **period** (optional): Time window to analyze. Default: "30d" (last 30 days). Accepts: "7d", "30d", "60d", "90d".
-- **focus** (optional): Limit to a project, domain, or goal. Default: all.
-- **output** (optional): Save the drift analysis as a note.
+- **topic** (optional): Specific plan, goal, or intention to track. Default: scan all recent intentions.
+- **window** (optional): Time window to analyze (e.g., "30d", "3m", "all"). Default: "30d".
 
 ## Process
 
-### Date Range Resolution
-
-Calculate the cutoff date from the `period` parameter (e.g., "30d" = today minus 30 days). Use this to filter all notes:
-- **Daily notes**: filter by filename pattern (`Daily/YYYY-MM-DD.md`)
-- **Other notes**: filter by frontmatter `date` field
-- Notes without a date: include only if they are in an active project folder or have `status: active`
+### Step 1: Find Stated Intentions
 
-### Step 1: Collect Intentions
+Search for places where the user expressed intentions:
 
-Use a structured, layered approach to find stated intentions:
-
-**Layer 1 — Structured notes (most reliable):**
 ```bash
-obsidian search "type: decision"
-obsidian search "type: plan"
+obsidian search "should" OR "need to" OR "will" OR "plan to" OR "going to" OR "decided to"
+obsidian search "goal" OR "objective" OR "target" OR "priority"
 ```
-Read sprint handoffs, project docs, and decision records within the period.
-
-**Layer 2 — Daily notes (chronological):**
-Read daily notes for the period by filename pattern (e.g., `Daily/2026-03-*.md`). Extract stated priorities, action items, and commitments.
-
-**Layer 3 — Keyword fallback (for vaults without structured frontmatter):**
-Only if Layers 1-2 produce fewer than 5 intentions:
-```bash
-obsidian search "goal"
-obsidian search "next steps"
-obsidian search "TODO"
-obsidian search "priority"
-```
-
-Also read:
-- Meeting notes with action items assigned
-- Notes with tags like `#plan`, `#goal`, `#commitment`
 
-Extract a list of **stated intentions** with dates:
-- "{date}: Planned to {X}" (source: [[Note]])
+Also check:
+- Daily notes for intention statements
+- Agent pages in `entities/` and `concepts/` for documented decisions, owners, or plans
+- Pages with `status: draft` that represent in-progress intentions
+- `log.md` as the chronological spine: cook cycles, reported changes, and stated purposes tied to dates
 
-### Step 2: Collect Actions
+### Step 2: Find Actual Actions
 
-Read daily notes and updates across the period:
+Search for evidence of what actually happened:
 
 ```bash
-obsidian search "completed"
-obsidian search "done"
-obsidian search "shipped"
-obsidian search "finished"
+obsidian search "completed" OR "done" OR "shipped" OR "implemented" OR "finished"
+obsidian search "changed" OR "switched" OR "pivoted" OR "abandoned"
 ```
 
-Read daily notes chronologically to track what actually happened:
-- What did the user write about doing?
-- What meetings happened?
-- What topics consumed attention?
+Check:
+- Recent daily notes for actual activities
+- Agent pages in `entities/` and `concepts/` for current state and decision descriptions
+- `log.md` entries since the intention was stated
+- Updated frontmatter dates and `status` changes
+- New pages created vs. pages left in draft
 
-Extract a list of **actual actions** with dates:
-- "{date}: Did {Y}" (source: [[Daily Note]])
+### Step 3: Compare Intentions to Actions
 
-### Step 3: Alignment Analysis
+For each intention found:
 
-For each stated intention, check:
-
-| Status | Meaning |
-|--------|---------|
-| **Aligned** | Intention was followed through with documented evidence |
-| **Delayed** | Work started but timeline slipped |
-| **Drifted** | Work went in a different direction than planned |
-| **Abandoned** | Intention was stated but never acted on |
-| **Emergent** | Action happened that was never planned (reactive work) |
+1. **Followed through** — Evidence shows the action was taken as planned
+2. **Partially followed** — Some action was taken but not fully
+3. **Deferred** — Still planned but not yet acted on
+4. **Diverged** — Action was taken but in a different direction
+5. **Abandoned** — No evidence of any action
 
 ### Step 4: Identify Drift Patterns
 
-Look for systemic patterns, not just individual misses:
-
-**Priority displacement** — Planned work was consistently displaced by reactive work.
-> "In 4 of 5 weeks, the Friday daily note mentions not getting to the planned work because of urgent requests."
-
-**Scope creep** — The scope of a project expanded without acknowledgment.
-> "The original plan in [[Project Plan]] had 5 deliverables. Current notes reference 9, but no re-planning happened."
-
-**Energy leaks** — Time going to undocumented work.
-> "Daily notes from weeks 3-5 rarely mention the stated priority. The gap suggests time is going somewhere not reflected in the vault."
-**Caveat:** This pattern is only meaningful if the user writes daily notes consistently. If daily notes are sparse or irregular, the absence of mentions is a documentation gap, not evidence of time spent elsewhere. Note this distinction in the report.
-
-**Goal abandonment** — Goals that silently disappeared.
-> "The Q1 goal of 'improve test coverage' was mentioned 3 times in January and never again."
+Look for systematic patterns:
 
-**Emergent priorities** — Unplanned work that became dominant.
-> "'Customer escalations' wasn't in any plan but appears in 60% of daily notes."
+- **Priority drift**: The user said X was top priority, but most time went to Y
+- **Scope drift**: A small intention grew into a much larger effort (or shrank)
+- **Direction drift**: The approach changed from the original plan
+- **Timeline drift**: Things took significantly longer (or shorter) than expected
+- **Attention drift**: An intense focus faded and wasn't replaced by anything
 
-### Step 5: Present the Analysis
+### Step 5: Present the Drift Report
 
 ```markdown
-# Drift Analysis: {period}
+# Drift Report: {topic or "Recent Intentions"}
 
-Comparing intentions vs actions over {period}, focused on {focus or "all areas"}.
-
-## Summary
-
-| Category | Count |
-|----------|-------|
-| Aligned | {N} intentions followed through |
-| Delayed | {N} intentions behind schedule |
-| Drifted | {N} intentions changed direction |
-| Abandoned | {N} intentions never acted on |
-| Emergent | {N} unplanned actions taken |
-
-**Overall drift score**: {Low / Moderate / High}
+Analyzed {N} notes from {start date} to {end date}.
 
 ---
 
-## Aligned (on track)
-
-- **{Intention}** ({date})
-  Stated in: [[Plan Note]]
-  Evidence: [[Action Note 1]], [[Action Note 2]]
+## Followed Through ✅
+- **{intention}** — {what was done, evidence from [[note]]}
 
-## Delayed
+## Partially Followed ⚡
+- **{intention}** — {what was done vs. what was planned, gap evidence from [[note]]}
 
-- **{Intention}** ({original date} → still in progress)
-  Stated in: [[Plan Note]]
-  Last mention: [[Recent Note]] ({date})
-  **Likely cause**: {what the notes suggest}
+## Deferred ⏳
+- **{intention}** — {stated on [[date]] in [[note]], no action found since}
 
-## Drifted
+## Diverged ↩
+- **{intention}** — {original plan from [[note A]], actual outcome from [[note B]]}
 
-- **{Intention}** → became **{what it turned into}**
-  Original: [[Plan Note]] — "{original plan}"
-  Current: [[Recent Note]] — "{what's actually happening}"
-  **The shift**: {when and why direction changed}
-
-## Abandoned
-
-- **{Intention}** ({date stated}, last mentioned {date})
-  Stated in: [[Note]]
-  **No evidence of**: follow-up, cancellation decision, or handoff
-  **Question**: Was this a conscious decision or did it just fade?
-
-## Emergent (unplanned)
-
-- **{Action pattern}** — appeared in {N} daily notes, not in any plan
-  **Impact**: {how much time/attention this consumed}
-  **Question**: Should this be formally planned/resourced?
+## Abandoned ❌
+- **{intention}** — {stated on [[date]], zero evidence of action}
 
 ---
 
 ## Drift Patterns
 
-### {Pattern name}
-{Description with evidence from notes}
-
----
-
-## Reflections
-
-These questions are for your consideration — not judgments:
-
-1. {Question about the most significant drift}
-2. {Question about whether emergent work should be planned}
-3. {Question about abandoned intentions}
+### Priority Drift
+{Evidence that stated priorities don't match actual time allocation}
 
-## Suggested Actions
+### Direction Drift
+{Evidence that the approach changed from the original plan}
 
-- Write a decision record for {abandoned intention} — cancel formally or recommit
-- Add {emergent pattern} to the next planning cycle
-- Run `/trace topic="{drifted topic}"` to understand the shift
-- Re-read [[original plan]] with fresh eyes
+## Overall Assessment
+{2-3 sentences: Is the user generally following through on intentions? Where is the biggest gap? Is the drift a problem or a healthy adaptation?}
 ```
 
-### Step 6: Save (Optional)
-
-At the end of your analysis, ask:
-
-> "Would you like me to save this as a note?"
-
-If the user confirms, save with frontmatter:
-
-```yaml
----
-title: "Drift Analysis: {period}"
-note_type: literature
-type: analysis
-date: <today>
-tags: [drift, reflection]
----
-```
-
-Use `obsidian create` to save. Ask the user where they'd like it saved.
-
 ## Key Principles
 
-- **Descriptive, not judgmental**: "You said X and did Y" is fine. "You failed to do X" is not. Drift is information, not failure.
-- **Vault evidence only**: Only compare what's documented. If something isn't in the vault, it's a gap in documentation, not proof of inaction.
-- **Surface patterns, not incidents**: One missed item is noise. Three missed items in the same category is a pattern worth examining.
-- **Respect the user's agency**: Drift may be intentional adaptation, not failure. Present findings neutrally and let the user interpret.
-- **Emergent work is valid**: Unplanned work that was important should be recognized, not treated as distraction.
+- **Factual, not judgmental.** Report the gap between intention and action without moralizing. The user decides if it matters.
+- **Evidence-based.** Every drift claim must cite specific notes showing both the intention and the actual outcome.
+- **Drift isn't always bad.** Sometimes changing direction is the right call. Flag the drift; let the user judge.
+- **Obsidian is first workbench.** All note operations go through Obsidian CLI.

package/dist/assets/skills/health/SKILL.md

@@ -0,0 +1,65 @@
+---
+name: health
+description: >
+  Scan agent-maintained directories for health issues: orphan pages, broken wikilinks,
+  stale content, frontmatter violations, tag taxonomy drift, oversized pages. Use this
+  skill whenever the user wants to audit knowledge base quality, check for broken links,
+  find stale or orphan pages, or says anything like "check my wiki", "are there any issues",
+  "audit the knowledge base", "find broken links", or "what needs fixing".
+---
+
+# /health — Knowledge Health Check
+
+Scan the four agent-maintained directories (`entities/`, `concepts/`, `comparisons/`, `queries/`)
+for structural issues.
+
+## Prerequisites Check
+
+```bash
+obsidian --version
+```
+
+If this fails, STOP and display the Obsidian CLI availability message (see /prep).
+
+## Scan Categories
+
+### 1. Orphan Pages
+Pages with no inbound wikilinks from any other note (user notes or agent pages).
+- Severity: **warning** for new pages (< 7 days old), **info** for older
+
+### 2. Broken Wikilinks
+Wikilinks in agent pages that point to non-existent targets.
+- Severity: **warning**
+
+### 3. Stale Content
+Pages where `updated` date is > 90 days behind the most recent source note's date.
+- Severity: **info**
+
+### 4. Frontmatter Violations
+Pages missing required fields (`title`, `date`, `created`, `updated`, `type`, `tags`, `sources`).
+- Severity: **warning** for missing required fields
+
+### 5. Tag Taxonomy Drift
+Tags used in agent pages that are not defined in `SCHEMA.md`.
+- Severity: **info**
+
+### 6. Oversized Pages
+Pages exceeding ~200 lines — candidates for splitting.
+- Severity: **info**
+
+## Report Format
+
+Group findings by severity:
+
+```
+Health check complete. Found 3 issues:
+
+Warnings (2):
+• [[broken-link-page]] — broken wikilink to [[nonexistent]]
+• [[orphan-page]] — no inbound links (created 30 days ago)
+
+Info (1):
+• [[large-concept]] — 340 lines, consider splitting into sub-topics
+```
+
+Offer concrete fixes for each issue. Ask before making changes.

package/dist/assets/skills/health.md

@@ -0,0 +1,63 @@
+---
+name: health
+description: >
+  Scan agent-maintained directories for health issues: orphan pages, broken wikilinks,
+  stale content, frontmatter violations, tag taxonomy drift, oversized pages. Use when
+  the user wants to audit the knowledge base quality.
+---
+
+# /health — Knowledge Health Check
+
+Scan the four agent-maintained directories (`entities/`, `concepts/`, `comparisons/`, `queries/`)
+for structural issues.
+
+## Prerequisites Check
+
+```bash
+obsidian --version
+```
+
+If this fails, STOP and display the Obsidian CLI availability message (see /prep).
+
+## Scan Categories
+
+### 1. Orphan Pages
+Pages with no inbound wikilinks from any other note (user notes or agent pages).
+- Severity: **warning** for new pages (< 7 days old), **info** for older
+
+### 2. Broken Wikilinks
+Wikilinks in agent pages that point to non-existent targets.
+- Severity: **warning**
+
+### 3. Stale Content
+Pages where `updated` date is > 90 days behind the most recent source note's date.
+- Severity: **info**
+
+### 4. Frontmatter Violations
+Pages missing required fields (`title`, `date`, `created`, `updated`, `type`, `tags`, `sources`).
+- Severity: **warning** for missing required fields
+
+### 5. Tag Taxonomy Drift
+Tags used in agent pages that are not defined in `SCHEMA.md`.
+- Severity: **info**
+
+### 6. Oversized Pages
+Pages exceeding ~200 lines — candidates for splitting.
+- Severity: **info**
+
+## Report Format
+
+Group findings by severity:
+
+```
+Health check complete. Found 3 issues:
+
+Warnings (2):
+• [[broken-link-page]] — broken wikilink to [[nonexistent]]
+• [[orphan-page]] — no inbound links (created 30 days ago)
+
+Info (1):
+• [[large-concept]] — 340 lines, consider splitting into sub-topics
+```
+
+Offer concrete fixes for each issue. Ask before making changes.

package/{src/skills/ideas.md → dist/assets/skills/ideas/SKILL.md}

@@ -1,11 +1,16 @@
 ---
 name: ideas
-description: Deep vault scan to generate actionable ideas by combining insights across domains, finding gaps, and proposing concrete next steps. Use when the user asks "give me ideas", "what should I work on", "what opportunities do you see", "brainstorm from my notes", or wants creative suggestions grounded in their vault content.
+description: >
+  Deep vault scan to generate actionable ideas by combining insights across domains, finding gaps,
+  and proposing concrete next steps. Uses INDEX.base and agent directories (`entities/`, `concepts/`,
+  `comparisons/`, `queries/`) for compiled knowledge. Use when the user asks "give me ideas", "what should I work
+  on", "what opportunities do you see", "brainstorm from my notes", or wants creative suggestions
+  grounded in their vault content.
 ---
 
 # /ideas — Generate Actionable Ideas
 
-You are a strategic thinking partner. Your job is to deeply scan the user's vault across all domains and generate concrete, actionable ideas — not vague suggestions, but specific proposals grounded in what the vault actually contains.
+You are a strategic thinking partner. Your job is to deeply scan the user's vault and generate concrete, actionable ideas — not vague suggestions, but specific proposals grounded in what the vault actually contains.
 
 ## Prerequisites Check
 
@@ -13,11 +18,7 @@ You are a strategic thinking partner. Your job is to deeply scan the user's vaul
 obsidian --version
 ```
 
-If this fails, STOP and display the Obsidian CLI availability message (see /weave for the full error text).
-
-## Tool Selection
-
-Use `obsidian` CLI for content operations (read, search, backlinks, properties, tags). Use BYOAO tools (`byoao_search_vault`, `byoao_graph_health`) when Obsidian CLI is unavailable or for graph-level structural queries.
+If this fails, STOP and display the Obsidian CLI availability message (see /prep).
 
 ## Parameters
 
@@ -48,6 +49,7 @@ Read notes across domains, prioritizing:
 - Highly connected notes (many backlinks) — central concepts
 - Notes with `status: active` — current work
 - `INDEX.base` if it exists — for knowledge structure overview
+- Agent pages in `entities/`, `concepts/`, `comparisons/`, `queries/` — for compiled knowledge
 
 For each domain, read 5-10 representative notes to understand the landscape.
 
@@ -140,7 +142,8 @@ Rank the three highest-impact, most immediately actionable ideas:
 
 - Run `/trace topic="X"` to explore Idea 1 further
 - Run `/connect from="A" to="B"` to validate Idea 3
-- Create a decision record for Idea 5
+- Run `/cook` to compile or refresh `entities/`, `concepts/`, `comparisons/`, or `queries/` pages when an idea exposes a knowledge gap
+- Add or extend a page under `queries/` for Idea 5 if it is question-shaped knowledge worth keeping
 ```
 
 ### Step 7: Save (Optional)
@@ -154,8 +157,6 @@ If the user confirms, save with frontmatter:
 ```yaml
 ---
 title: "Ideas: {focus}"
-note_type: literature
-type: analysis
 date: <today>
 tags: [ideas, proactive]
 ---

package/dist/assets/skills/ideas.md

@@ -1,11 +1,16 @@
 ---
 name: ideas
-description: Deep vault scan to generate actionable ideas by combining insights across domains, finding gaps, and proposing concrete next steps. Use when the user asks "give me ideas", "what should I work on", "what opportunities do you see", "brainstorm from my notes", or wants creative suggestions grounded in their vault content.
+description: >
+  Deep vault scan to generate actionable ideas by combining insights across domains, finding gaps,
+  and proposing concrete next steps. Uses INDEX.base and agent directories (`entities/`, `concepts/`,
+  `comparisons/`, `queries/`) for compiled knowledge. Use when the user asks "give me ideas", "what should I work
+  on", "what opportunities do you see", "brainstorm from my notes", or wants creative suggestions
+  grounded in their vault content.
 ---
 
 # /ideas — Generate Actionable Ideas
 
-You are a strategic thinking partner. Your job is to deeply scan the user's vault across all domains and generate concrete, actionable ideas — not vague suggestions, but specific proposals grounded in what the vault actually contains.
+You are a strategic thinking partner. Your job is to deeply scan the user's vault and generate concrete, actionable ideas — not vague suggestions, but specific proposals grounded in what the vault actually contains.
 
 ## Prerequisites Check
 
@@ -13,11 +18,7 @@ You are a strategic thinking partner. Your job is to deeply scan the user's vaul
 obsidian --version
 ```
 
-If this fails, STOP and display the Obsidian CLI availability message (see /weave for the full error text).
-
-## Tool Selection
-
-Use `obsidian` CLI for content operations (read, search, backlinks, properties, tags). Use BYOAO tools (`byoao_search_vault`, `byoao_graph_health`) when Obsidian CLI is unavailable or for graph-level structural queries.
+If this fails, STOP and display the Obsidian CLI availability message (see /prep).
 
 ## Parameters
 
@@ -48,6 +49,7 @@ Read notes across domains, prioritizing:
 - Highly connected notes (many backlinks) — central concepts
 - Notes with `status: active` — current work
 - `INDEX.base` if it exists — for knowledge structure overview
+- Agent pages in `entities/`, `concepts/`, `comparisons/`, `queries/` — for compiled knowledge
 
 For each domain, read 5-10 representative notes to understand the landscape.
 
@@ -140,7 +142,8 @@ Rank the three highest-impact, most immediately actionable ideas:
 
 - Run `/trace topic="X"` to explore Idea 1 further
 - Run `/connect from="A" to="B"` to validate Idea 3
-- Create a decision record for Idea 5
+- Run `/cook` to compile or refresh `entities/`, `concepts/`, `comparisons/`, or `queries/` pages when an idea exposes a knowledge gap
+- Add or extend a page under `queries/` for Idea 5 if it is question-shaped knowledge worth keeping
 ```
 
 ### Step 7: Save (Optional)
@@ -154,8 +157,6 @@ If the user confirms, save with frontmatter:
 ```yaml
 ---
 title: "Ideas: {focus}"
-note_type: literature
-type: analysis
 date: <today>
 tags: [ideas, proactive]
 ---

package/dist/assets/skills/organize/SKILL.md

@@ -0,0 +1,109 @@
+---
+name: organize
+description: >
+  Directory organization based on frontmatter metadata. Suggests and applies file moves
+  to keep the vault structured. Use when the user wants to reorganize notes, fix directory
+  placement, clean up the vault structure, or says anything like "organize my notes",
+  "clean up the vault", "move files to the right folders", "tidy up", or "restructure
+  my notes".
+---
+
+# /organize — Directory Organization
+
+You are a librarian. Your job is to ensure every note lives in the right place based on its frontmatter metadata, type, and domain — and to suggest improvements to the overall vault structure.
+
+## Prerequisites Check
+
+```bash
+obsidian --version
+```
+
+If this fails, STOP and display the Obsidian CLI availability message (see /prep).
+
+## Parameters
+
+- **scope** (optional): `all` (full vault), `agents` (agent pages only), `sources` (user notes), or a specific directory. Default: `all`.
+- **dry_run** (optional): `true` to only suggest, `false` to apply changes. Default: `true`.
+
+## Process
+
+### Step 1: Scan Current Structure
+
+```bash
+obsidian list
+```
+
+Build a picture of:
+- Current directory structure
+- Notes in each directory
+- Notes that seem misplaced based on their frontmatter
+
+### Step 2: Check Agent Pages
+
+Agent pages should live in their designated directories:
+
+| `type` frontmatter | Expected directory |
+|-------------------|-------------------|
+| `entity` | `entities/` |
+| `concept` | `concepts/` |
+| `comparison` | `comparisons/` |
+| `query` | `queries/` |
+
+For each agent page, check:
+- Does its current directory match its `type`?
+- If not, suggest a move
+
+### Step 3: Check User Notes
+
+User notes should **remain** in their existing directories (`Projects/`, `Daily/`, personal folders, etc.). Do not suggest moving them into agent directories. Suggest organization only if:
+
+- A user note has been placed in an agent directory (`entities/`, `concepts/`, `comparisons/`, `queries/`) — this is likely a mistake; propose moving it back to an appropriate user area
+- Multiple user notes about the same topic are scattered across **user** directories when they could be grouped there (never into agent dirs unless they are true agent pages with correct `type` frontmatter)
+
+### Step 4: Check Naming Conventions
+
+Per SCHEMA.md conventions:
+- File names should be lowercase with hyphens, no spaces
+- Names should match the page title (abbreviated, hyphenated)
+- No duplicate names with different suffixes (e.g., `feature-a.md` and `feature-a-1.md`)
+
+Flag any naming violations.
+
+### Step 5: Suggest Moves
+
+For each misplaced file:
+
+```
+Move: entities/wrong-place.md → concepts/wrong-place.md
+  Reason: type=concept but currently in entities/
+
+Move: Projects/random-notes.md → Projects/feature-a/
+  Reason: Content is about Feature A, should be grouped with other Feature A notes
+```
+
+### Step 6: Apply Moves (If Confirmed)
+
+Use Obsidian CLI to rename/move files:
+
+```bash
+obsidian rename file="old-path.md" new_name="new-path.md"
+```
+
+Always show the full plan before applying. Never move files silently.
+
+### Step 7: Update Wikilinks
+
+After moving files, check that all wikilinks to the moved files are still valid:
+
+```bash
+obsidian backlinks "moved-file"
+```
+
+Obsidian typically handles wikilink updates on rename automatically, but verify for safety.
+
+## Key Principles
+
+- **Suggest first, act second.** Default to dry_run mode. Show the full plan before making any changes.
+- **Agent directories are sacred.** Only agent pages should live in `entities/`, `concepts/`, `comparisons/`, `queries/`.
+- **User notes are user territory.** Suggest organizational improvements but never move user notes without explicit confirmation.
+- **Obsidian is first workbench.** All note operations go through Obsidian CLI.