@unified-product-graph/mcp-server 0.8.0 → 0.8.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@unified-product-graph/mcp-server",
-  "version": "0.8.0",
+  "version": "0.8.2",
   "description": "Local MCP server for .upg files. Read and write product knowledge graphs offline.",
   "license": "MIT",
   "author": "The Product Creator <hello@theproductcreator.com>",

package/scripts/claudemd-snippet.md

@@ -4,16 +4,16 @@ This project uses the Unified Product Graph to structure product thinking. A `.u
 
 ### Available Commands
 - `/upg`: See your product graph status and all available commands
-- `/upg-journey`: Guided 7-phase product journey with progress tracking
-- `/upg-init`: Bootstrap a new product graph (~5 min guided setup)
-- `/upg-explore`: Create any entity (90+ types across 32 domains)
-- `/upg-status`: Health dashboard with maturity scoring
-- `/upg-gaps`: Gap analysis across 8 business areas
-- `/upg-capture`: Capture session work into the graph
+- `/upg-show-journey`: Guided 7-phase product journey with progress tracking
+- `/upg-new-graph`: Bootstrap a new product graph (~5 min guided setup)
+- `/upg-walk-region`: Create any entity (90+ types across 32 domains)
+- `/upg-show-status`: Health dashboard with maturity scoring
+- `/upg-check-gaps`: Gap analysis across 8 business areas
+- `/upg-new-from-session`: Capture session work into the graph
 
 ### Graph Awareness
 When a `.upg` file exists, be aware of the product graph context. During conversations about product decisions, features, user research, or business strategy, offer to capture relevant insights into the graph. Don't be pushy; only suggest when the work is clearly graph-worthy (new features, strategic decisions, user insights). Routine code changes are not graph-worthy.
 
-At natural checkpoints (after commits, before session end, after design discussions), suggest running `/upg-capture` to review and save session work.
+At natural checkpoints (after commits, before session end, after design discussions), suggest running `/upg-new-from-session` to review and save session work.
 
 Learn more: unifiedproductgraph.org

package/scripts/install-skills.sh

@@ -252,8 +252,8 @@ fi
 echo ""
 echo "Quick start:"
 echo "  /upg:          see your product graph"
-echo "  /upg-init:     bootstrap a new graph (~5 min)"
-echo "  /upg-journey:  guided product journey"
+echo "  /upg-new-graph:     bootstrap a new graph (~5 min)"
+echo "  /upg-show-journey:  guided product journey"
 echo ""
 echo "Skills are symlinked; edits in the source are live immediately."
 echo ""

package/skills/upg/SKILL.md

@@ -76,10 +76,10 @@ Maturity ● ● ● ○ ○ **3/5** *<stage label>*
 
 | | Approach | Question | Common entry |
 |---|---|---|---|
-| 🧠 | **Plan** | What should I build next? | `/upg-explore <region>` · `/upg-strategy` · `/upg-journey` |
-| 🔍 | **Inspect** | What's broken? | `/upg-status` · `/upg-tree` · `/upg-inspect <entity>` |
-| 📊 | **Prioritise** | What's most important? | `/upg-prioritise` · `/upg-gaps` · `/upg-impact` |
-| 🧵 | **Trace** | Walk a path through what exists | `/upg-trace <anchor> → <destination>` · `/upg-impact <entity>` · `/upg-connect` |
+| 🧠 | **Plan** | What should I build next? | `/upg-walk-region <region>` · `/upg-new-strategy` · `/upg-show-journey` |
+| 🔍 | **Inspect** | What's broken? | `/upg-show-status` · `/upg-show-tree` · `/upg-show-entity <entity>` |
+| 📊 | **Prioritise** | What's most important? | `/upg-prioritise` · `/upg-check-gaps` · `/upg-show-impact` |
+| 🧵 | **Trace** | Walk a path through what exists | `/upg-trace <anchor> → <destination>` · `/upg-show-impact <entity>` · `/upg-link` |
 | 🪞 | **Reflect** | What should I be questioning? | `/upg-reflect` · *Five Whys · Pre-mortem · Red Team · Devil's Advocate · Second-order* |
 
 **Tell me which approach, or just describe what's on your mind.**
@@ -92,22 +92,22 @@ When the user selects an approach (or you infer one from their description), pre
 
 | Approach | Pre-call | Entry skill |
 |---|---|---|
-| 🧠 Plan | `mcp__unified-product-graph__list_playbooks()`; see region options | `/upg-explore <region>` |
-| 🔍 Inspect | `mcp__unified-product-graph__get_graph_digest()`; health metrics | `/upg-status` |
-| 📊 Prioritise | `mcp__unified-product-graph__get_graph_digest()`; gap + coverage data | `/upg-gaps` |
-| 🧵 Trace | `mcp__unified-product-graph__get_product_context()`; find anchor entities | `/upg-impact <entity>` |
+| 🧠 Plan | `mcp__unified-product-graph__list_playbooks()`; see region options | `/upg-walk-region <region>` |
+| 🔍 Inspect | `mcp__unified-product-graph__get_graph_digest()`; health metrics | `/upg-show-status` |
+| 📊 Prioritise | `mcp__unified-product-graph__get_graph_digest()`; gap + coverage data | `/upg-check-gaps` |
+| 🧵 Trace | `mcp__unified-product-graph__get_product_context()`; find anchor entities | `/upg-show-impact <entity>` |
 | 🪞 Reflect | `mcp__unified-product-graph__get_session_context()`; recent decisions | `/upg-reflect` |
 
 ---
 
 After the card, **make ONE concrete suggestion** based on the graph state. Pick the highest-value next move from this priority order:
 
-1. **No anchor entity for an active region** → suggest `/upg-explore <region>` to fill the missing scaffolding (Plan)
-2. **Anti-pattern violations present** → suggest `/upg-status` then `/upg-gaps` (Inspect)
+1. **No anchor entity for an active region** → suggest `/upg-walk-region <region>` to fill the missing scaffolding (Plan)
+2. **Anti-pattern violations present** → suggest `/upg-show-status` then `/upg-check-gaps` (Inspect)
 3. **A `decision` entity has no rationale or has gone stale** → suggest `/upg-reflect <decision>` (Reflect)
-4. **A `hypothesis` has no `evidence`** → suggest `/upg-hypothesis` to design the experiment (Plan)
-5. **A `feature` is `in_progress` with no linked outcome** → suggest `/upg-impact <feature>` (Trace)
-6. **Otherwise** → suggest `/upg-status` for a 30-second pulse
+4. **A `hypothesis` has no `evidence`** → suggest `/upg-new-hypothesis` to design the experiment (Plan)
+5. **A `feature` is `in_progress` with no linked outcome** → suggest `/upg-show-impact <feature>` (Trace)
+6. **Otherwise** → suggest `/upg-show-status` for a 30-second pulse
 
 Surface that one suggestion as: *"Looking at your graph, the highest-value next move is **X**. Want to start there?"*
 
@@ -129,7 +129,7 @@ Render (real markdown, NOT a code block):
 
 **Structure your product thinking as a connected graph, right here in the terminal.**
 
-Your graph lives in a `.upg` file; a portable JSON format you own and track with git. No cloud required, no lock-in.
+Your graph lives in a `.upg` file: a JSON format you own and track with git, with no cloud required.
 
 UPG is a chart of your product knowledge across **10 regions**: Strategy, Users & Needs, Discovery, Market, Experience, Delivery, Engineering, Business GTM, Analytics, Operations.
 
@@ -141,8 +141,8 @@ You read the chart through **5 approaches**: Plan, Inspect, Prioritise, Trace, R
 
 | | Command | What it does |
 |---|---|---|
-| 🌱 | `/upg-init` | Bootstrap your first product graph (guided, ~5 minutes) |
-| 📋 | `/upg-template` | Start from a proven pattern (SaaS, marketplace, mobile, OSS, agency) |
+| 🌱 | `/upg-new-graph` | Bootstrap your first product graph (guided, ~5 minutes) |
+| 📋 | `/upg-new-from-template` | Start from a proven pattern (SaaS, marketplace, mobile, OSS, agency) |
 
 > Learn more: **unifiedproductgraph.org**
 
@@ -154,7 +154,7 @@ If `/upg <something>` is given:
 
 1. **Match a subcommand:** `init`, `status`, `tree`, `gaps`, `inspect`, `reflect`, `explore`, `journey`, etc. → run the corresponding `/upg-<x>` skill.
 2. **Match an approach name:** `plan`, `inspect`, `prioritise`, `trace`, `reflect` → call `get_approach({ approach_id })` and route the user to the most-fitting skill for their graph state.
-3. **Match a region name:** `strategy`, `users_needs`, `experience_design_brand`, etc. → suggest `/upg-explore <region>`.
+3. **Match a region name:** `strategy`, `users_needs`, `experience_design_brand`, etc. → suggest `/upg-walk-region <region>`.
 4. **Free-text question:** parse intent into one of the 5 approaches, then suggest a skill.
 
 If unmatched, show the orientation card and ask: *"Did you mean one of these? Or tell me in your own words."*
@@ -172,49 +172,49 @@ When asked, show this expanded view:
 🧠 **Plan**
 | Skill | What |
 |---|---|
-| `/upg-explore <region>` | Walk a region's canonical playbook |
-| `/upg-run <playbook-id>` | Run any canonical playbook directly |
-| `/upg-journey` | 7-phase product journey |
-| `/upg-strategy` | Vision → mission → themes → outcomes |
-| `/upg-okr` | Objectives & key results |
-| `/upg-launch` | Go-to-market planning |
-| `/upg-research` | User research session |
-| `/upg-discover` | OST-guided discovery |
-| `/upg-hypothesis` | Structured hypothesis creation |
-| `/upg-persona` | Guided persona building |
+| `/upg-walk-region <region>` | Walk a region's canonical playbook |
+| `/upg-walk-playbook <playbook-id>` | Run any canonical playbook directly |
+| `/upg-show-journey` | 7-phase product journey |
+| `/upg-new-strategy` | Vision → mission → themes → outcomes |
+| `/upg-new-okr` | Objectives & key results |
+| `/upg-new-launch` | Go-to-market planning |
+| `/upg-new-research` | User research session |
+| `/upg-new-discovery` | OST-guided discovery |
+| `/upg-new-hypothesis` | Structured hypothesis creation |
+| `/upg-new-persona` | Guided persona building |
 
 🔍 **Inspect**
 | Skill | What |
 |---|---|
-| `/upg-status` | Health dashboard |
-| `/upg-tree` | Framework-aware tree view |
-| `/upg-inspect <entity>` | Deep-dive on one entity |
-| `/upg-analytics` | Product thinking metrics |
-| `/upg-verify` | Code-to-graph sync audit |
-| `/upg-diff` | What changed since last commit |
+| `/upg-show-status` | Health dashboard |
+| `/upg-show-tree` | Framework-aware tree view |
+| `/upg-show-entity <entity>` | Deep-dive on one entity |
+| `/upg-show-metrics` | Product thinking metrics |
+| `/upg-find-untracked` | Code-to-graph sync audit |
+| `/upg-show-diff` | What changed since last commit |
 
 📊 **Prioritise**
 | Skill | What |
 |---|---|
 | `/upg-prioritise` | RICE / WSJF / Eisenhower / ICE scoring across candidate items |
-| `/upg-gaps` | Strategic gap analysis + maturity scoring |
-| `/upg-impact` | Forward blast radius (Trace + Prioritise) |
+| `/upg-check-gaps` | Strategic gap analysis + maturity scoring |
+| `/upg-show-impact` | Forward blast radius (Trace + Prioritise) |
 
 🧵 **Trace**
 | Skill | What |
 |---|---|
 | `/upg-trace <anchor> → <destination>` | Walk a directed path through the graph (canonical Trace entry) |
-| `/upg-impact <entity>` | Forward / `--upstream` causal chain |
-| `/upg-connect` | Wire relationships between entities |
+| `/upg-show-impact <entity>` | Forward / `--upstream` causal chain |
+| `/upg-link` | Wire relationships between entities |
 
 🪞 **Reflect**
 | Skill | What |
 |---|---|
 | `/upg-reflect [scope]` | Five Whys / Pre-mortem / Red Team / Devil's Advocate / Second-order |
 
-**Tooling** (graph state operations; `/upg-init`, `/upg-capture`, `/upg-push`, `/upg-pull`, `/upg-snapshot`, `/upg-rollback`, `/upg-migrate`, `/upg-import`, `/upg-export`, `/upg-feedback`, `/upg-template`, `/upg-workspace`)
+**Tooling** (graph state operations; `/upg-new-graph`, `/upg-new-from-session`, `/upg-sync-push`, `/upg-sync-pull`, `/upg-sync-snapshot`, `/upg-fix-rollback`, `/upg-fix-types`, `/upg-sync-import`, `/upg-sync-export`, `/upg-send-feedback`, `/upg-new-from-template`, `/upg-use-workspace`)
 
-**Schema** (spec evolution; `/upg-schema-update`, `/upg-schema-consolidate`, `/upg-schema-evolve`, `/upg-schema-health`, `/upg-schema-changelog`, `/upg-schema-edges`)
+**Schema** (spec evolution; `/upg-new-schema-type`, `/upg-check-schema-merge`, `/upg-check-schema-coverage`, `/upg-check-schema`, `/upg-show-schema-changelog`, `/upg-check-schema-edges`)
 
 **Meta** (system reference; `/upg-context`, `/upg-design-system`)
 
@@ -224,11 +224,11 @@ When asked, show this expanded view:
 
 - **Orient, don't overwhelm.** Default view shows 5 approaches and ONE next move; never a wall of 40 skills.
 - **Approaches are the spine.** Plan, Inspect, Prioritise, Trace, Reflect; these are the conversational entry points. Skills implement them.
-- **Tooling is plumbing.** `/upg-init`, `/upg-push`, `/upg-snapshot` etc. are real and important, but they don't belong in the main view. They surface when the user needs them, or when they ask "show me everything."
+- **Tooling is plumbing.** `/upg-new-graph`, `/upg-sync-push`, `/upg-sync-snapshot` etc. are real and important, but they don't belong in the main view. They surface when the user needs them, or when they ask "show me everything."
 - **State-aware.** If a graph exists, show its state and one concrete suggestion. If not, show the get-started path.
 - **Listen before you list.** When the user describes a problem in their own words, route by approach, not by guessing skill names.
 - **Always write "Unified Product Graph" in full** when introducing it. Never abbreviate to "UPG" in user-facing text.
-- **The `.upg` file is the hero.** Open standard, portable, git-friendly. Reinforce ownership.
+- **The `.upg` file is the hero.** The graph lives in a file the user owns and tracks with git. Reinforce ownership.
 - **Follow the design system.** Use entity emojis, score dots, dashed dividers, and the logo mark from `/upg-context`.
 
 After routing the user to the next skill, call:

package/skills/{upg-gaps → upg-check-gaps}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: upg-gaps
+name: upg-check-gaps
 description: "Strategic Gap Analysis & Maturity Scoring"
 user-invocable: true
 argument-hint: "[description]"
@@ -7,7 +7,7 @@ category: cognitive
 approaches: [inspect, prioritise]
 ---
 
-# /upg-gaps: Strategic Gap Analysis & Maturity Scoring
+# /upg-check-gaps: Strategic Gap Analysis & Maturity Scoring
 
 You are a Unified Product Graph strategic advisor. Your job is to analyze the product graph for gaps, explain WHY each gap matters in product terms, prioritize by impact, calculate a maturity score, score against the tiered entity backbone, and provide specific actionable next steps.
 
@@ -18,9 +18,9 @@ You are a Unified Product Graph strategic advisor. Your job is to analyze the pr
 Use the `mcp__unified-product-graph__*` MCP tools (get_product_context with include_summary: true, list_nodes, get_node, search_nodes, query).
 
 **Boundary, in plain English:**
-- `/upg-status --quick` answers *"is anything bleeding right now?"* (the pulse).
-- `/upg-status --full` answers *"how mature is my product graph?"* (the dashboard).
-- **This skill (`/upg-gaps`)** answers *"what should I do next, and why?"*; deep gap analysis with WHY explanations, prioritised action plans, and forward-looking risk + blind-spot scanning. Skip maturity score rendering; that's `/upg-status --full` territory. Focus on: structural gaps, business area coverage, the action plan, and forward-looking risk signals.
+- `/upg-show-status --quick` answers *"is anything bleeding right now?"* (the pulse).
+- `/upg-show-status --full` answers *"how mature is my product graph?"* (the dashboard).
+- **This skill (`/upg-check-gaps`)** answers *"what should I do next, and why?"*; deep gap analysis with WHY explanations, prioritised action plans, and forward-looking risk + blind-spot scanning. Skip maturity score rendering; that's `/upg-show-status --full` territory. Focus on: structural gaps, business area coverage, the action plan, and forward-looking risk signals.
 
 ## Analysis Flow
 
@@ -32,17 +32,17 @@ get_graph_digest()
 
 The digest pre-computes counts, health metrics, chain completeness (`chains` section), and business area coverage (`coverage` section); all in ~500 tokens. Use the `query` tool only for structural gap details (e.g. which specific personas lack jobs).
 
-**Read the product stage** from `get_product_context()`. The stage lives in the product properties and is one of: `idea`, `mvp`, `growth`, `scale`. If no stage is set, default to `idea`.
+**Read the product stage** from `get_product_context()`. The stage is a canonical product-stage value — don't hard-code the enum; if you need the valid set, call `list_product_stages`. If no stage is set, default to the earliest (concept) stage.
 
-**Map stage to tier:**
+**Map stage to tier** (the three tiers are an editorial maturity framing; stable):
 
-| Stage | Tier | Target Types |
-|---|---|---|
-| `idea` or `mvp` | Solo Builder | 40 core types |
-| `growth` | Small Team | 55 types |
-| `scale` | Scale-Up | 70 types |
+| Stage | Tier |
+|---|---|
+| earliest stages (concept…beta) | Solo Builder |
+| launch / growth | Small Team |
+| mature / maintenance / sunset | Scale-Up |
 
-This tier determines the denominator for the business completeness score in Step 4b.
+The tier sets the *denominator* for the business completeness score in Step 4b. **Derive that denominator from MCP, not a baked number**: prefer `get_graph_digest`'s `coverage` section (it already reports area coverage against the spec), or count the relevant types from `list_entity_types` / `get_region`. The "40/55/70" figures from earlier versions of this skill are drift-prone — use the live counts instead and report whatever the digest's coverage fields give you.
 
 ### Step 2: Check Structural Gaps
 
@@ -52,43 +52,43 @@ Analyze gaps in priority order (validation > discovery > strategy > execution).
 
 **Hypotheses without experiments:**
 > ⚗️ You have **X** hypotheses with no 🧪 experiments. Untested assumptions are the #1 cause of product failure. Every bet you're making is currently just an opinion.
-> → `/upg-explore an experiment to test "<hypothesis title>"`
+> → `/upg-walk-region an experiment to test "<hypothesis title>"`
 
 **Experiments without learnings:**
 > 🧪 **X** experiments have no 📝 learnings. If you ran a test but didn't capture the result, the insight is lost.
-> → `/upg-explore a learning from the "<experiment title>" experiment`
+> → `/upg-walk-region a learning from the "<experiment title>" experiment`
 
 **Solutions without hypotheses:**
 > 🔧 **X** solutions have no ⚗️ hypothesis. You're building without stating what you believe will happen.
-> → `/upg-hypothesis for "<solution title>"`
+> → `/upg-new-hypothesis for "<solution title>"`
 
 #### 💡 Discovery Gaps (High Priority)
 
 **Personas without jobs:**
 > 👤 **X** personas have no 💼 jobs. Without knowing what job they're hiring your product to do, you're guessing at what to build.
-> → `/upg-explore a job for <persona name>`
+> → `/upg-walk-region a job for <persona name>`
 
 **Jobs without needs:**
 > 💼 **X** jobs have no 🔥 needs. You know the job, but not where the experience breaks down.
-> → `/upg-explore a need for "<job title>"`
+> → `/upg-walk-region a need for "<job title>"`
 
 **Outcomes without opportunities:**
 > 🎯 **X** outcomes have no 💡 opportunities. You know what success looks like but haven't identified problems worth solving.
-> → `/upg-discover` to run a guided discovery session
+> → `/upg-new-discovery` to run a guided discovery session
 
 #### 🎯 Strategy Gaps (Medium Priority)
 
 **Outcomes without metrics (KPIs):**
 > 🎯 **X** outcomes have no 📊 metrics. A goal without a metric is just a wish.
-> → `/upg-explore a metric (designation: "kpi") for "<outcome title>"`
+> → `/upg-walk-region a metric (designation: "kpi") for "<outcome title>"`
 
 **No personas at all:**
 > Your graph has zero 👤 personas. Who are you building for?
-> → `/upg-persona` to create a rich, detailed persona
+> → `/upg-new-persona` to create a rich, detailed persona
 
 **No competitors mapped:**
 > No ⚔️ competitors in your graph. Your users are solving this problem somehow today.
-> → `/upg-explore a competitor`
+> → `/upg-walk-region a competitor`
 
 #### 📦 Execution Gaps (Lower Priority)
 
@@ -109,7 +109,7 @@ Structural gaps tell you *what's missing right now*. This step interprets the gr
 | Untested bets | ⚗️ hypotheses with status `untested` (or no status), created >14 days ago | 🔴 High |
 | Assumption-based personas | 👤 personas with no connected 🔬 research_study or 💎 insight | 🟡 Medium |
 | Orphan features | 📦 features not connected to any 👤 persona (directly or via job chain) | 🔴 High |
-| Missing business model | Product at `mvp` or `growth` stage, zero 💰 business_model entities | 🔴 High |
+| Missing business model | Product at `build`, `launch`, or `growth` stage, zero 💰 business_model entities | 🔴 High |
 | Need without response | 🔥 needs with no connected 💡 opportunity | 🟡 Medium |
 | Validated but unbuilt | ⚗️ hypotheses with status `validated` but no connected 📦 feature | 🟡 Medium |
 | No learning loop | Zero 🧪 experiment or 📝 learning entities, AND >10 📦 features | 🔴 High |
@@ -118,7 +118,7 @@ Structural gaps tell you *what's missing right now*. This step interprets the gr
 
 Compare against known PM benchmarks. Adapt expected values to product stage.
 
-| Benchmark | Expected (idea/mvp) | Expected (growth+) | Source |
+| Benchmark | Expected (concept–beta) | Expected (launch+) | Source |
 |-----------|---------------------|---------------------|--------|
 | Personas | 2-4 | 3-6 | Lean Startup (Ries) |
 | Jobs per persona | >=2 | >=3 | JTBD (Christensen) |
@@ -138,7 +138,7 @@ Look at what's structurally absent given the product's stage and shape. Examples
 
 Name each blind spot in plain language, then INTERPRET; what does this pattern mean for the product? End each blind spot with a specific `/upg-` command.
 
-> **Strategy-without-measurement.** You have 6 outcomes but only 1 metric. Without measurement you can't tell which outcomes you're hitting. → `/upg-explore metric` for each outcome.
+> **Strategy-without-measurement.** You have 6 outcomes but only 1 metric. Without measurement you can't tell which outcomes you're hitting. → `/upg-walk-region metric` for each outcome.
 
 Render this section under a heading like:
 
@@ -182,9 +182,9 @@ This section scores the graph against the **8 business areas**: the fundamental
 
 #### The 8 Business Areas
 
-Each area maps to specific entity types. Count how many of the listed types have **at least 1 entity** in the graph.
+The **8 areas are an editorial grouping** (stable). The **type lists below are illustrative anchors, not the authoritative spec**: prefer `get_graph_digest`'s `coverage`/`by_type` sections for which types exist and are populated, and confirm any type name against `list_entity_types` (or `get_region(<region>)` for a region's membership) before treating a missing type as a gap. If a type listed below has been renamed or removed, defer to the digest's area coverage rather than reporting a phantom gap. Count how many of the area's live types have **at least 1 entity**.
 
-| Area | Entity Types (Solo Builder tier) |
+| Area | Entity Types (illustrative, Solo Builder tier) |
 |---|---|
 | 🎯 **Identity** | product, vision, mission |
 | 👤 **Understanding** | persona, job, need, research_study, insight |
@@ -203,7 +203,7 @@ At **Small Team** tier (growth), add these clusters to the scoring:
 | 🎨 **Design Alignment** | prototype, wireframe, design_component, user_flow |
 | 📣 **User Signal** | feature_request, feedback_theme, growth_loop, roadmap, nps_campaign |
 
-At **Scale-Up** tier (scale), add further:
+At **Scale-Up** tier (`mature`+), add further:
 
 | Cluster | Additional Types |
 |---|---|
@@ -280,57 +280,54 @@ If **🏦 Sustaining** has zero coverage, this is always a top-3 action:
 
 **[CRITICAL]** 🏦 You don't have a business model yet
 Your graph has zero entities in the Sustaining area; no business model, no revenue streams, no cost structure. Every product needs to answer "how does this make money?"
-→ `/upg-explore a business model for this product`
+→ `/upg-walk-region a business model for this product`
 
 If **📣 Reaching** has zero or low coverage:
 
 **[HIGH]** 📣 No go-to-market thinking
 You've built the product in your graph but haven't thought about how people find it. Who's your ideal customer? What channels will you use?
-→ `/upg-explore an ideal customer profile`
+→ `/upg-walk-region an ideal customer profile`
 
 If **💰 Converting** has zero or low coverage:
 
 **[HIGH]** 💰 No conversion path
 You know your value proposition but haven't mapped the journey from awareness to paying customer.
-→ `/upg-explore a pricing model`
+→ `/upg-walk-region a pricing model`
 
 Example full action plan:
 
 **1. [CRITICAL]** ⚗️ Test your hypotheses
 You have 4 untested hypotheses. Pick the riskiest one and design an experiment.
-→ `/upg-hypothesis` to structure a new one
+→ `/upg-new-hypothesis` to structure a new one
 
 **2. [CRITICAL]** 🏦 Define your business model
 Your graph has nothing in the Sustaining area. How does this product make money? What does it cost to run?
-→ `/upg-explore a business model for this product`
+→ `/upg-walk-region a business model for this product`
 
 **3. [HIGH]** 📣 Think about distribution
 You've only covered 2 of 5 Reaching types. Who's your ideal customer profile? What channels will you use?
-→ `/upg-explore an ideal customer profile`
+→ `/upg-walk-region an ideal customer profile`
 
 **4. [HIGH]** 💼 Add jobs for Sarah Chen
 Your primary persona has no Jobs-to-be-Done defined.
-→ `/upg-explore a job for Sarah Chen`
+→ `/upg-walk-region a job for Sarah Chen`
 
 **5. [MEDIUM]** 📊 Measure your outcomes
 "Reduce time-to-value" has no metric. Define the metric and targets.
-→ `/upg-explore a metric (designation: "kpi") for "Reduce time-to-value"`
+→ `/upg-walk-region a metric (designation: "kpi") for "Reduce time-to-value"`
 
 ### Step 6: Framework Recommendations
 
 Based on gaps, suggest which frameworks would help:
 
 > **Opportunity Solution Tree** *(Teresa Torres, 2021)*; Your discovery chain is incomplete. OST would structure outcome → opportunity → solution → experiment.
-> Try: `/upg-tree ost`
+> Try: `/upg-show-tree ost`
 
 ### Step 7: Closing
 
-┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄
-Your `.upg` file is yours: open standard, portable, git-friendly.
-unifiedproductgraph.org
 
 After rendering the gap analysis and your recommendation, call:
-`update_session_context({ skill_invoked: "upg-gaps", recommendation: "<the next skill you recommended>" })`
+`update_session_context({ skill_invoked: "upg-check-gaps", recommendation: "<the next skill you recommended>" })`
 
 ## Lens-Aware Gap Analysis
 
@@ -339,9 +336,9 @@ Check `get_session_context()` for the current lens. **Prepend lens-specific gaps
 **Engineering lens: prepend these gaps:**
 
 1. **Bugs without resolution:** 🐛 N bugs have no linked task or fix
-   → `/upg-explore task` to plan a fix
+   → `/upg-walk-region task` to plan a fix
 2. **Features without dependency tracking:** 📦 N in-progress features have no dependency edges
-   → `/upg-connect` to add blocks/enables edges
+   → `/upg-link` to add blocks/enables edges
 3. **Blockers without resolution:** 🔴 N blocking edges have no resolution
    → Update each with a resolution plan
 4. **Orphaned tasks:** 📋 N tasks not connected to any feature or story

package/skills/{upg-schema-health → upg-check-schema}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: upg-schema-health
+name: upg-check-schema
 description: "Schema usage audit: dead types, empty properties, orphan patterns, real vs theoretical"
 user-invocable: false
 audience: advanced
@@ -9,7 +9,7 @@ category: schema
 
 > ⚠️ **Advanced skill**: intended for UPG contributors and power users who understand the spec internals. Not for general use. Running mutation skills (schema-update, schema-consolidate, schema-evolve) without understanding the cascade can corrupt your graph.
 
-# /upg-schema-health: Schema Usage Audit
+# /upg-check-schema: Schema Usage Audit
 
 You are a schema health auditor. Your job is to compare what the UPG schema defines against what real graphs actually contain; surfacing dead types, empty properties, unused edges, and patterns the schema didn't anticipate.
 
@@ -27,17 +27,17 @@ You are a schema health auditor. Your job is to compare what the UPG schema defi
 
 **Mode 1: Audit a specific graph**
 ```
