@plainconceptsplatform/agent-harness 2.2.1 → 2.4.0

package/{src/content → harness}/.agents/skills/pc-userstory-browser/SKILL.md

@@ -1,132 +1,136 @@
----
-name: pc-userstory
-description: Parse work item from any URL using browser automation. Use when user provides a URL that doesn't match GitHub/Azure/Jira CLI platforms, or when backlog platform is 'browser'.
-license: MIT
-compatibility: Requires opencode-browser extension and openspec CLI.
-metadata:
-  author: copilots
-  version: "1.0"
----
-
-This skill is used when the backlog platform is set to "Others (Browser)": when there is no CLI integration for the backlog system, or the user doesn't have API tokens. Work items are read directly from the web page using the opencode-browser plugin.
-
-This skill overrides the `browser-automation` skill's external navigation restriction, but only for URLs the user explicitly provides as work items. Navigate only to URLs the user gives you.
-
-## Prerequisites
-
-- opencode-browser extension installed and running (installed during onboarding)
-- The user must be authenticated to the backlog system in their browser (e.g. logged into Azure DevOps, Jira, Trello, Linear, etc.)
-
-## Steps
-
-1. **Extract the URL** from the user's message
-   - The user provides a direct URL to a work item, issue, ticket, or PBI
-   - Examples: `https://dev.azure.com/org/project/_workitems/edit/123`, `https://linear.app/team/issue/ENG-123`, `https://trello.com/c/abc123`, `https://your-tool.com/ticket/456`
-
-2. **Navigate to the URL**
-   ```bash
-   browser_open_tab url="https://the-url-the-user-provided"
-   ```
-
-3. **Wait for the page to load**
-   ```bash
-   browser_wait ms=3000
-   ```
-
-4. **Read the work item content**
-   ```bash
-   browser_query mode="page_text"
-   ```
-
-   Also try to get structured content:
-   ```bash
-   browser_snapshot
-   ```
-   The accessibility snapshot often reveals the work item title, description, and fields more precisely than raw page text.
-
-5. **Parse work item fields**
-
-   From the page text and/or snapshot, extract:
-   - Title/Summary: usually the main heading or the `<h1>` / page title
-   - Description: the body text, acceptance criteria, or "Definition of Done" section
-   - ID/Key: the work item ID from the URL or page (e.g. `123`, `ENG-123`)
-   - Status: if visible (e.g. "To Do", "In Progress", "Active")
-   - Assignee: if visible
-   - Priority: if visible
-   - Labels/Tags: if visible
-
-   If the page is a SPA that loads content dynamically:
-   - Wait longer (`browser_wait ms=5000`)
-   - Use `browser_query` with `mode=page_text` after the wait
-   - Try `browser_snapshot` which may capture more structured content
-
-6. **Create OpenSpec Change**
-   ```bash
-   openspec new change "{slug-from-title}"
-   ```
-
-   Write `proposal.md` with:
-   - Title: the work item title from the page
-   - Context: mention the source URL and the work item ID
-   - Requirements: extracted from description and acceptance criteria
-   - Scope: what's in/out based on the ticket
-
-7. **Hand off to proposal.** Load the `pc-plan-propose` skill (interactive mode) to generate the proposal, specs, and tasks. After it completes, call the `question` tool:
-
-   ```json
-   {
-     "questions": [
-       {
-         "header": "Ready to implement",
-         "question": "Ready to implement?",
-         "options": [
-           { "label": "yes", "description": "Load the pc-plan-apply skill to start implementation." },
-           { "label": "no", "description": "Stop here. You can run /plan-apply later." }
-         ]
-       }
-     ]
-   }
-   ```
-
-   Wait for confirmation before loading `pc-plan-apply`.
-
-## Working with common backlog tools
-
-### Azure DevOps (browser fallback)
-- URL: `https://dev.azure.com/{org}/{project}/_workitems/edit/{id}`
-- Title: visible in the work item header
-- Description: "Description" field section
-- Acceptance Criteria: "Acceptance Criteria" field section
-- State: visible in the top-right area
-
-### Linear
-- URL: `https://linear.app/{team}/issue/{key}`
-- Title: the issue title
-- Description: the issue body
-- Status: visible as a dropdown
-
-### Jira (browser fallback)
-- URL: `https://yoursite.atlassian.net/browse/{key}`
-- Title: the issue summary
-- Description: the description field
-- Status: visible in the status badge
-
-### Trello
-- URL: `https://trello.com/c/{short-id}`
-- Title: the card title
-- Description: the card description
-- Labels: visible as colored badges
-
-### Other tools (generic)
-- Look for `<h1>` or page title for the work item title
-- Look for the main content area for description
-- Use `browser_snapshot` to get structured accessibility tree data
-
-## Rules
-
-- Navigate only to URLs the user explicitly provides. Never guess or browse randomly.
-- The user must already be authenticated in their browser to the backlog system.
-- If the page requires login and the user isn't authenticated, tell them to log in via their browser and retry.
-- For GitHub/Azure/Jira URLs when the CLI is configured for those platforms, use the CLI-based skill instead (faster, more reliable, no browser needed).
-- This skill is read-only: no clicking buttons, no changing status.
-- Browser is a backlog-only platform: it has no PR or repo integration. PR creation uses the repo platform configured separately.
+---
+name: pc-userstory
+description: Parse work item from any URL using browser automation. Use when user provides a URL that doesn't match GitHub/Azure/Jira CLI platforms, or when backlog platform is 'browser'.
+license: MIT
+compatibility: Requires agent-browser CLI installed and openspec CLI.
+metadata:
+  author: copilots
+  version: "2.0"
+---
+
+This skill is used when the backlog platform is set to "Others (Browser)": when there is no CLI integration for the backlog system, or the user doesn't have API tokens. Work items are read directly from the web page using agent-browser.
+
+This skill overrides the `browser-automation` skill's external navigation restriction, but only for URLs the user explicitly provides as work items. Navigate only to URLs the user gives you.
+
+## Prerequisites
+
+- agent-browser installed (installed during onboarding) — verify with `agent-browser doctor`
+- An authenticated session for the backlog system:
+  - agent-browser runs its own Chrome, not the user's daily browser. Login state persists per session via `--session <slug> --restore`: log in once, and later runs restore cookies automatically.
+  - On first use, the user logs in manually in the opened window; state is saved on close and auto-restored afterwards.
+
+## Steps
+
+1. **Extract the URL** from the user's message
+   - The user provides a direct URL to a work item, issue, ticket, or PBI
+   - Examples: `https://dev.azure.com/org/project/_workitems/edit/123`, `https://linear.app/team/issue/ENG-123`, `https://trello.com/c/abc123`, `https://your-tool.com/ticket/456`
+
+2. **Open the URL in a persistent session**
+   ```bash
+   agent-browser --session backlog --restore open "https://the-url-the-user-provided"
+   ```
+
+3. **Wait for the page to load**
+   ```bash
+   agent-browser wait --load networkidle
+   ```
+   Prefer load-state waits over fixed sleeps; for SPAs that render after idle, add `agent-browser wait --text "<known heading>"` when a stable string is known.
+
+4. **Read the work item content**
+   ```bash
+   agent-browser snapshot
+   ```
+   The accessibility tree with `@ref` handles usually reveals the work item title, description, and fields more precisely than raw page text. Also useful:
+   ```bash
+   agent-browser read           # agent-readable text of the active tab
+   agent-browser get text "h1"  # the heading, when present
+   ```
+
+5. **Parse work item fields**
+
+   From the snapshot and/or text, extract:
+   - Title/Summary: usually the main heading or the `<h1>` / page title
+   - Description: the body text, acceptance criteria, or "Definition of Done" section
+   - ID/Key: the work item ID from the URL or page (e.g. `123`, `ENG-123`)
+   - Status: if visible (e.g. "To Do", "In Progress", "Active")
+   - Assignee: if visible
+   - Priority: if visible
+   - Labels/Tags: if visible
+
+   If the page is a SPA that loads content dynamically:
+   - Wait for load state again (`agent-browser wait --load networkidle`)
+   - Take a fresh `snapshot` after the wait
+   - `agent-browser get url` confirms you are still on the work item
+
+   If a login page appears instead, the session is not authenticated: tell the user to log in manually in the opened browser window, then retry from step 2 with the same `--session backlog --restore` (the login is saved for future runs).
+
+6. **Create OpenSpec Change**
+   ```bash
+   openspec new change "{slug-from-title}"
+   ```
+
+   Write `proposal.md` with:
+   - Title: the work item title from the page
+   - Context: mention the source URL and the work item ID
+   - Requirements: extracted from description and acceptance criteria
+   - Scope: what's in/out based on the ticket
+
+7. **Hand off to proposal.** Load the `pc-plan-propose` skill (interactive mode) to generate the proposal, specs, and tasks. After it completes, call the `question` tool:
+
+   ```json
+   {
+     "questions": [
+       {
+         "header": "Ready to implement",
+         "question": "Ready to implement?",
+         "options": [
+           { "label": "yes", "description": "Load the pc-plan-apply skill to start implementation." },
+           { "label": "no", "description": "Stop here. You can run /plan-apply later." }
+         ]
+       }
+     ]
+   }
+   ```
+
+   Wait for confirmation before loading `pc-plan-apply`.
+
+## Working with common backlog tools
+
+### Azure DevOps (browser fallback)
+- URL: `https://dev.azure.com/{org}/{project}/_workitems/edit/{id}`
+- Title: visible in the work item header
+- Description: "Description" field section
+- Acceptance Criteria: "Acceptance Criteria" field section
+- State: visible in the top-right area
+
+### Linear
+- URL: `https://linear.app/{team}/issue/{key}`
+- Title: the issue title
+- Description: the issue body
+- Status: visible as a dropdown
+
+### Jira (browser fallback)
+- URL: `https://yoursite.atlassian.net/browse/{key}`
+- Title: the issue summary
+- Description: the description field
+- Status: visible in the status badge
+
+### Trello
+- URL: `https://trello.com/c/{short-id}`
+- Title: the card title
+- Description: the card description
+- Labels: visible as colored badges
+
+### Other tools (generic)
+- Look for `<h1>` or page title for the work item title
+- Look for the main content area for description
+- Use `agent-browser snapshot` to get structured accessibility tree data
+
+## Rules
+
+- Navigate only to URLs the user explicitly provide. Never guess or browse randomly.
+- Reuse the `backlog` session (`--session backlog --restore`) so login state persists across runs.
+- If the page requires login and the session is not authenticated, tell them to log in via the opened browser window and retry.
+- For GitHub/Azure/Jira URLs when the CLI is configured for those platforms, use the CLI-based skill instead (faster, more reliable, no browser needed).
+- This skill is read-only: no clicking buttons, no changing status.
+- Browser is a backlog-only platform: it has no PR or repo integration. PR creation uses the repo platform configured separately.

