@unified-product-graph/mcp-server 0.8.1 → 0.8.4

package/skills/{upg-analytics → upg-show-metrics}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: upg-analytics
+name: upg-show-metrics
 description: "Product thinking metrics: hypothesis velocity, coverage ratio, evidence density"
 user-invocable: true
 argument-hint: ""
@@ -7,7 +7,7 @@ category: cognitive
 approaches: [inspect]
 ---
 
-# /upg-analytics: Product Thinking Metrics
+# /upg-show-metrics: Product Thinking Metrics
 
 You are a fast analytics dashboard. Your job: fetch metrics, render a dashboard, suggest ONE action. No questions. No interaction. Just the numbers and what they mean.
 
@@ -17,9 +17,9 @@ You are a fast analytics dashboard. Your job: fetch metrics, render a dashboard,
 
 Call `get_graph_digest()` first. Check for these conditions before rendering metrics:
 
-- **Hypothesis type mismatch**: If `by_type` shows `hypothesis_claim` nodes but zero `hypothesis` nodes, surface: "Your graph has deprecated `hypothesis_claim` entities. Run `/upg-migrate` to convert them to `hypothesis` before this analysis is accurate."
+- **Hypothesis type mismatch**: If `by_type` shows `hypothesis_claim` nodes but zero `hypothesis` nodes, surface: "Your graph has deprecated `hypothesis_claim` entities. Run `/upg-fix-types` to convert them to `hypothesis` before this analysis is accurate."
 - **Hypothesis velocity**: The "Hypothesis Velocity" metric shows a point-in-time status distribution (untested vs. tested), not a rate of change. Label it clearly: "Hypothesis status (not a velocity measure)" when local-only.
-- **Stage mismatch**: If `product.stage` is `concept`, treat it as equivalent to `idea` stage for all benchmark comparisons.
+- **Stage benchmarks are canonical**: `product.stage` is a canonical `UPGProductStage` (`concept | validation | build | beta | launch | growth | mature | maintenance | sunset`), and the count/relationship benchmarks are keyed on those same canonical stages. Compare directly; do NOT translate to legacy `idea`/`mvp`/`scale` labels.
 
 ## Tools
 
@@ -62,7 +62,7 @@ Show each status with its status dot and count, then a filled bar for % resolved
   ▓▓▓▓▓▓▓▓▓▓▓▓▓▓░░░░░░░░ 58% resolved
 ```
 
-If zero hypotheses exist, show: "No hypotheses yet; run `/upg-hypothesis` to start testing your riskiest assumptions."
+If zero hypotheses exist, show: "No hypotheses yet; run `/upg-new-hypothesis` to start testing your riskiest assumptions."
 
 ### Coverage Ratio
 
@@ -73,7 +73,7 @@ Show persona count with complete chains out of total, plus a filled bar:
   ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓░░░░░ 75%
 ```
 
-If zero personas, show: "No personas yet; run `/upg-persona` to define who you're building for."
+If zero personas, show: "No personas yet; run `/upg-new-persona` to define who you're building for."
 
 ### Evidence Density
 
@@ -116,7 +116,7 @@ One short paragraph: what stands out, and what's the single fastest win? End wit
 
 Example:
 > Your hypothesis pipeline is moving: 58% resolved. But 4 are still untested. The fastest win is picking one and designing an experiment.
-> → `/upg-hypothesis` to test your riskiest assumption
+> → `/upg-new-hypothesis` to test your riskiest assumption
 
 ## Key Principles
 
@@ -124,12 +124,9 @@ Example:
 - **Filled bars** for all percentages; max 22 characters (▓ for filled, ░ for empty).
 - **Interpret, don't just report.** "1.08 evidence per hypothesis <- healthy" beats "ratio: 1.08".
 - **ONE recommendation.** Pick the metric that needs the most attention and suggest the matching skill.
-- **This is NOT `/upg-status --quick`** (5 quick signals) or **/upg-gaps** (deep maturity scoring + action plan). This is the quantitative dashboard.
+- **This is NOT `/upg-show-status --quick`** (5 quick signals) or **/upg-check-gaps** (deep maturity scoring + action plan). This is the quantitative dashboard.
 - **Follow the design system.** Entity emojis, status dots, dashed dividers, consistent formatting from `/upg-context`.
 
-┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄
-Your .upg file is yours: open standard, portable, git-friendly.
-unifiedproductgraph.org
 
 After rendering your recommendation, call:
-`update_session_context({ skill_invoked: "upg-analytics", recommendation: "<the next skill you recommended>" })`
+`update_session_context({ skill_invoked: "upg-show-metrics", recommendation: "<the next skill you recommended>" })`

package/skills/{upg-schema-changelog → upg-show-schema-changelog}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: upg-schema-changelog
+name: upg-show-schema-changelog
 description: "Generate a schema changelog: what changed between versions, migration notes, breaking changes"
 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-changelog: Schema Changelog Generator
+# /upg-show-schema-changelog: Schema Changelog Generator
 
 You are a schema changelog generator. Your job is to diff the UPG schema between versions and produce a human-readable changelog that tells adopters what changed, why, and how to migrate.
 
@@ -26,18 +26,18 @@ You are a schema changelog generator. Your job is to diff the UPG schema between
 
 **Mode 1: Diff against git**
 ```
-/upg-schema-changelog latest
+/upg-show-schema-changelog latest
 ```
 Compares current working state against the last tagged version.
 
 **Mode 2: Between specific versions**
 ```
-/upg-schema-changelog 0.1.0 0.2.0
+/upg-show-schema-changelog 0.1.0 0.2.0
 ```
 
 **Mode 3: Current PR changes**
 ```
-/upg-schema-changelog pr
+/upg-show-schema-changelog pr
 ```
 Compares current branch against `origin/dev`.
 

package/skills/{upg-status → upg-show-status}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: upg-status
+name: upg-show-status
 description: "Product Graph Health Dashboard"
 user-invocable: true
 argument-hint: "[--quick | --full | description]"
@@ -7,7 +7,7 @@ category: cognitive
 approaches: [inspect]
 ---
 
-# /upg-status: Product Graph Health Dashboard
+# /upg-show-status: Product Graph Health Dashboard
 
 You are a Unified Product Graph analytics engine. Your job is to produce a dashboard of the product graph's health; entity counts, region coverage (the 10 canonical regions that roll up the atomic domains), connectivity, validation depth, and maturity scoring.
 
@@ -15,15 +15,15 @@ You are a Unified Product Graph analytics engine. Your job is to produce a dashb
 
 ## Modes
 
-- `/upg-status --quick`: 10-second pulse. 5 health signals + ONE recommendation. No bars, no benchmarks, no maturity score. Use the **Quick Pulse Mode** section below.
-- `/upg-status` or `/upg-status --full` (default); the full dashboard described below.
+- `/upg-show-status --quick`: 10-second pulse. 5 health signals + ONE recommendation. No bars, no benchmarks, no maturity score. Use the **Quick Pulse Mode** section below.
+- `/upg-show-status` or `/upg-show-status --full` (default); the full dashboard described below.
 
 **Boundary, in plain English:**
 - `--quick` answers *"is anything bleeding right now?"* (the pulse).
 - `--full` answers *"how mature is my product graph?"* (the dashboard).
-- `/upg-gaps` answers *"what should I do next, and why?"* (the action plan).
+- `/upg-check-gaps` answers *"what should I do next, and why?"* (the action plan).
 
-If a recent `/upg-gaps` run is in session context, skip the TOP GAP section in `--full` mode.
+If a recent `/upg-check-gaps` run is in session context, skip the TOP GAP section in `--full` mode.
 
 ## Tools
 