-/upg-schema-health .upg/entopo.upg
+/upg-check-schema .upg/entopo.upg
 ```
 
 **Mode 2: Audit all graphs in workspace**
 ```
-/upg-schema-health
+/upg-check-schema
 ```
 
 **Mode 3: Audit a specific domain against real data**
 ```
-/upg-schema-health engineering
+/upg-check-schema engineering
 ```
 
 ## Phase 1: Gather Data
@@ -252,8 +252,8 @@ Graph: [name] · [N] nodes · [M] edges · [T] types used
 - [list things that need fixing]
 
 RECOMMENDATIONS:
-1. [Most impactful action]; /upg-schema-evolve [domain]
-2. [Second action]; /upg-schema-consolidate [types]
+1. [Most impactful action]; /upg-check-schema-coverage [domain]
+2. [Second action]; /upg-check-schema-merge [types]
 3. [Third action]; consider deprecating [types]
 
 DEAD TYPE CANDIDATES FOR DEPRECATION:

package/skills/{upg-schema-evolve → upg-check-schema-coverage}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: upg-schema-evolve
+name: upg-check-schema-coverage
 description: "Domain deep-dive: audit entity coverage, surface gaps, design new types from real needs"
 user-invocable: false
 audience: advanced
@@ -9,7 +9,7 @@ category: schema
 
 > ⚠️ **Advanced skill**: intended for UPG contributors and power users who understand the spec internals. Not for general use. Running mutation skills (schema-update, schema-consolidate, schema-evolve) without understanding the cascade can corrupt your graph.
 
-# /upg-schema-evolve: Schema Evolution Through Domain Analysis
+# /upg-check-schema-coverage: Schema Evolution Through Domain Analysis
 
 You are a schema evolution advisor. Your job is to help the UPG schema grow thoughtfully, not by adding types speculatively, but by analysing real domains, real user feedback, and real cross-domain requirements to determine what's genuinely missing.
 
@@ -27,17 +27,17 @@ You are a schema evolution advisor. Your job is to help the UPG schema grow thou
 
 **Mode 1: Domain audit**
 ```
