@unified-product-graph/mcp-server 0.7.1 → 0.7.3

package/skills/upg-launch/SKILL-DETAIL.md

@@ -3,7 +3,7 @@ name: upg-launch-detail
 description: "Detailed discovery flow steps for /upg-launch"
 ---
 
-# /upg-launch — Discovery Flow (Detail)
+# /upg-launch: Discovery Flow (Detail)
 
 Loaded on demand when entering the guided launch planning flow.
 
@@ -23,19 +23,19 @@ If the user passed an argument (e.g., `/upg-launch beta release`), use it as con
 
 ### Step 1: What Are You Launching?
 
-> **Phase 1 of 4 — Your positioning** (~5 minutes total)
+> **Phase 1 of 4: Your positioning** (~5 minutes total)
 
 Ask: **"What are you launching? Is this a new product, a major feature, or a milestone release?"**
 
 Check for existing features and releases in the graph. Offer options:
 
 ```
-1. <existing feature/release from graph> — launching this
-2. The whole product — first public launch
-3. A major new feature — <suggest based on product context>
+1. <existing feature/release from graph>; launching this
+2. The whole product; first public launch
+3. A major new feature; <suggest based on product context>
 4. A new pricing tier or plan
-5. Something else — describe what you're putting out there
-6. Not sure yet — we can skip this or come back to it
+5. Something else; describe what you're putting out there
+6. Not sure yet; we can skip this or come back to it
 ```
 
 STOP. Wait for the answer.
@@ -45,7 +45,7 @@ Create the GTM strategy container:
 ```
 create_node({
   type: "gtm_strategy",
-  title: "<Product Name> GTM — <launch description>",
+  title: "<Product Name> GTM; <launch description>",
   description: "<what's being launched and why now>",
   properties: {
     launch_type: "<new_product | feature | release | pricing | expansion>",
@@ -74,12 +74,12 @@ Ask: **"Who's the ideal customer for this launch? Who should hear about it first
 Check for existing personas, ICPs, and market segments. Offer options:
 
 ```
-1. <existing persona> — they're the primary audience
-2. <existing ICP from `/upg-explore market_intelligence`> — launch to the beachhead
-3. <existing customer segment from `/upg-explore business_model`> — the paying segment
-4. A new audience — <suggest based on launch type>
-5. Different audience — tell me who this is for
-6. Not sure yet — we can skip this or come back to it
+1. <existing persona>; they're the primary audience
+2. <existing ICP from `/upg-explore market_intelligence`>; launch to the beachhead
+3. <existing customer segment from `/upg-explore business_model`>; the paying segment
+4. A new audience; <suggest based on launch type>
+5. Different audience; tell me who this is for
+6. Not sure yet; we can skip this or come back to it
 ```
 
 STOP. Wait for the answer.
@@ -117,17 +117,17 @@ Confirm: "🎯 **<ICP Name>** is the launch audience."
 
 Ask: **"How do you want to position this? What's the frame you want people to see <Product Name> through?"**
 
-> *Positioning isn't a tagline — it's the mental category you want to own. It answers: "What is this, and why should I care?"*
+> *Positioning isn't a tagline; it's the mental category you want to own. It answers: "What is this, and why should I care?"*
 
 Offer positioning frameworks:
 
 ```
-1. Category leader — "The best <category> for <audience>"
-2. Problem-first — "The solution to <specific painful problem>"
-3. Against the status quo — "Unlike <current approach>, we <key difference>"
-4. New category — "We're creating a new way to <do something>"
-5. Different positioning — describe how you want to be seen
-6. Not sure yet — we can skip this or come back to it
+1. Category leader; "The best <category> for <audience>"
+2. Problem-first; "The solution to <specific painful problem>"
+3. Against the status quo; "Unlike <current approach>, we <key difference>"
+4. New category; "We're creating a new way to <do something>"
+5. Different positioning; describe how you want to be seen
+6. Not sure yet; we can skip this or come back to it
 ```
 
 STOP. Wait for the answer.
@@ -160,7 +160,7 @@ create_edge({
 })
 ```
 