@@ -72,10 +72,10 @@ The bar is 20 chars wide. Fill `▓` proportionally to the fraction (numerator /
 The **numerator** = how many entity types in that area actually have ≥1 node in the graph.
 The **denominator** = the total entity types expected for that area at the product's current stage tier.
 
-**Stage → Tier mapping:**
-- idea or mvp → **Solo Builder** (40 entities across 8 areas)
-- growth → **Small Team** (55 entities)
-- scale → **Scale-Up** (70 entities)
+**Stage → Tier mapping** (stage is a canonical `UPGProductStage`):
+- `concept`, `validation`, `build`, `beta` → **Solo Builder** (40 entities across 8 areas)
+- `launch`, `growth` → **Small Team** (55 entities)
+- `mature`, `maintenance`, `sunset` → **Scale-Up** (70 entities)
 
 **Business Completeness Score**: render immediately after the table:
 
@@ -86,14 +86,14 @@ Business Completeness: **<covered>/<total>** (<percent>%) for <Tier Name> stage
 → ...
 
 Only list areas where coverage < 100%. Use these suggested commands:
-- 📣 Reaching → `/upg-launch` to define positioning and channels
-- 💰 Converting → `/upg-explore` to define your value proposition and pricing
-- 🏦 Sustaining → `/upg-explore business_model` to build your business model
-- 📊 Learning → `/upg-explore` to add metrics and retrospectives
-- 📦 Building → `/upg-explore` to flesh out features and stories
-- 👤 Understanding → `/upg-discover` to deepen user research
-- 💡 Discovery → `/upg-discover` to explore more opportunities
-- 🎯 Identity → `/upg-explore` to define your product identity
+- 📣 Reaching → `/upg-new-launch` to define positioning and channels
+- 💰 Converting → `/upg-walk-region` to define your value proposition and pricing
+- 🏦 Sustaining → `/upg-walk-region business_model` to build your business model
+- 📊 Learning → `/upg-walk-region` to add metrics and retrospectives
+- 📦 Building → `/upg-walk-region` to flesh out features and stories
+- 👤 Understanding → `/upg-new-discovery` to deepen user research
+- 💡 Discovery → `/upg-new-discovery` to explore more opportunities
+- 🎯 Identity → `/upg-walk-region` to define your product identity
 
 If all 8 areas are fully covered, instead show:
 > *All 8 business areas covered; your graph has full business breadth.*
@@ -148,10 +148,10 @@ RECOMMENDED FRAMEWORKS
 Based on the current state, suggest 2-3 frameworks that would add the most value. Use this format:
 
 > **Opportunity Solution Tree** *(Teresa Torres, 2021)*; Your discovery chain is partially built. OST would structure outcome → opportunity → solution → experiment.
-> Try: `/upg-tree ost`
+> Try: `/upg-show-tree ost`
 
 > **Hypothesis Testing** *(Eric Ries, 2011)*; 4 untested hypotheses need experiments.
-> Try: `/upg-tree validation`
+> Try: `/upg-show-tree validation`
 
 ┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄
 
@@ -167,14 +167,11 @@ QUICK ACTIONS
 
 | | |
 |---|---|
-| `/upg-gaps` | Deep-dive into what's missing and why |
-| `/upg-tree user` | See your persona → job → need chains |
-| `/upg-explore` | Add missing entities |
-| `/upg-discover` | Run a guided OST discovery session |
+| `/upg-check-gaps` | Deep-dive into what's missing and why |
+| `/upg-show-tree user` | See your persona → job → need chains |
+| `/upg-walk-region` | Add missing entities |
+| `/upg-new-discovery` | Run a guided OST discovery session |
 
-┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄
-Your `.upg` file is yours: open standard, portable, git-friendly.
-unifiedproductgraph.org
 
 ---
 
@@ -213,9 +210,11 @@ Check `get_session_context()` for the current lens. Adapt the dashboard:
 | 🔵 Planned | N | [feature names] |
 | ✅ Shipped | N | [feature names] |
 
-Show: `BLOCKERS: N active · BUGS: N open (M critical) · DEBT: N items`
+A feature counts as **Blocked** when it has an inbound blocking edge (e.g. `bug_blocks_feature`, `dependency_blocks_*`, `technical_debt_item_slows_*`), NOT when it carries a `blocker` type; there is no `blocker` entity type. Map feature `status` (`proposed | in_progress | shipped | archived`) to In Progress / Planned / Shipped.
+
+Show: `BLOCKED: N features · BUGS: N open (M critical) · DEBT: N items` (blocking signal comes from `bug` / `technical_debt_item` / `dependency` / `root_cause` entities, not a `blocker` type)
 
-Recommend: `/upg-impact --upstream`, `/upg-impact`, `/upg-explore engineering` (covers technical debt + architecture)
+Recommend: `/upg-show-impact --upstream`, `/upg-show-impact`, `/upg-walk-region engineering` (covers technical debt + architecture)
 
 **Design lens:** Replace "BY BUSINESS AREA" with "DESIGN COVERAGE":
 
@@ -226,7 +225,7 @@ Recommend: `/upg-impact --upstream`, `/upg-impact`, `/upg-explore engineering` (
 | 🔄 Flows | N complete | [list] |
 | 🎨 Tokens | N defined | [count] |
 
-Recommend: `/upg-explore ux_design` (covers screens, flows, wireframes, design audit)
+Recommend: `/upg-walk-region ux_design` (covers screens, flows, wireframes, design audit)
 
 **Growth lens:** Replace "BY BUSINESS AREA" with "GROWTH STATUS":
 
@@ -234,7 +233,7 @@ Recommend: `/upg-explore ux_design` (covers screens, flows, wireframes, design a
 |---------|---------|-----------|
 | [channel name] | N | N active |
 
-Recommend: `/upg-explore growth` (funnel + experiments), `/upg-explore marketing` (positioning + SEO + campaigns), `/upg-launch` (GTM workshop)
+Recommend: `/upg-walk-region growth` (funnel + experiments), `/upg-walk-region marketing` (positioning + SEO + campaigns), `/upg-new-launch` (GTM workshop)
 
 **Product lens (default):** Show the standard business area coverage table (no change).
 
@@ -249,7 +248,7 @@ Recommend: `/upg-explore growth` (funnel + experiments), `/upg-explore marketing
 
 ## Business Area Entity Mapping
 
-### Solo Builder tier (idea / mvp stage: 40 entities)
+### Solo Builder tier (`concept`–`beta` stage: 40 entities)
 
 | Area | Entity Types |
 |---|---|
@@ -262,7 +261,7 @@ Recommend: `/upg-explore growth` (funnel + experiments), `/upg-explore marketing
 | 🏦 Sustaining | business_model, revenue_stream, cost_structure, unit_economics, pricing_strategy |
 | 📊 Learning | outcome, metric, objective, key_result, retrospective |
 
-### Small Team tier (growth stage: 55 entities)
+### Small Team tier (`launch`–`growth` stage: 55 entities)
 
 All Solo Builder entities plus:
 
@@ -274,7 +273,7 @@ All Solo Builder entities plus:
 | 📦 Building | + team, role, dependency, prototype, wireframe, design_component, user_flow (flow_type: onboarding), roadmap, screen |
 | 📊 Learning | + milestone, feature_request, feedback_theme |
 
-### Scale-Up tier (scale stage: 70 entities)
+### Scale-Up tier (`mature`–`sunset` stage: 70 entities)
 
 All Small Team entities plus additional entities per area to reach 70 total. Expand each area with deeper operational and governance entity types appropriate for scale.
 
@@ -291,10 +290,10 @@ get_session_context()   // see what skills already ran + what was recommended
 
 After rendering, register this invocation:
 ```
-update_session_context({ skill_invoked: "upg-status", mode: "quick", recommendation: "<your recommendation>" })
+update_session_context({ skill_invoked: "upg-show-status", mode: "quick", recommendation: "<your recommendation>" })
 ```
 
-The digest pre-computes health metrics, chain completeness, coverage, and orphan rates server-side. No `list_nodes` needed. No maturity scoring (that's `--full` mode). No action plans (that's `/upg-gaps`).
+The digest pre-computes health metrics, chain completeness, coverage, and orphan rates server-side. No `list_nodes` needed. No maturity scoring (that's `--full` mode). No action plans (that's `/upg-check-gaps`).
 
 ### Health Signals (5)
 
@@ -318,8 +317,8 @@ Render as real markdown, NOT inside a code block. Use this structure exactly:
 
 ```
   🟡 3 hypotheses untested; ⚗️ "Wizard reduces drop-off", ⚗️ "Users prefer mobile", ⚗️ "Pricing tier works"
-  🔴 2 personas have no jobs; 👤 "Jordan", 👤 "Sam" (add JTBDs with /upg-persona)
-  🟡 5 entities below 50% complete; consider /upg-gaps for details
+  🔴 2 personas have no jobs; 👤 "Jordan", 👤 "Sam" (add JTBDs with /upg-new-persona)
+  🟡 5 entities below 50% complete; consider /upg-check-gaps for details
   🟢 All key chains connected
   🟢 Graph updated today
 ```
@@ -329,7 +328,7 @@ Render as real markdown, NOT inside a code block. Use this structure exactly:
 One short paragraph: what's the overall health, and what's the single fastest win? End with a specific command suggestion.
 
 > Your graph is healthy but has untested bets. The fastest win is running one experiment.
-> → `/upg-hypothesis` to pick one and design a test
+> → `/upg-new-hypothesis` to pick one and design a test
 
 ### Quick mode principles
 
@@ -337,4 +336,4 @@ One short paragraph: what's the overall health, and what's the single fastest wi
 - **Name entities, not just counts.** "3 untested hypotheses" < naming them.
 - **Signal colours:** 🟢 healthy, 🟡 attention needed, 🔴 action required.
 - **ONE recommendation.** Pick the highest-impact action and suggest it.
-- **This is NOT `--full`** (maturity score + bars + benchmarks + frameworks) or `/upg-gaps` (deep action plans). This is the 10-second pulse.
+- **This is NOT `--full`** (maturity score + bars + benchmarks + frameworks) or `/upg-check-gaps` (deep action plans). This is the 10-second pulse.

package/skills/{upg-tree → upg-show-tree}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: upg-tree
+name: upg-show-tree
 description: "Framework-Aware Tree View"
 user-invocable: true
 argument-hint: "[pattern]"
@@ -7,7 +7,7 @@ category: cognitive
 approaches: [inspect]
 ---
 
-# /upg-tree: Framework-Aware Tree View
+# /upg-show-tree: Framework-Aware Tree View
 
 You are a Unified Product Graph tree renderer. Your job is to display the product graph as a hierarchical tree, optionally filtered through a named framework pattern. You know the frameworks and can render any tree archetype.
 
@@ -20,13 +20,13 @@ Use `mcp__unified-product-graph__query` for tree fetching (one call per tree) an
 ## Usage
 
 ```
-/upg-tree: Auto-detect best tree based on graph contents
-/upg-tree ost: Opportunity Solution Tree
-/upg-tree okr: Objectives & Key Results
-/upg-tree user: Persona → JTBD → Pain Point chain
-/upg-tree product: Product → Feature → Epic → User Story
-/upg-tree validation: Hypothesis → Experiment → Learning
-/upg-tree strategy: Vision → Mission → Strategic Theme → Initiative → Outcome
+/upg-show-tree: Auto-detect best tree based on graph contents
+/upg-show-tree ost: Opportunity Solution Tree
+/upg-show-tree okr: Objectives & Key Results
+/upg-show-tree user: Persona → JTBD → Pain Point chain
+/upg-show-tree product: Product → Feature → Epic → User Story
+/upg-show-tree validation: Hypothesis → Experiment → Learning
+/upg-show-tree strategy: Vision → Mission → Strategic Theme → Initiative → Outcome
 ```
 
 ## Named Tree Patterns
@@ -147,7 +147,7 @@ Example rendering (OST):
 │
 ├─ 💡 Users don't get value in first 5 min
 │     reach ● ● ● ● ●   pain ● ● ● ● ○   freq ● ● ● ○ ○
-│     (no solutions; /upg-explore a solution)
+│     (no solutions; /upg-walk-region a solution)
 │
 └─ 💡 Onboarding asks for too much upfront
       reach ● ● ● ● ○   pain ● ● ● ○ ○   freq ● ● ● ● ○
@@ -199,9 +199,9 @@ After the tree, display outside the code block:
 
 **<N>** entities shown · **<N>** levels deep · <breakdown by type emojis>
 
-Other views: `/upg-tree user` · `/upg-tree validation` · `/upg-tree okr`
+Other views: `/upg-show-tree user` · `/upg-show-tree validation` · `/upg-show-tree okr`
 
-→ `/upg-push` to sync | unifiedproductgraph.org for the standard
+→ `/upg-sync-push` to sync | unifiedproductgraph.org for the standard
 
 ## Auto-Detection Logic
 
@@ -221,13 +221,13 @@ If the graph is empty or has no entities matching the requested pattern:
 >
 > Your graph needs: <list root entity types for this pattern>
 >
-> Get started: `/upg-init` to bootstrap your product graph
-> Or: `/upg-explore` to add specific entity types
+> Get started: `/upg-new-graph` to bootstrap your product graph
+> Or: `/upg-walk-region` to add specific entity types
 
 ## Key Principles
 
 - **Framework attribution matters.** Always credit the framework's creator.
 - **Show properties, not just titles.** A tree of titles is useless; show the data.
-- **Auto-detect when possible.** If the user just says `/upg-tree`, pick the most informative view.
+- **Auto-detect when possible.** If the user just says `/upg-show-tree`, pick the most informative view.
 - **Suggest other views.** After rendering one tree, mention the other available patterns.
 - **Follow the design system.** Entity emojis, score dots, filled bars, nested blocks, annotation arrows.

package/skills/{upg-export → upg-sync-export}/SKILL.md

@@ -1,12 +1,12 @@
 ---
-name: upg-export
+name: upg-sync-export
 description: "Export Graph as Shareable Artifact"
 user-invocable: true
 argument-hint: "[description]"
 category: tooling
 ---
 
-# /upg-export: Export Graph as Shareable Artifact
+# /upg-sync-export: Export Graph as Shareable Artifact
 
 You are a Unified Product Graph export engine. Your job is to produce a well-formatted export of the entire product graph that can be shared with stakeholders, pasted into documents, or used as a snapshot for review.
 
@@ -20,7 +20,7 @@ Use the `mcp__unified-product-graph__*` MCP tools (get_product_context, get_grap
 
 ### Step 1: Choose Format
 
-If the user specified a format as an argument (e.g., `/upg-export mermaid`), skip this step. Otherwise ask:
+If the user specified a format as an argument (e.g., `/upg-sync-export mermaid`), skip this step. Otherwise ask:
 
 ```
 Which export format?
@@ -52,7 +52,7 @@ Produce a markdown document with these sections:
 
 > Exported from the Unified Product Graph (UPG)
 > Date: <current date>
-> Stage: <idea | mvp | growth | scale>
+> Stage: <concept | validation | build | beta | launch | growth | mature | maintenance | sunset>
 
 ## Product Overview
 
@@ -177,13 +177,10 @@ Produce a markdown document with these sections:
 
 ## Tree View
 
-<Render the full product-rooted tree using the same format as /upg-tree>
+<Render the full product-rooted tree using the same format as /upg-show-tree>
 
 ---
 
-┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄
-Your .upg file is yours: open standard, portable, git-friendly.
-unifiedproductgraph.org
 
 *Structured using the Unified Product Graph; an open standard for product knowledge.*
 ```
@@ -364,11 +361,11 @@ Stats: X entities, Y edges, Z domains
 Format: <Full Markdown | Mermaid | CSV | Markdown Report>
 
 Next steps:
-- /upg-export <other format>: try a different format
-- /upg-discover: run another discovery session
-- /upg-gaps: check for gaps
-- /upg-status: live dashboard view
-- /upg-diff: see what changed since your last commit
+- /upg-sync-export <other format>: try a different format
+- /upg-new-discovery: run another discovery session
+- /upg-check-gaps: check for gaps
+- /upg-show-status: live dashboard view
+- /upg-show-diff: see what changed since your last commit
 ```
 
 ## Conditional Sections

package/skills/{upg-import → upg-sync-import}/SKILL.md

@@ -1,12 +1,12 @@
 ---
-name: upg-import
+name: upg-sync-import
 description: "Import product knowledge from external tools into your .upg graph: Markdown, GitHub, Linear, Jira, Dovetail, Vistaly, Notion, and 30+ more adapters"
 user-invocable: true
 argument-hint: "[tool]"
 category: tooling
 ---
 
-# /upg-import: Import Product Knowledge
+# /upg-sync-import: Import Product Knowledge
 
 You are a UPG import engine. Pull structured product knowledge from external tools into the user's .upg graph.
 
@@ -24,7 +24,7 @@ You are a UPG import engine. Pull structured product knowledge from external too
 
 ## Step 1: Choose Source
 
-Skip if the user provided an argument (e.g. `/upg-import github`). Otherwise present the menu:
+Skip if the user provided an argument (e.g. `/upg-sync-import github`). Otherwise present the menu:
 
 ```
 Where do you want to import from?
@@ -165,10 +165,10 @@ After any successful import:
 
 ```
 Your graph just grew! Suggested next steps:
-- /upg-tree: see the full structure
-- /upg-gaps: check what's still missing
-- /upg-status: health dashboard with completeness scores
-- /upg-discover: AI-powered entity discovery from what you just imported
+- /upg-show-tree: see the full structure
+- /upg-check-gaps: check what's still missing
+- /upg-show-status: health dashboard with completeness scores
+- /upg-new-discovery: AI-powered entity discovery from what you just imported
 ```
 
 ---
@@ -181,9 +181,3 @@ Your graph just grew! Suggested next steps:
 - **Deduplicate.** Check existing nodes with `search_nodes` before creating. Flag potential matches.
 - **Respect mapping_confidence.** Adapters set `'high'` / `'medium'` / `'low'`; surface `'low'` items for human review.
 - **Never auto-emit `insight_informs_opportunity`.** This edge always requires PM judgment. Emit a warning instead.
-
----
-
-┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄
-37 adapters. Open standard. Your .upg file is portable and git-friendly.
-unifiedproductgraph.org/integrations

package/skills/{upg-pull → upg-sync-pull}/SKILL-DETAIL.md

@@ -3,7 +3,7 @@ name: upg-pull-detail
 description: "Detailed pull flow, merge logic, incremental sync"
 ---
 
-# /upg-pull: Pull Flow Detail
+# /upg-sync-pull: Pull Flow Detail
 
 ## Pull Flow
 
@@ -21,7 +21,7 @@ To pull from The Product Creator, you need an API key configured.
 2. Go to Settings → API Keys → Create New Key
 3. Add to your .mcp.json config
 
-Once configured, run /upg-pull again.
+Once configured, run /upg-sync-pull again.
 ```
 
 ### Step 2: Select Product
@@ -151,7 +151,7 @@ Pulled "<Product Name>" from The Product Creator cloud.
   Connections: <N>
   Domains: <N> covered
 
-Your graph is now local. It's a .upg file; portable, git-friendly, yours.
+Your graph is now local in a .upg file you can edit, diff, and commit.
 ```
 
 Then show the "What You Can Do Now" section (Step 6).
@@ -188,7 +188,7 @@ If user declines, suggest:
 You can:
   - Save your current .upg file first: cp product.upg product-backup.upg
   - Or commit it to git: git add product.upg && git commit -m "Backup before pull"
-  - Then run /upg-pull again
+  - Then run /upg-sync-pull again
 ```
 
 ---
@@ -349,7 +349,7 @@ Then show the "What You Can Do Now" section (Step 6 below).
 **Cloud graph is empty:**
 ```
 "<Product Name>" has no entities in the cloud yet.
-Build it locally with /upg-init, then /upg-push when ready.
+Build it locally with /upg-new-graph, then /upg-sync-push when ready.
 ```
 
 **Very large graph (200+ entities):**
@@ -370,12 +370,12 @@ Show this section after every successful pull (full or incremental):
 ```
 ### What You Can Do Now
 
-  /upg-status: See your graph health dashboard
-  /upg-tree: View through framework lenses (ost, user, validation...)
-  /upg-gaps: Find strategic gaps and get action plans
-  /upg-explore: Add new entities locally
-  /upg-discover: Run a guided discovery session
-  /upg-push: Push local changes back to the cloud
+  /upg-show-status: See your graph health dashboard
+  /upg-show-tree: View through framework lenses (ost, user, validation...)
+  /upg-check-gaps: Find strategic gaps and get action plans
+  /upg-walk-region: Add new entities locally
+  /upg-new-discovery: Run a guided discovery session
+  /upg-sync-push: Push local changes back to the cloud
 
 ### Version Control
 
@@ -387,12 +387,8 @@ Show this section after every successful pull (full or incremental):
 
 ### Stay in Sync
 
-  Edit locally, then /upg-push to sync back to the cloud.
-  Pull again with /upg-pull to get the latest from your team.
+  Edit locally, then /upg-sync-push to sync back to the cloud.
+  Pull again with /upg-sync-pull to get the latest from your team.
   The .upg file is your source of truth for local work.
 
-┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄
-Your .upg file is yours: open standard, portable, git-friendly.
-unifiedproductgraph.org
 ```
-

package/skills/{upg-pull → upg-sync-pull}/SKILL.md

@@ -1,12 +1,12 @@
 ---
-name: upg-pull
+name: upg-sync-pull
 description: "Pull a cloud graph down to a local .upg file"
 user-invocable: true
 argument-hint: "[product-name]"
 category: tooling
 ---
 
-# /upg-pull: Pull Cloud Graph to Local
+# /upg-sync-pull: Pull Cloud Graph to Local
 
 You are a Unified Product Graph sync engine. Your job is to pull a product graph from The Product Creator cloud into a local `.upg` file, enabling offline work, git version control, and CLI-based graph operations. You support both full pulls and incremental sync.
 
@@ -48,7 +48,7 @@ The `.upg-sync` file tracks the sync state between local and cloud. It lives nex
 
 ## Key Principles
 
-- **Cloud to local, not cloud to local lock-in.** The `.upg` file is the user's; portable, open, git-tracked.
+- **Cloud to local is a real round-trip.** The pulled `.upg` file is the user's to edit and commit; nothing stays tied to the cloud.
 - **Preserve fidelity.** Every entity, every edge, every property should survive the round-trip.
 - **Incremental by default.** If a sync file exists, merge changes instead of overwriting.
 - **Handle conflicts transparently.** v1 uses last-write-wins (cloud takes precedence), but always tell the user when it happens.

package/skills/{upg-push → upg-sync-push}/SKILL-DETAIL.md

@@ -3,7 +3,7 @@ name: upg-push-detail
 description: "Detailed push flow, sync file format, ID mapping, edge cases"
 ---
 
-# /upg-push: Push Flow Detail
+# /upg-sync-push: Push Flow Detail
 
 ## First-Time Push (Step 4)
 
@@ -112,7 +112,7 @@ Nothing to push; your graph hasn't changed since last sync.
 
 Last synced: <last_synced_at from .upg-sync>
 
-Make changes locally, then run /upg-push again.
+Make changes locally, then run /upg-sync-push again.
 ```
 Stop here.
 
@@ -295,7 +295,7 @@ View your graph: cloud.unifiedproductgraph.org/p/<product_id>
 ### Keep Building Locally
 
 Your .upg file is still the source of truth for local work.
-Run /upg-push again anytime; only your changes will be synced.
+Run /upg-sync-push again anytime; only your changes will be synced.
 ```
 
 **After incremental push:**
@@ -317,11 +317,6 @@ View your graph: cloud.unifiedproductgraph.org/p/<product_id>
 ```
 
 **Shared footer (always append):**
-```
-┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄
-Your .upg file is yours: open standard, portable, git-friendly.
-unifiedproductgraph.org
-```
 
 ## The .upg-sync File
 
@@ -378,8 +373,7 @@ This is a large graph (<N> entities). Syncing in batches...
 Use pagination on `list_nodes` and batch creates (50 at a time).
 
 **Partial push failure:**
-If some batch creates succeed but others fail, report what succeeded and what failed. The `.upg-sync` file should still be updated with the mappings for entities that DID sync; don't throw away progress. Suggest retrying with `/upg-push` for the remaining entities.
+If some batch creates succeed but others fail, report what succeeded and what failed. The `.upg-sync` file should still be updated with the mappings for entities that DID sync; don't throw away progress. Suggest retrying with `/upg-sync-push` for the remaining entities.
 
 **Node type mapping:**
 Cloud uses the same entity types as local (`@unified-product-graph/core` shared ontology), so types map directly. Cloud stores type-specific data in a `data` JSONB column; map this from `properties` in the `.upg` format.
-