-/upg-schema-evolve engineering
+/upg-check-schema-coverage engineering
 ```
 
 **Mode 2: Requirement-driven**
 ```
-/upg-schema-evolve "Felix needs to track debugging sessions and how bugs relate to root causes"
+/upg-check-schema-coverage "Felix needs to track debugging sessions and how bugs relate to root causes"
 ```
 
 **Mode 3: Cross-domain analysis**
 ```
-/upg-schema-evolve design engineering
+/upg-check-schema-coverage design engineering
 ```
 
 ## Phase 1: Domain Audit
@@ -58,7 +58,7 @@ DOMAIN AUDIT: [Domain Name]
 
 | Entity Type | Properties | Edges | Skills | Graph UI | Status |
 |-------------|-----------|-------|--------|----------|--------|
-| service | ✓ ServiceProperties | 12 edges | `/upg-explore engineering` | ✓ | ✅ Complete |
+| service | ✓ ServiceProperties | 12 edges | `/upg-walk-region engineering` | ✓ | ✅ Complete |
 | deployment | ✓ DeploymentProperties | 4 edges | (none) | ✓ | 🟡 No skill |
 | data_flow | ✓ DataFlowProperties | 3 edges | (none) | ✓ | 🟡 No skill |
 ```
@@ -254,7 +254,7 @@ Edges:
   - benchmark_measures_endpoint (performance_benchmark → api_endpoint)
 
 Lens relevance: Engineering (primary), DevOps (secondary)
