@pbhamri/quartermaster-mcp 0.7.0 → 0.8.0

package/README.md

@@ -40,7 +40,7 @@ Exposes **19 tools** over MCP stdio, organised by workflow:
 
 | Tool | Purpose |
 |---|---|
-| `qm_welcome` | First-run welcome + 3-step guide for new peers |
+| `qm_welcome` | First-run onboarding: a 4-stage guide (1. you + product, 2. skills, 3. connect ADO/GitHub/Kusto, 4. NPF + Connect goals) |
 | `qm_personalize` | Interactive Q&A → writes a personalised `connect-db.json`. Never inherits package author's data. |
 | `qm_skills_for_pm` | Curated daily-use catalog: Monday self-assess, midweek PRDs, Friday strategy, sharing |
 | `qm_init_profile` | **Create a custom product profile from scratch** — any product, any org. Generates a reusable `.json` profile with ADO/Kusto/IcM/GitHub connections. |
@@ -122,9 +122,12 @@ Reload your MCP client. Then: *"use quartermaster-mcp to seed this repo with pur
 ## Usage examples
 
 ```text
-# Onboarding (first time)
+# Onboarding (first time) — 4 stages, in order
 "Run qm_welcome."
-"Personalize my Quartermaster setup."
+# 1. Onboard you + product:  "Apply the purview-dlm profile."  (or "Create a new profile for my product.")
+# 2. See skills in detail:   "Run qm_skills_for_pm."
+# 3. Connect data sources:   "Help me wire up ADO / GitHub / Kusto."   (templates in resources/mcp-servers/)
+# 4. NPF + Connect goals:    "Personalize my Quartermaster setup."  then  "/npf"
 
 # Create YOUR product profile (not Purview? no problem)
 "Create a new profile for my product area."

package/bin/server.js

@@ -317,19 +317,52 @@ function qmWelcome() {
     server: "quartermaster-mcp",
     version: PKG.version,
     welcome: "Welcome to Quartermaster MCP — a PM paved-path bundle for Microsoft PMs.",
-    what_this_is: "12 MCP tools that scaffold a PM operating model: Purview product profiles, /npf and /cxe prompts, NPF assessment, BATON-style frameworks, and read-only access to your repo content.",
-    next_three_steps: hasConnectDb ? [
-      `1. Run \`qm_personalize\` to refresh your Connect tracker if needed (current: ${QM_CONNECT_DB}).`,
-      "2. Run `qm_skills_for_pm` to see the daily-use catalog for product roadmap + strategy.",
-      "3. Run `qm_seed_repo` to scaffold a target repo with the Quartermaster kit.",
-    ] : [
-      "1. Run `qm_personalize` — answers 5 questions, writes YOUR connect-db (uses ~/.quartermaster/connect-db.json by default; override via QM_CONNECT_DB env var). The package author's data is never used.",
-      `2. Run \`qm_apply_profile\` with one of the ${profiles.length} profiles: ${profiles.map(p => p.id).join(", ")}.`,
-      "3. Run `qm_skills_for_pm` to see the daily-use catalog for product roadmap + strategy.",
-    ],
+    what_this_is: `${TOOLS.length} MCP tools that set up your PM operating model: product profiles, PRD + strategy + roadmap + monitoring skills, data-source connectors (ADO / GitHub / Kusto / IcM), and — last — NPF alignment and Connect goals.`,
+    how_to_use_this: "Follow the four stages below IN ORDER. Your AI client runs each tool for you. Start at Stage 1 (who you are + your product). Do NOT start with goals — we deliberately get to NPF + Connect goals at the very end, once your product context and data sources are in place.",
+    onboarding_journey: {
+      "stage_1_onboard_you_and_your_product": {
+        goal: "Establish who you are, your product, and your focus areas — no goals yet.",
+        do: [
+          `Pick the product profile that fits you from the ${profiles.length} built in (${profiles.map(p => p.id).join(", ")}), then run \`qm_apply_profile\` with that profileId.`,
+          "No profile fits your product? Run `qm_init_profile` to create a custom one — it captures your personas, focus areas, KPIs, and directives for ANY product.",
+        ],
+        sets_up: "Your role, product, and focus areas (personas). These are inherited into every PRD, audit, and roadmap artefact later.",
+      },
+      "stage_2_see_your_skills_in_detail": {
+        goal: "Understand what Quartermaster does for you across PRDs, strategy, product roadmap, and monitoring.",
+        do: ["Run `qm_skills_for_pm` for the full catalog grouped by capability."],
+        skills_at_a_glance: {
+          "PRDs & specs": "`qm_seed_repo` scaffolds the IGRM compact PRD format; `/cxe` audits any PRD against the 4 CXE pillars; your profile's KPIs + directives auto-inherit into every PRD.",
+          "Strategy & performance": "`/npf` scores leverage x reach x cycle-time calibrated to your IC level; `qm_audit_repo` scores any repo /6 on PM-readiness for fast peer review.",
+          "Product roadmap & frameworks": "Profile directives become roadmap commitments; `repo_overview` / `repo_search` / `repo_read_file` pull roadmap artefacts into context with no copy-paste.",
+          "Monitoring & telemetry": "`qm_telemetry` reads paved-path adoption events (Reach signal); `repo_recent_sessions` recalls what shipped last week; pair with a connected Kusto MCP for live KPI pulls.",
+        },
+      },
+      "stage_3_connect_your_data_sources": {
+        goal: "Wire Quartermaster to YOUR ADO, GitHub, Kusto, and IcM.",
+        do: [
+          "Connector templates ship at `<package>/resources/mcp-servers/` : `ado.json`, `kusto.json`, `icm.json`, `workiq.json`, `playwright.json`.",
+          "Paste each into your MCP client config and fill the `{{PLACEHOLDERS}}` with your own org / project / cluster / service — full key map in `resources/mcp-servers/README.md`.",
+          "GitHub / repo read works immediately: run this server from inside your repo and use `repo_overview`, `repo_search`, `repo_read_file` (read-only; secrets denied at the server).",
+        ],
+        credentials_note: "Every credential and connection string stays on YOUR machine. Quartermaster ships only templates with placeholders — nothing is phoned home and the author's environment is never inherited.",
+      },
+      "stage_4_align_npf_and_connect_goals": {
+        goal: "Final step — calibrate performance and capture your Connect goals.",
+        do: [
+          `Run \`qm_personalize\` to capture your role, IC level, FY period, and 3-5 draft Connect goal titles. Writes YOUR connect-db at ${QM_CONNECT_DB} (override via QM_CONNECT_DB env var).`,
+          "Then run `/npf` in Copilot for your first NPF assessment, calibrated to the level you just set.",
+        ],
+        why_last: "NPF and Connect goals are only meaningful once your product profile and data sources are connected — so the assessment reflects real signal instead of an empty workspace.",
+        status: hasConnectDb
+          ? `You already have a connect-db at ${QM_CONNECT_DB}. Re-run \`qm_personalize\` only if you want to refresh it.`
+          : "No connect-db yet — this is where you create it, at the END of onboarding.",
+      },
+    },
     privacy_note: "Quartermaster ships templates only. Your Connect data, GitHub/Kusto/ADO credentials, and personal NPF history live on YOUR machine and are never committed to the package. The author's environment is not leaked to your install.",
     troubleshooting: {
       "Tools not visible after install": "Restart your MCP client (Copilot CLI: /restart; Claude Desktop: Cmd-Q + relaunch).",
+      "I want to skip straight to a stage": "Each stage is independent — call its tool directly. But Stage 4 (NPF + goals) is most useful after Stages 1-3.",
       "qm_personalize asks me questions but I want to skip": "Answer 'skip' to any question; you can re-run later. The template is also at <package>/resources/connect-db.template.json — copy and edit by hand.",
       "I want to see what files this server can read": "Call repo_overview — it returns the repo_root and exclusion list.",
     },