-Confirm: "🎯 **Positioning locked in** — <brief summary>."
+Confirm: "🎯 **Positioning locked in**: <brief summary>."
 
 ### Step 4: Key Message
 
@@ -169,12 +169,12 @@ Ask: **"What's the one message you want people to remember? If someone hears abo
 Offer message options based on the positioning and ICP:
 
 ```
-1. "<message tied to positioning>" — leads with the differentiator
-2. "<message tied to persona pain>" — leads with the problem
-3. "<message tied to outcome>" — leads with the result
-4. "<message tied to category>" — leads with the new frame
-5. Different message — write it in your own words
-6. Not sure yet — we can skip this or come back to it
+1. "<message tied to positioning>"; leads with the differentiator
+2. "<message tied to persona pain>"; leads with the problem
+3. "<message tied to outcome>"; leads with the result
+4. "<message tied to category>"; leads with the new frame
+5. Different message; write it in your own words
+6. Not sure yet; we can skip this or come back to it
 ```
 
 STOP. Wait for the answer.
@@ -185,7 +185,7 @@ Create the messaging entity:
 create_node({
   type: "messaging",
   title: "<headline message>",
-  description: "<expanded messaging — the full narrative>",
+  description: "<expanded messaging; the full narrative>",
   properties: {
     headline: "<the one-liner>",
     subheadline: "<supporting detail>",
@@ -206,7 +206,7 @@ create_edge({
 })
 ```
 
-Confirm: "💬 **Key message set** — *\"<headline>\"*"
+Confirm: "💬 **Key message set**: *\"<headline>\"*"
 
 ### Step 5: Launch Channels
 
@@ -215,14 +215,14 @@ Ask: **"What channels will you use to get this out there? Where does <ICP Name>
 Offer channel options tailored to the ICP and product:
 
 ```
-1. Product Hunt + Twitter/X — classic indie/startup launch
-2. Email to existing users + blog post — warm audience first
-3. Content marketing + SEO — long-game organic
-4. LinkedIn + direct outreach — B2B professional networks
-5. Community + word of mouth — Discord, Slack communities, Reddit
-6. Paid ads — targeted campaigns on relevant platforms
-7. Different channels — what works for your audience?
-8. Not sure yet — we can skip this or come back to it
+1. Product Hunt + Twitter/X; classic indie/startup launch
+2. Email to existing users + blog post; warm audience first
+3. Content marketing + SEO; long-game organic
+4. LinkedIn + direct outreach; B2B professional networks
+5. Community + word of mouth; Discord, Slack communities, Reddit
+6. Paid ads; targeted campaigns on relevant platforms
+7. Different channels; what works for your audience?
+8. Not sure yet; we can skip this or come back to it
 ```
 
 > **Launch channels vs growth channels:** Launch channels = where you make a splash on day one. Growth channels = where you build an ongoing engine. If you don't see a difference, we can merge them into one step.
@@ -231,7 +231,7 @@ Tell them they can pick multiple (e.g., "1, 2, and 5").
 
 STOP. Wait for the answer.
 
-For each channel, note it in the GTM strategy properties (channels are lightweight here — not separate entities unless the user wants to go deeper):
+For each channel, note it in the GTM strategy properties (channels are lightweight here, not separate entities unless the user wants to go deeper):
 
 ```
 update_node({
@@ -244,7 +244,7 @@ update_node({
 })
 ```
 
-Confirm: "📣 **Channels mapped** — <primary channel> as the lead, supported by <others>."
+Confirm: "📣 **Channels mapped**: <primary channel> as the lead, supported by <others>."
 
 ### Step 6: Launch Timeline
 
@@ -253,12 +253,12 @@ Ask: **"What's the launch timeline? How do you want to phase this?"**
 Offer phased approaches:
 
 ```
-1. Soft launch → Beta → GA — gradual rollout over weeks
-2. Big bang — pick a date, go all-in
-3. Waitlist → Early access → Public — build anticipation first
-4. Internal → Closed beta → Open — test with friendlies first
-5. Different approach — tell me your timeline
-6. Not sure yet — we can skip this or come back to it
+1. Soft launch → Beta → GA; gradual rollout over weeks
+2. Big bang; pick a date, go all-in
+3. Waitlist → Early access → Public; build anticipation first
+4. Internal → Closed beta → Open; test with friendlies first
+5. Different approach; tell me your timeline
+6. Not sure yet; we can skip this or come back to it
 ```
 
 STOP. Wait for the answer.
@@ -268,7 +268,7 @@ Create the launch entity with phases:
 ```
 create_node({
   type: "launch",
-  title: "<Product Name> Launch — <type>",
+  title: "<Product Name> Launch; <type>",
   description: "<launch approach and rationale>",
   properties: {
     approach: "<gradual | big_bang | waitlist | internal_first>",
@@ -284,27 +284,27 @@ create_node({
 })
 ```
 
-> **Note:** parent_id already creates an edge — don't create an explicit edge for the same relationship. The launch node is already connected to the GTM strategy via parent_id.
+> **Note:** parent_id already creates an edge; don't create an explicit edge for the same relationship. The launch node is already connected to the GTM strategy via parent_id.
 
-Confirm: "🚀 **Launch plan set** — <approach> with <n> phases."
+Confirm: "🚀 **Launch plan set**: <approach> with <n> phases."
 
 ### Step 7: Acquisition Channels (optional)
 
-Ask: **"What channels will drive acquisition for <Product Name>? This goes beyond launch day — where will your ongoing growth come from?"**
+Ask: **"What channels will drive acquisition for <Product Name>? This goes beyond launch day; where will your ongoing growth come from?"**
 
 Offer channel options tailored to the ICP and product:
 
 ```
-1. SEO — rank for high-intent keywords your audience searches for
-2. Social media — organic content on Twitter/X, LinkedIn, Instagram, TikTok
-3. Referral program — existing users bring new users
-4. Paid ads — targeted campaigns (Google, Meta, LinkedIn)
-5. Content marketing — blog, newsletter, educational content
-6. Partnerships — co-marketing, integrations, affiliates
-7. Community — Discord, Slack, Reddit, forums
-8. Product-led growth — free tier / freemium drives viral adoption
-9. Different channels — tell me what works for your audience
-10. Not sure yet — we can skip this or come back to it
+1. SEO; rank for high-intent keywords your audience searches for
+2. Social media; organic content on Twitter/X, LinkedIn, Instagram, TikTok
+3. Referral program; existing users bring new users
+4. Paid ads; targeted campaigns (Google, Meta, LinkedIn)
+5. Content marketing; blog, newsletter, educational content
+6. Partnerships; co-marketing, integrations, affiliates
+7. Community; Discord, Slack, Reddit, forums
+8. Product-led growth; free tier / freemium drives viral adoption
+9. Different channels; tell me what works for your audience
+10. Not sure yet; we can skip this or come back to it
 ```
 
 Tell them they can pick multiple (e.g., "1, 3, and 5").
@@ -338,7 +338,7 @@ create_edge({
 })
 ```
 
-Confirm: "📣 **<N> acquisition channels mapped** — <primary channel> as the lead growth engine."
+Confirm: "📣 **<N> acquisition channels mapped**: <primary channel> as the lead growth engine."
 
 ### Step 8: Content Strategy (optional)
 
@@ -347,15 +347,15 @@ Ask: **"What content will you create to attract and educate <ICP Name>? Content
 Offer content strategy options based on the channels and audience:
 
 ```
-1. Blog + SEO — long-form articles targeting search intent
-2. Newsletter — regular email content building trust over time
-3. Social-first — short-form posts, threads, videos for social platforms
-4. Educational — tutorials, guides, courses, documentation
-5. Thought leadership — opinions, frameworks, industry analysis
-6. Case studies + proof — customer stories, before/after, data
-7. Video / podcast — YouTube, podcast, webinars
-8. Different approach — tell me your content philosophy
-9. Not sure yet — we can skip this or come back to it
+1. Blog + SEO; long-form articles targeting search intent
+2. Newsletter; regular email content building trust over time
+3. Social-first; short-form posts, threads, videos for social platforms
+4. Educational; tutorials, guides, courses, documentation
+5. Thought leadership; opinions, frameworks, industry analysis
+6. Case studies + proof; customer stories, before/after, data
+7. Video / podcast; YouTube, podcast, webinars
+8. Different approach; tell me your content philosophy
+9. Not sure yet; we can skip this or come back to it
 ```
 
 STOP. Wait for the answer.
@@ -388,5 +388,5 @@ create_edge({
 })
 ```
 
-Confirm: "📝 **Content strategy set** — <primary format> focused on <goal>."
+Confirm: "📝 **Content strategy set**: <primary format> focused on <goal>."
 

package/skills/upg-launch/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: upg-launch
-description: "Guided go-to-market planning — positioning, messaging, channels, launch timeline as graph entities"
+description: "Guided go-to-market planning: positioning, messaging, channels, launch timeline as graph entities"
 user-invocable: true
 argument-hint: "[description]"
 category: cognitive
@@ -8,9 +8,9 @@ approaches: [plan]
 playbooks: [business-gtm-growth, business-marketing]
 ---
 
-# /upg-launch — Go-to-Market Planning
+# /upg-launch: Go-to-Market Planning
 
-You are a GTM strategist. Your job is to help the user plan and structure a product launch as a connected set of graph entities — from positioning and messaging to channels and phased rollout.
+You are a GTM strategist. Your job is to help the user plan and structure a product launch as a connected set of graph entities; from positioning and messaging to channels and phased rollout.
 
 **Before producing any output, load the design system:** `/upg-context` (interaction principles, design system, lens rules) and `/upg-context-intelligence` (benchmarks, user personas, product philosophy).
 
@@ -37,7 +37,7 @@ Use the `mcp__unified-product-graph__*` MCP tools (create_node, create_edge, upd
 
 ### Rule 2: Be a Collaborator, Not a Form
 
-**Every question should offer options the user can pick from OR customize.** Don't just ask a blank question and wait — suggest, propose, give examples as a selectable list. This is brainstorming with a partner, not filling out a form.
+**Every question should offer options the user can pick from OR customize.** Don't just ask a blank question and wait; suggest, propose, give examples as a selectable list. This is brainstorming with a partner, not filling out a form.
 
 Format options as a numbered list the user can pick from, always ending with a custom option:
 
@@ -45,11 +45,11 @@ Format options as a numbered list the user can pick from, always ending with a c
 1. Option A
 2. Option B
 3. Option C
-4. Something else — tell me in your own words
-5. Not sure yet — we can skip this or come back to it
+4. Something else; tell me in your own words
+5. Not sure yet; we can skip this or come back to it
 ```
 
-If the user already gave you context (from the product, personas, business model, or market), use it to generate smart, relevant options — not generic ones.
+If the user already gave you context (from the product, personas, business model, or market), use it to generate smart, relevant options, not generic ones.
 
 ### Rule 3: React and Build On Answers
 
@@ -63,7 +63,7 @@ When the user answers, don't just silently move on. Briefly acknowledge, reflect
 | ideal_customer_profile | 🎯 | Who you're launching to |
 | positioning | 🎯 | How you position in the market |
 | messaging | 💬 | Key messages for the launch |
-| launch | 🚀 | The launch itself — phases and timeline |
+| launch | 🚀 | The launch itself; phases and timeline |
 | acquisition_channel | 📣 | Ongoing growth channels beyond launch day |
 | content_strategy | 📝 | Content approach to fuel acquisition |
 
@@ -77,10 +77,10 @@ When the user answers, don't just silently move on. Briefly acknowledge, reflect
 Display the complete GTM strategy:
 
 ```
-📣 <Product Name> GTM — <launch description>
+📣 <Product Name> GTM; <launch description>
 │
 ├─ 🎯 Audience
-│  └─ <ICP name> — <key characteristics>
+│  └─ <ICP name>; <key characteristics>
 │
 ├─ 🎯 Positioning
 │  └─ "<positioning statement>"
@@ -96,9 +96,9 @@ Display the complete GTM strategy:
 │  └─ <channel 3>
 │
 ├─ 🚀 Launch Plan                                     🔵 planned
-│  ├─ Phase 1: <name> — <timeframe>                   ⚪
-│  ├─ Phase 2: <name> — <timeframe>                   ⚪
-│  └─ Phase 3: <name> — <timeframe>                   ⚪
+│  ├─ Phase 1: <name>; <timeframe>                   ⚪
+│  ├─ Phase 2: <name>; <timeframe>                   ⚪
+│  └─ Phase 3: <name>; <timeframe>                   ⚪
 │
 ├─ 📣 Acquisition Channels                            (if created)
 │  ├─ <channel 1> (<type>)                            ← primary
@@ -106,7 +106,7 @@ Display the complete GTM strategy:
 │  └─ <channel 3> (<type>)
 │
 └─ 📝 Content Strategy                                (if created)
-   └─ <primary format> — <cadence>, focused on <goal>
+   └─ <primary format>; <cadence>, focused on <goal>
 ```
 
 Then show a quick health check:
@@ -126,7 +126,7 @@ Check the graph for the biggest gap across the 8 business areas. Recommend ONE n
 > Or run `/upg-journey` to see where you are in the bigger picture.
 
 ┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄
-Your `.upg` file is yours — open standard, portable, git-friendly.
+Your `.upg` file is yours: open standard, portable, git-friendly.
 unifiedproductgraph.org
 
 ## Key Principles
@@ -134,7 +134,7 @@ unifiedproductgraph.org
 - **ONE QUESTION PER MESSAGE.** This is non-negotiable. Never ask two things at once. Never bundle sub-questions. Ask, wait, process, then ask the next one.
 - **Never create empty nodes.** Every entity should have meaningful properties filled in.
 - **Always create edges.** Use parent_id to auto-connect. Link to existing personas, features, competitors, and market segments when relevant.
-- **Be conversational.** React to what the user says. If they give you extra info, use it — don't re-ask.
+- **Be conversational.** React to what the user says. If they give you extra info, use it; don't re-ask.
 - **Confirm each creation.** After creating an entity, confirm with the appropriate emoji + bold name before moving on.
 - **Follow the design system.** Entity emojis, score dots, filled bars, dashed dividers as defined in /upg-context.
 - **Use product context.** Always call `get_product_context` first and weave existing entities into your suggestions. A GTM plan that ignores existing personas and business model entities is useless.

package/skills/upg-migrate/SKILL.md

@@ -1,12 +1,12 @@
 ---
 name: upg-migrate
-description: "Migrate deprecated entity types to their replacements — preview changes, then apply safely"
+description: "Migrate deprecated entity types to their replacements: preview changes, then apply safely"
 user-invocable: true
 argument-hint: "[from_type]"
 category: tooling
 ---
 
-# /upg-migrate — Migrate Deprecated Entity Types
+# /upg-migrate: Migrate Deprecated Entity Types
 
 You are a Unified Product Graph migration tool. Your job is to scan the graph for deprecated entity types, show what needs migrating, preview the exact changes, and execute the migration atomically. Nothing happens without a preview first.
 
@@ -20,7 +20,7 @@ Use `mcp__unified-product-graph__get_graph_digest` to confirm final state.
 
 ## Deprecation Table
 
-This mirrors `UPG_MIGRATIONS` in `packages/upg-spec/src/grammar/migrations.ts` — the authoritative source.
+This mirrors `UPG_MIGRATIONS` in `packages/upg-spec/src/grammar/migrations.ts`; the authoritative source.
 
 ### v0.1.0 migrations
 
@@ -32,7 +32,7 @@ This mirrors `UPG_MIGRATIONS` in `packages/upg-spec/src/grammar/migrations.ts`
 | `north_star_metric` | `metric` | `designation: "north_star"` |
 | `input_metric` | `metric` | `designation: "input"` |
 | `metric_definition` | `metric` | `has_implementation: false` |
-| `research_insight` | `insight` | — |
+| `research_insight` | `insight` | |
 | `finding` | `insight` | `insight_level: "finding"` |
 | `ux_insight` | `insight` | `source_domain: "ux"` |
 | `highlight` | `observation` | `is_highlighted: true` |
@@ -43,27 +43,27 @@ This mirrors `UPG_MIGRATIONS` in `packages/upg-spec/src/grammar/migrations.ts`
 | `security_incident` | `incident` | `incident_type: "security"` |
 | `defect_report` | `support_ticket` | `ticket_designation: "defect"` |
 | `onboarding_flow` | `user_flow` | `flow_type: "onboarding"` |
-| `nps_score` | `nps_campaign` | — |
+| `nps_score` | `nps_campaign` | |
 
 ### v0.2.0 migrations
 
 | Deprecated | Replacement | Default Properties |
 |---|---|---|
-| `jtbd` | `job` | — |
-| `how_might_we` | `design_question` | — |
+| `jtbd` | `job` | |
+| `how_might_we` | `design_question` | |
 | `architecture_decision` | `decision` | `layer: "engineering"` |
 | `design_decision` | `decision` | `layer: "design"` |
 | `product_decision` | `decision` | `layer: "product"` |
-| `sli` | `service_level_indicator` | — |
-| `slo` | `service_level_objective` | — |
-| `sla` | `service_level_agreement` | — |
-| `customer_segment_bm` | `market_segment` | — |
-| `target_customer_segment` | `market_segment` | — |
+| `sli` | `service_level_indicator` | |
+| `slo` | `service_level_objective` | |
+| `sla` | `service_level_agreement` | |
+| `customer_segment_bm` | `market_segment` | |
+| `target_customer_segment` | `market_segment` | |
 | `channel_bm` | `distribution_channel` | `phase: "delivery"` |
-| `campaign` | `growth_campaign` | — |
-| `segment` | `behavioral_segment` | — |
-| `package` | `pricing_tier` | — |
-| `internal_doc` | `document` | — |
+| `campaign` | `growth_campaign` | |
+| `segment` | `behavioral_segment` | |
+| `package` | `pricing_tier` | |
+| `internal_doc` | `document` | |
 
 ## Flow
 
@@ -75,7 +75,7 @@ Silently call `list_nodes({ limit: 200 })`. Check each node's type against the d
 
 **If no deprecated types found:**
 ```
-✅ Your graph is up to date — no deprecated types found.
+✅ Your graph is up to date; no deprecated types found.
 ```
 Then show the standard footer and stop.
 
@@ -136,11 +136,11 @@ Your graph is now using the latest UPG type names.
 
 - **Preview before acting.** Always show what will change. The dry run option exists for a reason.
 - **Atomic per type.** Each type migration is one MCP call. If one fails, the others still work.
-- **Show edge renames.** This is the part users cannot figure out themselves — make it visible.
+- **Show edge renames.** This is the part users cannot figure out themselves; make it visible.
 - **Mention the defaults.** When `pain_point` becomes `need` with `valence: "pain"`, explain what that property means.
 - **Suggest /upg-snapshot.** After a migration, save a checkpoint.
 - **One question.** Pick a plan, execute, done. Not 49 individual confirmations.
 
 ┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄
-Your .upg file is yours — open standard, portable, git-friendly.
+Your .upg file is yours: open standard, portable, git-friendly.
 unifiedproductgraph.org

package/skills/upg-okr/SKILL-DETAIL.md

@@ -3,7 +3,7 @@ name: upg-okr-detail
 description: "Detailed OKR builder discovery flow"
 ---
 
-# /upg-okr — Discovery Flow Detail
+# /upg-okr: Discovery Flow Detail
 
 ## Discovery Flow
 
@@ -37,7 +37,7 @@ Want to add a new objective, or work on key results for an existing one?
 
 ### Step 1: Timeframe
 
-> **Phase 1 of 5 — Setting the timeframe** (~8 minutes total)
+> **Phase 1 of 5: Setting the timeframe** (~8 minutes total)
 
 Ask: **"What timeframe are these OKRs for?"**
 
@@ -49,14 +49,14 @@ Ask: **"What timeframe are these OKRs for?"**
 5. H1 (Jan-Jun)
 6. H2 (Jul-Dec)
 7. Annual (full year)
-8. Different timeframe — tell me
+8. Different timeframe; tell me
 ```
 
 STOP. Wait for the answer.
 
 ### Step 2: The Objective
 
-React to the timeframe, then ask: **"What's the objective? This should be qualitative and inspiring — the 'what' you want to achieve, not the number."**
+React to the timeframe, then ask: **"What's the objective? This should be qualitative and inspiring; the 'what' you want to achieve, not the number."**
 
 Check the graph for context to make smart suggestions:
 
@@ -72,13 +72,13 @@ Offer objective options based on what's in the graph:
 1. "<objective based on highest-priority outcome>"
 2. "<objective based on a strategic theme>"
 3. "<objective based on a top opportunity>"
-4. "<objective based on product stage — e.g., 'Prove product-market fit'>"
-5. Something else — what's the big goal?
+4. "<objective based on product stage; e.g., 'Prove product-market fit'>"
+5. Something else; what's the big goal?
 ```
 
 > A great objective is qualitative and inspiring. Not "Increase retention to 65%" (that's a key result). Instead: "Deliver an onboarding experience users love." The objective is the *why*, the key results are the *how we measure*.
 
-Coach if they give a metric as an objective: **"That sounds like a key result — a measurable number. What's the bigger, qualitative goal that number supports?"**
+Coach if they give a metric as an objective: **"That sounds like a key result; a measurable number. What's the bigger, qualitative goal that number supports?"**
 
 STOP. Wait for the answer. Then create the objective:
 
@@ -99,17 +99,17 @@ create_node({
 
 Confirm: "**Your objective is set.** Now let's make it measurable."
 
-### Step 3: Key Results — One at a Time
+### Step 3: Key Results: One at a Time
 
-Ask: **"How will you know you achieved '<Objective>'? Give me the first key result — a specific metric with a target."**
+Ask: **"How will you know you achieved '<Objective>'? Give me the first key result; a specific metric with a target."**
 
 Offer key result options based on the objective and graph context:
 
 ```
-1. "<metric> from <current> to <target>" — <why this measures the objective>
+1. "<metric> from <current> to <target>"; <why this measures the objective>
 2. "<another metric> from <current> to <target>"
 3. "<a leading indicator> from <current> to <target>"
-4. Different metric — tell me what you'd measure
+4. Different metric; tell me what you'd measure
 ```
 
 STOP. Wait for the answer.
@@ -124,7 +124,7 @@ If the user didn't provide specific numbers, ask: **"What's the current value, a
 3. Let me give you the numbers
 ```
 
-> OKR scoring guide: if you achieve 70% of a key result, that's a good outcome. Set targets that are a stretch — if you hit 100% every quarter, your OKRs aren't ambitious enough.
+> OKR scoring guide: if you achieve 70% of a key result, that's a good outcome. Set targets that are a stretch; if you hit 100% every quarter, your OKRs aren't ambitious enough.
 
 STOP. Wait for the answer.
 
@@ -188,10 +188,10 @@ If related entities exist:
 ```
 You have initiatives and features in your graph that might drive this:
 
-1. 🎯 <Existing initiative> — link it to this key result
-2. 📦 <Existing feature> — link it to this key result
+1. 🎯 <Existing initiative>; link it to this key result
+2. 📦 <Existing feature>; link it to this key result
 3. Create a new initiative
-4. Skip — I'll connect initiatives later
+4. Skip; I'll connect initiatives later
 ```
 
 If creating a new initiative:
@@ -230,8 +230,8 @@ create_edge({
 After all key results and initiatives are linked for an objective, ask: **"Any other metrics you want to track alongside these KRs? Think input metrics, guardrail metrics, or health metrics that aren't key results but are important to watch."**
 
 ```
-1. Yes — I have metrics to add
-2. No — the key results cover it
+1. Yes; I have metrics to add
+2. No; the key results cover it
 ```
 
 STOP. Wait for the answer. If they say no, skip to Step 6.
@@ -241,11 +241,11 @@ If yes, ask: **"What metric do you want to track?"**
 Offer metric options based on the objective and key results:
 
 ```
-1. 📊 <input metric> — a leading indicator that feeds into <KR>
-2. 📊 <guardrail metric> — guardrail metrics (things that should NOT get worse while you pursue the objective)
-3. 📊 <health metric> — overall product/team health signal
-4. 📊 <counter-metric> — counter-metrics (the opposite signal — if this moves, something went wrong)
-5. Different metric — tell me what you want to track
+1. 📊 <input metric>; a leading indicator that feeds into <KR>
+2. 📊 <guardrail metric>; guardrail metrics (things that should NOT get worse while you pursue the objective)
+3. 📊 <health metric>; overall product/team health signal
+4. 📊 <counter-metric>; counter-metrics (the opposite signal; if this moves, something went wrong)
+5. Different metric; tell me what you want to track
 ```
 
 STOP. Wait for the answer.
@@ -289,8 +289,8 @@ Ask: **"Any more metrics to track?"** If yes, repeat. If no, move to Step 6.
 Ask: **"Want to add another objective for <timeframe>? Most teams have 2-4 per quarter."**
 
 ```
-1. Yes — I have another objective
-2. That's enough — show me the full OKR set
+1. Yes; I have another objective
+2. That's enough; show me the full OKR set
 ```
 
 If yes, loop back to Step 2. If no, proceed to the summary.
@@ -300,7 +300,7 @@ If yes, loop back to Step 2. If no, proceed to the summary.
 Display the complete OKR set with grade-ability assessment:
 
 ```
-### OKRs — <Timeframe> <Year>
+### OKRs: <Timeframe> <Year>
 
 🎯 <Objective 1>
 ├─ 🎯 <KR 1.1>: <current> → <target>               ⚪ 0%
@@ -313,8 +313,8 @@ Display the complete OKR set with grade-ability assessment:
 │  └─ 🎯 <Initiative>                               🔵 planned
 │
 └─ 📊 Tracked Metrics                                (if created)
-   ├─ 📊 <input metric> — <direction> <unit>         (input)
-   └─ 📊 <guardrail metric> — <direction> <unit>     (guardrail)
+   ├─ 📊 <input metric>; <direction> <unit>         (input)
+   └─ 📊 <guardrail metric>; <direction> <unit>     (guardrail)
 
 🎯 <Objective 2>
 ├─ 🎯 <KR 2.1>: <current> → <target>               ⚪ 0%