-Skill: Would be created by `/upg-explore engineering` (or a new `/upg-explore performance` playbook if the domain emerges as separate).
+Skill: Would be created by `/upg-walk-region engineering` (or a new `/upg-walk-region performance` playbook if the domain emerges as separate).
 
 Similar existing types:
   - metric: but lacks SLA/threshold semantics
@@ -272,14 +272,14 @@ Before approving any new type, run a quick consolidation check:
 2. Could this be a discriminator value on an existing type?
 3. Would this type have >3 instances in a typical graph?
 
-If any answer is "no", reconsider. Suggest running `/upg-schema-consolidate` for a deeper look.
+If any answer is "no", reconsider. Suggest running `/upg-check-schema-merge` for a deeper look.
 
 ## Phase 4: Action
 
 Once analysis is complete and the user agrees on what to add/change:
 
-1. **New types** → hand off to `/upg-schema-update` for the cascade
-2. **Consolidations** → hand off to `/upg-schema-consolidate` for migration design
+1. **New types** → hand off to `/upg-new-schema-type` for the cascade
+2. **Consolidations** → hand off to `/upg-check-schema-merge` for migration design
 3. **New edges only** → add directly to `UPG_EDGE_CATALOG` in `catalog/edge-catalog.ts`
 4. **Defer** → document the decision in your project's decisions log for future reference
 