@@ -501,12 +534,59 @@ function qmInitProfile(args = {}) {
 }
 
 function qmSkillsForPm() {
-  // Curated catalog: 12 MCP tools mapped to PM daily-use cases.
-  // Optimised for product roadmap + strategy work.
+  // Curated catalog mapped to PM daily-use cases.
+  // Two views: by_capability (PRDs / strategy / roadmap / monitoring) and by workflow (day of week).
   return {
-    title: "Quartermaster — daily PM skills for roadmap + strategy",
-    intro: "12 tools, organised by PM workflow. Each tool name in backticks is callable as `<tool_name>` from your MCP client.",
-    workflows: [
+    title: "Quartermaster — PM skills in detail",
+    intro: `${TOOLS.length} tools + 2 prompts, organised by capability first, then by weekly workflow. Each name in backticks is callable as \`<tool_name>\` from your MCP client; \`/npf\` and \`/cxe\` are Copilot prompts.`,
+    by_capability: [
+      {
+        capability: "PRDs & specs",
+        what_you_can_do: "Author leadership-ready PRDs and executive specs that inherit your product's KPIs and pass a CXE review before you ship them.",
+        tools: [
+          { name: "qm_seed_repo", use: "Scaffold a repo with the IGRM compact 1-2 page PRD format, /cxe + /npf prompts, and a command-center seed. Idempotent — safe to re-run." },
+          { name: "qm_apply_profile", use: "Lock in your product profile so every PRD inherits your personas, KPIs, and manager directives instead of starting blank." },
+          { name: "/cxe (prompt)", use: "Audit any PRD or work item against the 4 CXE pillars — Customer priority, Time-to-value, Confidence, Support — before review." },
+        ],
+      },
+      {
+        capability: "Strategy & performance",
+        what_you_can_do: "Pressure-test your strategy and measure your own leverage with an IC-level-calibrated performance lens.",
+        tools: [
+          { name: "/npf (prompt)", use: "30-second NPF score (leverage x reach x cycle-time) + biggest gap + next move, calibrated to your IC level." },
+          { name: "qm_audit_repo", use: "Score any repo /6 on PM-readiness (AGENTS.md, copilot-instructions, profile, /npf, /cxe, verify.ps1). Fast peer review." },
+        ],
+      },
+      {
+        capability: "Product roadmap & frameworks",
+        what_you_can_do: "Turn manager directives into tracked roadmap commitments and pull roadmap artefacts into context without copy-paste.",
+        tools: [
+          { name: "qm_apply_profile / qm_init_profile", use: "Profile directives + KPIs become your roadmap's measurable commitments; qm_init_profile builds a custom profile for any product." },
+          { name: "repo_overview / repo_list_dir / repo_read_file / repo_search", use: "Read-only access to your repo artefacts (roadmaps, PRDs, command-center) so the AI can assemble readouts. Secrets denied at the server." },
+        ],
+      },
+      {
+        capability: "Monitoring & telemetry",
+        what_you_can_do: "See whether your paved paths are being adopted (Reach) and recall what shipped, then feed that signal back into NPF.",
+        tools: [
+          { name: "qm_telemetry", use: "Read paved-path adoption events from the JSONL log; the Reach signal for your next /npf." },
+          { name: "qm_report_adoption", use: "Opt-in: send an anonymous adoption ping (machine hash + counts + version) so a paved-path owner can measure reach. No PII." },
+          { name: "repo_recent_sessions", use: "Read your cross-model session log to recall what shipped last week without re-explaining." },
+          { name: "Kusto KPI pulls", use: "Pair with a connected Kusto MCP (Stage 3 connector template) to pull live product KPIs into the same workflow." },
+        ],
+      },
+      {
+        capability: "Onboarding & sharing",
+        what_you_can_do: "Bring a peer PM onto the same paved path in minutes.",
+        tools: [
+          { name: "qm_welcome", use: "The 4-stage first-run guide. Surface this to any new peer." },
+          { name: "qm_personalize", use: "Walk a peer through role / level / FY / goal questions and write THEIR connect-db. Their data, their machine." },
+          { name: "qm_install_prompts", use: "Drop /npf + /cxe into a peer's ~/.github/prompts so the prompts work in Copilot Chat (IDE) too." },
+          { name: "qm_skills_for_pm", use: "This catalog. Run any time you forget what's available." },
+        ],
+      },
+    ],
+    by_workflow: [
       {
         scenario: "Monday — Weekly self-assessment + planning",
         tools: [
@@ -531,15 +611,6 @@ function qmSkillsForPm() {
           { name: "qm_emit_pr", use: "Seed a repo with a profile AND open a labeled PR via gh CLI — closes the loop on cross-team commitments in one call." },
         ],
       },
-      {
-        scenario: "Onboarding + sharing with peer PMs",
-        tools: [
-          { name: "qm_welcome", use: "First-run guide. Surface this to any new peer." },
-          { name: "qm_personalize", use: "Walk a peer through 5 questions, write THEIR connect-db. Their data, their machine, never the package author's." },
-          { name: "qm_install_prompts", use: "Drop /npf + /cxe into a peer's ~/.github/prompts so the prompts work in Copilot Chat (IDE) too." },
-          { name: "qm_skills_for_pm", use: "This catalog. Run any time you forget what's available." },
-        ],
-      },
     ],
     daily_loop: [
       "1. Mon 09:00 — `/npf` for the week's score + gap.",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pbhamri/quartermaster-mcp",
-  "version": "0.7.0",
+  "version": "0.8.0",
   "description": "MCP server that seeds any repo with a customizable PM kit. Any PM, any product — connect YOUR GitHub, ADO, Kusto, IcM. 19 tools: scaffolding, repo-read, onboarding, custom profile creation, self-agent auto-reply. Never ships personal data — profiles are templates you fill in.",
   "type": "module",
   "bin": {