package/{src/content → harness}/.opencode/package.json

@@ -1,10 +1,9 @@
-{
-  "dependencies": {
-    "@opencode-ai/plugin": "1.18.19",
-    "@different-ai/opencode-browser": "4.6.1",
-    "@mohak34/opencode-notifier": "0.2.8",
-    "@opentui/core": "0.5.6",
-    "@opentui/solid": "0.5.6",
-    "solid-js": "1.9.12"
-  }
-}
+{
+  "dependencies": {
+    "@opencode-ai/plugin": "1.18.19",
+    "@mohak34/opencode-notifier": "0.2.8",
+    "@opentui/core": "0.5.6",
+    "@opentui/solid": "0.5.6",
+    "solid-js": "1.9.12"
+  }
+}

package/{src/content → harness}/.opencode/plugins/pc-subagent-tiers.js

@@ -24,19 +24,94 @@ const TIERS = ["build", "fast", "plan"]
 // The two primaries, and the tier each takes its model from. plan denies edit
 // so a planning session cannot mutate the tree; bash stays allowed because the
 // planning skills shell out to git and openspec to read state.
+//
+// Their colours are theme keywords rather than derived hexes, and they are
+// fixed: these are the two agents a human picks, so they should look the same
+// in every project regardless of the theme in use.
 const PRIMARIES = {
   build: {
     tier: "build",
+    color: "primary",
     description: "Implement changes in this repository. Full write access, spawns specialist engineers for parallel work.",
     permission: null,
   },
   plan: {
     tier: "plan",
+    color: "warning",
     description: "Explore and plan without touching the tree. Read-only: proposes work for build to carry out.",
     permission: { edit: "deny" },
   },
 }
 