@@ -294,10 +294,10 @@ EVOLUTION SUMMARY
 ✅ Covered by existing schema: [list]
 🆕 New types recommended: [list with reasons]
 🔗 New edges recommended: [list]
-🔀 Consolidation candidates: [list; run /upg-schema-consolidate]
+🔀 Consolidation candidates: [list; run /upg-check-schema-merge]
 ⏸️ Deferred: [list with revisit conditions]
 
-Next: /upg-schema-update [type] to implement approved additions
+Next: /upg-new-schema-type [type] to implement approved additions
 ```
 
 ## Key Principles

package/skills/{upg-schema-edges → upg-check-schema-edges}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: upg-schema-edges
+name: upg-check-schema-edges
 description: "Edge design advisor: when to add an edge, naming, direction, edge vs hierarchy vs entity"
 user-invocable: false
 audience: advanced
@@ -9,7 +9,7 @@ category: schema
 
 > ⚠️ **Advanced skill**: intended for UPG contributors and power users who understand the spec internals. Not for general use. Running mutation skills (schema-update, schema-consolidate, schema-evolve) without understanding the cascade can corrupt your graph.
 
-# /upg-schema-edges: Edge Design Advisor
+# /upg-check-schema-edges: Edge Design Advisor
 
 You are an edge design advisor. Your job is to help decide whether a relationship between entities should be an edge, a parent-child hierarchy link, or a relationship entity, and if it's an edge, how to name and direct it.
 
@@ -212,7 +212,7 @@ grep "SOURCE_.*_TARGET" packages/upg-spec/src/catalog/edge-catalog.ts
 When called without arguments, audit the edge map for problems:
 
 ```
-/upg-schema-edges
+/upg-check-schema-edges
 ```
 
 ### Check 1: Orphan Edges

package/skills/{upg-schema-consolidate → upg-check-schema-merge}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: upg-schema-consolidate
+name: upg-check-schema-merge
 description: "Evaluate whether entity types should merge: shared properties, structural analysis, migration path"
 user-invocable: false
 audience: advanced
@@ -9,7 +9,7 @@ category: schema
 
 > ⚠️ **Advanced skill**: intended for UPG contributors and power users who understand the spec internals. Not for general use. Running mutation skills (schema-update, schema-consolidate, schema-evolve) without understanding the cascade can corrupt your graph.
 
-# /upg-schema-consolidate: Entity Type Consolidation
+# /upg-check-schema-merge: Entity Type Consolidation
 
 You are a schema analyst. Your job is to evaluate whether two or more entity types should be consolidated into a single type with a discriminator property, or kept separate. You do this through structured analysis, not gut feeling.
 
@@ -27,12 +27,12 @@ You are a schema analyst. Your job is to evaluate whether two or more entity typ
 
 **Mode 1: Compare specific types**
 ```
-/upg-schema-consolidate architecture_decision design_decision
+/upg-check-schema-merge architecture_decision design_decision
 ```
 
 **Mode 2: Scan a domain for candidates**
 ```
-/upg-schema-consolidate engineering
+/upg-check-schema-merge engineering
 ```
 
 ## Analysis Framework
@@ -168,7 +168,7 @@ Parent migration:
 - `upg-migrate` skill handles the retyping
 - Old `.upg` files with `architecture_decision` still parse and auto-migrate
 
-**5d. Cascade the change** using `/upg-schema-update`
+**5d. Cascade the change** using `/upg-new-schema-type`
 
 ### Step 5 (Alternative): If Keeping Separate: Document Why