+// opencode's theme keywords. Treated as unset so a name-derived hex wins: the
+// old /make-engineer template asked whoever ran it to pick one of these and
+// avoid collisions by hand, which does not survive more than a few agents.
+const THEME_COLORS = new Set(["primary", "secondary", "accent", "success", "warning", "error", "info"])
+
+// Mirrors cli/utils/agent-color.js in the CLI, duplicated because a plugin has
+// to stand alone in the consumer repo. agent-color.test.js asserts the two stay
+// in step; change one and change the other.
+//
+// Only the hue is hashed. Fixed saturation and lightness are what keep every
+// result usable: hashing those too would eventually produce a near-grey,
+// near-black or near-white agent, invisible against one theme or the other.
+function agentColor(name) {
+  let h = 0x811c9dc5
+  for (let i = 0; i < name.length; i++) {
+    h ^= name.charCodeAt(i)
+    h = Math.imul(h, 0x01000193) >>> 0
+  }
+  const hue = (h >>> 0) % 360
+  const sat = 0.68
+  const light = 0.52
+  const c = (1 - Math.abs(2 * light - 1)) * sat
+  const x = c * (1 - Math.abs(((hue / 60) % 2) - 1))
+  const m = light - c / 2
+  const [r, g, b] =
+    hue < 60 ? [c, x, 0] :
+    hue < 120 ? [x, c, 0] :
+    hue < 180 ? [0, c, x] :
+    hue < 240 ? [0, x, c] :
+    hue < 300 ? [x, 0, c] :
+    [c, 0, x]
+  const toHex = v => Math.round((v + m) * 255).toString(16).padStart(2, "0")
+  return `#${toHex(r)}${toHex(g)}${toHex(b)}`.toUpperCase()
+}
+
+/** A theme keyword or a missing value yields to the derived hex; a hex stays. */
+function shouldDeriveColor(current) {
+  if (!current) return true
+  return THEME_COLORS.has(current.trim().toLowerCase())
+}
+
+/**
+ * Render a colour for YAML frontmatter.
+ *
+ * A hex has to be quoted. `#` opens a comment in YAML, so `color: #D83155`
+ * parses as null and opencode refuses the agent with "Invalid input color".
+ * Theme keywords need no quoting and stay bare.
+ */
+function yamlColor(value) {
+  return value.startsWith("#") ? `"${value}"` : value
+}
+
+function unquoteColor(raw) {
+  return (raw ?? "").trim().replace(/^["']/, "").replace(/["']$/, "")
+}
+
+/**
+ * The colour line an agent should have, or null when the current one is already
+ * right. Handles both choosing the colour and quoting it, so a file written by
+ * an earlier version with a bare hex is repaired in place rather than left
+ * broken.
+ */
+function colorLineFor(name, rawCurrent) {
+  const current = unquoteColor(rawCurrent)
+  const target = shouldDeriveColor(current) ? agentColor(name) : current
+  const rendered = yamlColor(target)
+  return (rawCurrent ?? "").trim() === rendered ? null : `color: ${rendered}`
+}
+
 const FULLSTACK_NAME = "fullstack-engineer"
 const FULLSTACK_TEMPLATE = `${FULLSTACK_NAME}.md`
 
@@ -102,7 +177,7 @@ export const PcSubagentTiers = async ({ directory }) => {
   // startup and are injected into generated files only, so a stale model: (from
   // a prior `stampAgentModels` run, or from when these were primary) is
   // stripped and the agent falls back to the session model in opencode.jsonc.
-  function normalizeTemplate(templateContent) {
+  function normalizeTemplate(templateContent, name) {
     const fmMatch = templateContent.match(/^---\r?\n([\s\S]*?)\r?\n---/)
     if (!fmMatch) return templateContent
 
@@ -113,6 +188,17 @@ export const PcSubagentTiers = async ({ directory }) => {
       fm = /^mode:/m.test(fm) ? fm.replace(/^mode:.*$/m, 'mode: subagent') : `mode: subagent\n${fm}`
       changed = true
     }
+    // Give every agent a colour derived from its name, so the same engineer
+    // reads the same in any project and two agents never collide by accident.
+    // colorLineFor also repairs a bare #hex written by an earlier version,
+    // which YAML read as a comment and opencode rejected outright.
+    if (name) {
+      const colorLine = colorLineFor(name, fm.match(/^color:\s*(.+)$/m)?.[1])
+      if (colorLine) {
+        fm = /^color:/m.test(fm) ? fm.replace(/^color:.*$/m, () => colorLine) : `${fm}\n${colorLine}`
+        changed = true
+      }
+    }
     if (/^model:/m.test(fm)) {
       // Remove the model: line and its trailing newline without leaving a
       // leading blank line (model: can be the first frontmatter entry).
@@ -140,7 +226,7 @@ export const PcSubagentTiers = async ({ directory }) => {
       'mode: primary',
     ]
     if (model) lines.push(`model: ${model}`)
-    lines.push('color: warning')
+    lines.push(`color: ${yamlColor(spec.color)}`)
     lines.push('permission:')
     // plan denies edit; everything else stays allowed so the planning skills can
     // still read the tree, shell out to git and openspec, and spawn engineers.
@@ -179,7 +265,7 @@ export const PcSubagentTiers = async ({ directory }) => {
         if (hasFullstack) {
           const fullstackPath = path.join(agentsDir, FULLSTACK_TEMPLATE)
           const rawFullstack = await fs.readFile(fullstackPath, "utf-8")
-          const fullstack = normalizeTemplate(rawFullstack)
+          const fullstack = normalizeTemplate(rawFullstack, FULLSTACK_NAME)
           if (fullstack !== rawFullstack) {
             await writeIfChanged(fullstackPath, fullstack)
             console.error(`[pc-subagent-tiers] Normalized ${FULLSTACK_TEMPLATE} (mode: subagent)`)
@@ -198,6 +284,7 @@ export const PcSubagentTiers = async ({ directory }) => {
                 ...cfg.agent[name],
                 mode: 'primary',
                 description: spec.description,
+                color: spec.color,
                 ...(model ? { model } : {}),
                 ...(spec.permission ? { permission: { ...cfg.agent[name]?.permission, ...spec.permission } } : {}),
               }
@@ -211,7 +298,7 @@ export const PcSubagentTiers = async ({ directory }) => {
         const templateContents = await Promise.all(
           templates.map(async name => {
             const rawContent = await fs.readFile(path.join(agentsDir, `${name}.md`), "utf-8")
-            const content = normalizeTemplate(rawContent)
+            const content = normalizeTemplate(rawContent, name)
             // If the template had the wrong mode or a stale model:, persist the fix to disk
             if (content !== rawContent) {
               await writeIfChanged(path.join(agentsDir, `${name}.md`), content)

package/{src/content → harness}/ARCHITECTURE.md

@@ -1,16 +1,16 @@
-> NOT GENERATED YET
->
-> This file has not been populated yet. It is intentionally empty.
->
-> **If this is a greenfield project** (no codebase exists yet): skip this for now.
-> Come back and run `/make-architecture` once you have meaningful code, structure, or infrastructure in place.
->
-> **If this is a brownfield project** (existing codebase): run this command now to generate the architecture documentation:
->
-> ```
-> /make-architecture
-> ```
->
-> This command analyzes your folder structure, config files, routes, data models, integrations, and build setup,
-> then writes a complete ARCHITECTURE.md covering components, data flow, tech stack, deployment, and more.
-> It is safe to rerun any time the architecture changes significantly.
+> NOT GENERATED YET
+>
+> This file has not been populated yet. It is intentionally empty.
+>
+> **If this is a greenfield project** (no codebase exists yet): skip this for now.
+> Come back and run `/make-architecture` once you have meaningful code, structure, or infrastructure in place.
+>
+> **If this is a brownfield project** (existing codebase): run this command now to generate the architecture documentation:
+>
+> ```
+> /make-architecture
+> ```
+>
+> This command analyzes your folder structure, config files, routes, data models, integrations, and build setup,
+> then writes a complete ARCHITECTURE.md covering components, data flow, tech stack, deployment, and more.
+> It is safe to rerun any time the architecture changes significantly.

package/{src/content → harness}/DESIGN.md

@@ -1,16 +1,16 @@
-> NOT GENERATED YET
->
-> This file has not been populated yet. It is intentionally empty.
->
-> **If this is a greenfield project** (no UI exists yet): skip this for now.
-> Come back and run `/make-design` once you have a design system, UI components, or styles in place.
->
-> **If this is a brownfield project** (existing UI/styles): run this command now to generate the design documentation:
->
-> ```
-> /make-design
-> ```
->
-> This command analyzes your CSS, Tailwind config, component files, and design tokens,
-> then writes a complete DESIGN.md with structured YAML tokens and written design intent.
-> It is safe to rerun any time your design system changes.
+> NOT GENERATED YET
+>
+> This file has not been populated yet. It is intentionally empty.
+>
+> **If this is a greenfield project** (no UI exists yet): skip this for now.
+> Come back and run `/make-design` once you have a design system, UI components, or styles in place.
+>
+> **If this is a brownfield project** (existing UI/styles): run this command now to generate the design documentation:
+>
+> ```
+> /make-design
+> ```
+>
+> This command analyzes your CSS, Tailwind config, component files, and design tokens,
+> then writes a complete DESIGN.md with structured YAML tokens and written design intent.
+> It is safe to rerun any time your design system changes.

package/{src/content → harness}/opencode.jsonc

@@ -4,9 +4,15 @@
     "AGENTS.md"
   ],
   "plugin": [
-    "@different-ai/opencode-browser@4.6.1",
     "@mohak34/opencode-notifier@0.2.8"
   ],
+  "mcp": {
+    "agent-browser": {
+      "type": "local",
+      "command": ["agent-browser", "mcp", "--tools", "core"],
+      "enabled": true
+    }
+  },
   "experimental": {
     "mcp_timeout": 300000
   },
@@ -23,12 +29,14 @@
   "skills": {
     "paths": [".agents/skills"]
   },
-  // build and plan are the only primaries. The pc-subagent-tiers plugin
+  // build and plan are the only primaries, and plan is the default: a session
+  // starts read-only and you switch to build once you know what to change.
+  // The pc-subagent-tiers plugin
   // regenerates .opencode/agents/{build,plan}.md from fullstack-engineer.md on
   // every startup and overrides these two entries with the resolved tier model,
   // so what is here is only the floor if the plugin cannot run. Every engineer
   // is mode: subagent and reached through task(), never picked by a human.
-  "default_agent": "build",
+  "default_agent": "plan",
   "agent": {
     "build": { "mode": "primary" },
     "plan": {

package/{src/content → harness}/openspec/config.yaml

@@ -1,20 +1,20 @@
-schema: spec-driven
-
-# Project context (optional)
-# This is shown to AI when creating artifacts.
-# Add your tech stack, conventions, style guides, domain knowledge, etc.
-# Example:
-#   context: |
-#     Tech stack: TypeScript, React, Node.js
-#     We use conventional commits
-#     Domain: e-commerce platform
-
-# Per-artifact rules (optional)
-# Add custom rules for specific artifacts.
-# Example:
-#   rules:
-#     proposal:
-#       - Keep proposals under 500 words
-#       - Always include a "Non-goals" section
-#     tasks:
-#       - Break tasks into chunks of max 2 hours
+schema: spec-driven
+
+# Project context (optional)
+# This is shown to AI when creating artifacts.
+# Add your tech stack, conventions, style guides, domain knowledge, etc.
+# Example:
+#   context: |
+#     Tech stack: TypeScript, React, Node.js
+#     We use conventional commits
+#     Domain: e-commerce platform
+
+# Per-artifact rules (optional)
+# Add custom rules for specific artifacts.
+# Example:
+#   rules:
+#     proposal:
+#       - Keep proposals under 500 words
+#       - Always include a "Non-goals" section
+#     tasks:
+#       - Break tasks into chunks of max 2 hours

package/{src/content → harness}/skills-lock.json

@@ -1,17 +1,17 @@
-{
-  "version": 1,
-  "skills": {
-    "find-skills": {
-      "source": "vercel-labs/skills",
-      "sourceType": "github",
-      "skillPath": "skills/find-skills/SKILL.md",
-      "computedHash": "781bd6d3f9b19f8c9af6b53d8d0e4876d0183841b565db34ca7092ffa412d111"
-    },
-    "user-story": {
-      "source": "deanpeters/product-manager-skills",
-      "sourceType": "github",
-      "skillPath": "skills/user-story/SKILL.md",
-      "computedHash": "user-story-placeholder"
-    }
-  }
-}
+{
+  "version": 1,
+  "skills": {
+    "find-skills": {
+      "source": "vercel-labs/skills",
+      "sourceType": "github",
+      "skillPath": "skills/find-skills/SKILL.md",
+      "computedHash": "781bd6d3f9b19f8c9af6b53d8d0e4876d0183841b565db34ca7092ffa412d111"
+    },
+    "user-story": {
+      "source": "deanpeters/product-manager-skills",
+      "sourceType": "github",
+      "skillPath": "skills/user-story/SKILL.md",
+      "computedHash": "user-story-placeholder"
+    }
+  }
+}