@plainconceptsplatform/agent-harness 3.2.0 → 3.3.0

package/cli/fragments/ops-ship/gl.md

@@ -1,85 +1,85 @@
-GitLab data comes from the `glab` CLI; a page fetch of gitlab.com is denied (pc-system-reminders). If `glab` is unavailable, report it as a blocker. Always pass `--repo {owner}/{repo}` explicitly, never rely on git context to resolve the repo.
-
----
-
-### Step 1: Verify feature branch
-
-```bash
-BRANCH="$(git branch --show-current)"
-DEFAULT_BRANCH="$(git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null | sed 's|^origin/||')"
-[ -z "$DEFAULT_BRANCH" ] && DEFAULT_BRANCH="main"
-```
-
-`$BRANCH` must be a work branch (`feature/*` or `bugfix/*`: the `pc-plan-apply` skill creates `feature/{change-slug}`). Never push the default branch.
-
-### Step 2: Capture screenshots (if UI changes exist)
-
-```bash
-browser_navigate url="http://localhost:{port}/{route}"
-browser_wait ms=2000
-browser_screenshot
-```
-
-Save to: `openspec/changes/{change-name}/images/{feature}.png`
-
-### Step 3: Commit and push
-
-The `pc-plan-apply` skill already committed each task group: usually only screenshots or small residuals remain. Stage the paths you actually changed; unscoped staging is denied (`pc-system-reminders`):
-
-```bash
-git add openspec/changes/{change-name}/images/  # plus any other paths you actually changed
-git commit -m "{change}: {summary}"   # only if there is something to commit
-git push -u origin "$BRANCH"
-```
-
-### Step 4: Upload screenshots (if any)
-
-If screenshots exist, upload them so they can be referenced in the MR description:
-
-```bash
-glab api --method POST "projects/:id/uploads" -f "file=@openspec/changes/{change-name}/images/{feature}.png"
-```
-
-(`:id` is glab's placeholder for the current project: this is the one sanctioned use of git context in this skill.)
-
-Parse the returned `markdown` field: use it to embed the image in the MR description. If the upload fails (the endpoint needs multipart form data and `-f` support varies by glab version), fall back to referencing the image committed on the branch instead.
-
-If no UI changes, skip this step.
-
-### Step 5: Create Merge Request
-
-```bash
-glab mr create \
-  --source-branch "$BRANCH" \
-  --target-branch "$DEFAULT_BRANCH" \
-  --title "{title}" \
-  --description "Closes {issue-link}
-
-## Summary
-{summary from proposal.md}
-
-## Changes
-{key changes from tasks.md}
-
-## Test plan
-- [ ] {checklist of manual verification steps}
-{screenshots if available}" \
-  --remove-source-branch \
-  --squash-before-merge
-```
-
-Do NOT use `--yes` unless running in autopilot/non-interactive mode.
-
-### Step 6: Report
-
-Display:
-
-```text
-Merge Request created
-  MR: {mr-url}
-  Title: {title}
-  Source: {branch}
-  Target: {default-branch}
-```
-
+GitLab data comes from the `glab` CLI; a page fetch of gitlab.com is denied (pc-system-reminders). If `glab` is unavailable, report it as a blocker. Always pass `--repo {owner}/{repo}` explicitly, never rely on git context to resolve the repo.
+
+---
+
+### Step 1: Verify feature branch
+
+```bash
+BRANCH="$(git branch --show-current)"
+DEFAULT_BRANCH="$(git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null | sed 's|^origin/||')"
+[ -z "$DEFAULT_BRANCH" ] && DEFAULT_BRANCH="main"
+```
+
+`$BRANCH` must be a work branch (`feature/*` or `bugfix/*`: the `pc-plan-apply` skill creates `feature/{change-slug}`). Never push the default branch.
+
+### Step 2: Capture screenshots (if UI changes exist)
+
+```bash
+browser_navigate url="http://localhost:{port}/{route}"
+browser_wait ms=2000
+browser_screenshot
+```
+
+Save to: `openspec/changes/{change-name}/images/{feature}.png`
+
+### Step 3: Commit and push
+
+The `pc-plan-apply` skill already committed each task group: usually only screenshots or small residuals remain. Stage the paths you actually changed; unscoped staging is denied (`pc-system-reminders`):
+
+```bash
+git add openspec/changes/{change-name}/images/  # plus any other paths you actually changed
+git commit -m "{change}: {summary}"   # only if there is something to commit
+git push -u origin "$BRANCH"
+```
+
+### Step 4: Upload screenshots (if any)
+
+If screenshots exist, upload them so they can be referenced in the MR description:
+
+```bash
+glab api --method POST "projects/:id/uploads" -f "file=@openspec/changes/{change-name}/images/{feature}.png"
+```
+
+(`:id` is glab's placeholder for the current project: this is the one sanctioned use of git context in this skill.)
+
+Parse the returned `markdown` field: use it to embed the image in the MR description. If the upload fails (the endpoint needs multipart form data and `-f` support varies by glab version), fall back to referencing the image committed on the branch instead.
+
+If no UI changes, skip this step.
+
+### Step 5: Create Merge Request
+
+```bash
+glab mr create \
+  --source-branch "$BRANCH" \
+  --target-branch "$DEFAULT_BRANCH" \
+  --title "{title}" \
+  --description "Closes {issue-link}
+
+## Summary
+{summary from proposal.md}
+
+## Changes
+{key changes from tasks.md}
+
+## Test plan
+- [ ] {checklist of manual verification steps}
+{screenshots if available}" \
+  --remove-source-branch \
+  --squash-before-merge
+```
+
+Do NOT use `--yes` unless running in autopilot/non-interactive mode.
+
+### Step 6: Report
+
+Display:
+
+```text
+Merge Request created
+  MR: {mr-url}
+  Title: {title}
+  Source: {branch}
+  Target: {default-branch}
+```
+
 ---

package/cli/index.js

@@ -1,116 +1,116 @@
-#!/usr/bin/env node
-import chalk from 'chalk'
-import { createRequire } from 'node:module'
-import { runJoin } from './commands/join.js'
-import { runUpdate } from './commands/update.js'
-import { runSingleCommand } from './commands/single.js'
-import { runWizard } from './commands/wizard.js'
-import { exit } from './utils/process.js'
-import { runMigrateCommand } from './commands/migrate.js'
-import { findLegacyInstall } from './utils/legacy-check.js'
-
-function printHelp(version) {
-  console.log(`agent-harness v${version}`)
-  console.log()
-  console.log('Usage:')
-  console.log('  npx @plainconceptsplatform/agent-harness             Install the harness (full wizard)')
-  console.log('  npx @plainconceptsplatform/agent-harness <command>   Run a single step command')
-  console.log()
-  console.log('Commands:')
-  console.log('  update          Bring the harness up to date from saved config (no prompts)')
-  console.log('  migrate         Move a v1 (opencode-onboard) project to v2, keeping your content')
-  console.log('  join            Set up a teammate\'s machine (checks & local installs only)')
-  console.log('  clean           Run AI files cleanup step')
-  console.log('  platform        Run platform selection step')
-  console.log('  copy            Run content copy step')
-  console.log('  openspec        Run OpenSpec initialization step')
-  console.log('  models          Run models selection step')
-  console.log('  optimization    Run token optimization tools step')
-  console.log('  browser         Run agent-browser installer step')
-  console.log('  metadata        Write onboarding metadata step')
-  console.log()
-  console.log('Options:')
-  console.log('  -h, --help      Show this help message')
-}
-
-if (process.stdout.isTTY) console.clear()
-console.log()
-const require = createRequire(import.meta.url)
-const { version } = require('../package.json')
-const args = process.argv.slice(2)
-
-if (args.includes('-h') || args.includes('--help')) {
-  printHelp(version)
-  exit()
-}
-
-async function refuseLegacyInstall() {
-  const legacy = await findLegacyInstall()
-  if (!legacy) return false
-
-  console.log(chalk.red('This project was set up by opencode-onboard v1.'))
-  console.log()
-  if (legacy.files.length > 0) console.log(chalk.dim(`  config:  ${legacy.files.join(', ')}`))
-  if (legacy.skills.length > 0) {
-    const shown = legacy.skills.slice(0, 3).join(', ')
-    const rest = legacy.skills.length > 3 ? `, +${legacy.skills.length - 3} more` : ''
-    console.log(chalk.dim(`  skills:  ${shown}${rest}`))
-  }
-  console.log()
-  console.log('agent-harness v2 renamed both the config files and the skill prefix,')
-  console.log('and it does not migrate v1 projects. Continuing would leave the harness')
-  console.log('half-patched without reporting an error.')
-  console.log()
-  console.log('Migrate it, keeping your generated skills and custom engineers:')
-  console.log(chalk.dim('  npx @plainconceptsplatform/agent-harness migrate'))
-  console.log(chalk.dim('  npx @plainconceptsplatform/agent-harness update'))
-  console.log()
-  console.log(chalk.dim('Add --dry-run to see what migrate would change first.'))
-  return true
-}
-
-// Ctrl-C out of an @inquirer prompt throws ExitPromptError; that is a normal
-// cancellation, not a crash, so it must not exit non-zero.
-async function main() {
-  // migrate is the way out of a v1 project, so it must run before the guard
-  // that refuses v1 projects.
-  if (args[0] === 'migrate') {
-    await runMigrateCommand(args.slice(1))
-    return
-  }
-  if (await refuseLegacyInstall()) {
-    exit(1)
-    return
-  }
-  if (args.length === 0) {
-    await runWizard(version)
-    return
-  }
-  if (args[0] === 'join') {
-    await runJoin()
-    return
-  }
-  if (args[0] === 'update') {
-    await runUpdate()
-    return
-  }
-  if (!await runSingleCommand(args[0])) {
-    console.log(chalk.red(`Unknown command: ${args[0]}`))
-    console.log()
-    printHelp(version)
-    exit(1)
-  }
-}
-
-try {
-  await main()
-} catch (err) {
-  if (err.name === 'ExitPromptError') {
-    console.log()
-    console.log(chalk.yellow('Cancelled.'))
-  } else {
-    console.error(chalk.red('\nUnexpected error:'), err.message)
-    exit(1)
-  }
-}
-exit()
+#!/usr/bin/env node
+import chalk from 'chalk'
+import { createRequire } from 'node:module'
+import { runJoin } from './commands/join.js'
+import { runUpdate } from './commands/update.js'
+import { runSingleCommand } from './commands/single.js'
+import { runWizard } from './commands/wizard.js'
+import { exit } from './utils/process.js'
+import { runMigrateCommand } from './commands/migrate.js'
+import { findLegacyInstall } from './utils/legacy-check.js'
+
+function printHelp(version) {
+  console.log(`agent-harness v${version}`)
+  console.log()
+  console.log('Usage:')
+  console.log('  npx @plainconceptsplatform/agent-harness             Install the harness (full wizard)')
+  console.log('  npx @plainconceptsplatform/agent-harness <command>   Run a single step command')
+  console.log()
+  console.log('Commands:')
+  console.log('  update          Bring the harness up to date from saved config (no prompts)')
+  console.log('  migrate         Move a v1 (opencode-onboard) project to v2, keeping your content')
+  console.log('  join            Set up a teammate\'s machine (checks & local installs only)')
+  console.log('  clean           Run AI files cleanup step')
+  console.log('  platform        Run platform selection step')
+  console.log('  copy            Run content copy step')
+  console.log('  openspec        Run OpenSpec initialization step')
+  console.log('  models          Run models selection step')
+  console.log('  optimization    Run token optimization tools step')
+  console.log('  browser         Run agent-browser installer step')
+  console.log('  metadata        Write onboarding metadata step')
+  console.log()
+  console.log('Options:')
+  console.log('  -h, --help      Show this help message')
+}
+
+if (process.stdout.isTTY) console.clear()
+console.log()
+const require = createRequire(import.meta.url)
+const { version } = require('../package.json')
+const args = process.argv.slice(2)
+
+if (args.includes('-h') || args.includes('--help')) {
+  printHelp(version)
+  exit()
+}
+
+async function refuseLegacyInstall() {
+  const legacy = await findLegacyInstall()
+  if (!legacy) return false
+
+  console.log(chalk.red('This project was set up by opencode-onboard v1.'))
+  console.log()
+  if (legacy.files.length > 0) console.log(chalk.dim(`  config:  ${legacy.files.join(', ')}`))
+  if (legacy.skills.length > 0) {
+    const shown = legacy.skills.slice(0, 3).join(', ')
+    const rest = legacy.skills.length > 3 ? `, +${legacy.skills.length - 3} more` : ''
+    console.log(chalk.dim(`  skills:  ${shown}${rest}`))
+  }
+  console.log()
+  console.log('agent-harness v2 renamed both the config files and the skill prefix,')
+  console.log('and it does not migrate v1 projects. Continuing would leave the harness')
+  console.log('half-patched without reporting an error.')
+  console.log()
+  console.log('Migrate it, keeping your generated skills and custom engineers:')
+  console.log(chalk.dim('  npx @plainconceptsplatform/agent-harness migrate'))
+  console.log(chalk.dim('  npx @plainconceptsplatform/agent-harness update'))
+  console.log()
+  console.log(chalk.dim('Add --dry-run to see what migrate would change first.'))
+  return true
+}
+
+// Ctrl-C out of an @inquirer prompt throws ExitPromptError; that is a normal
+// cancellation, not a crash, so it must not exit non-zero.
+async function main() {
+  // migrate is the way out of a v1 project, so it must run before the guard
+  // that refuses v1 projects.
+  if (args[0] === 'migrate') {
+    await runMigrateCommand(args.slice(1))
+    return
+  }
+  if (await refuseLegacyInstall()) {
+    exit(1)
+    return
+  }
+  if (args.length === 0) {
+    await runWizard(version)
+    return
+  }
+  if (args[0] === 'join') {
+    await runJoin()
+    return
+  }
+  if (args[0] === 'update') {
+    await runUpdate()
+    return
+  }
+  if (!await runSingleCommand(args[0])) {
+    console.log(chalk.red(`Unknown command: ${args[0]}`))
+    console.log()
+    printHelp(version)
+    exit(1)
+  }
+}
+
+try {
+  await main()
+} catch (err) {
+  if (err.name === 'ExitPromptError') {
+    console.log()
+    console.log(chalk.yellow('Cancelled.'))
+  } else {
+    console.error(chalk.red('\nUnexpected error:'), err.message)
+    exit(1)
+  }
+}
+exit()

package/cli/presets/agents-content.json

@@ -1,34 +1,34 @@
-{
-  "platform": {
-    "none": {
-      "workflow": "There is no backlog and no PR integration here, so the work arrives in the conversation and the local repository is the only context.\n\n- A described feature, bug or refactor: clarify if needed, then `pc-plan-propose` when the change is worth planning, or straight to `pc-plan-apply`.\n- An existing OpenSpec change, plus any of `implement` / `start` / `go`: `pc-plan-apply`.\n- `just do it` or `quick fix`: work in this session, no proposal, no ceremony.\n\nA GitHub or Azure DevOps URL is not a trigger in this mode; re-run onboarding to configure a platform.",
-      "skillsGuide": "No platform skills installed (platform: none). Work from direct user instructions and local OpenSpec artifacts only."
-    },
-    "azure": {
-      "workflow": "An Azure DevOps work item or PR URL in the user's message means run the pipeline, in whatever words it arrives, unless they asked for analysis or context only.\n\n- Work item URL: `pc-userstory` to parse it, `pc-plan-propose` for the plan, confirm, `pc-plan-apply` to build, then ship.\n- An existing OpenSpec change, plus any of `implement` / `start` / `go`: `pc-plan-apply`, then ship.\n- A PR URL with a feedback or fix request: read the PR comments, fix, update the PR.",
-      "skillsGuide": "Platform skills (Azure DevOps):\n- `@pc-userstory`: load when an Azure DevOps work item URL is detected. Fetches the work item via `az` CLI and creates an OpenSpec change. NEVER use browser tools for Azure DevOps operations.\n- `pc-ops-ship`: load in ship mode to create a PR and link the work item, or in feedback mode to read and classify PR review comments."
-    },
-    "github": {
-      "workflow": "A GitHub Issue or PR URL in the user's message means run the pipeline, in whatever words it arrives, unless they asked for analysis or context only.\n\n- Issue URL: `pc-userstory` to parse it, `pc-plan-propose` for the plan, confirm, `pc-plan-apply` to build, then ship.\n- An existing OpenSpec change, plus any of `implement` / `start` / `go`: `pc-plan-apply`, then ship.\n- A PR URL with a feedback or fix request: read the PR comments, fix, update the PR.",
-      "skillsGuide": "Platform skills (GitHub):\n- `@pc-userstory`: load when a GitHub Issue URL is detected. Fetches the issue via `gh` CLI and creates an OpenSpec change. NEVER use webfetch to access GitHub URLs.\n- `pc-ops-ship`: load in ship mode to create a PR with screenshots, or in feedback mode to read and classify PR review comments."
-    },
-    "mixed": {
-      "default": {
-        "workflow": "The backlog and the repo are on different platforms here: `.opencode/harness.json` → `platform.backlog` and `platform.repo`. Never cross them. Work items always come from the backlog CLI and pull requests always from the repo CLI, or the command fails against the wrong host and the fallback is a page fetch that is denied.\n\nA work item URL, or a PR URL with a feedback request, means run the pipeline, in whatever words it arrives, unless the user asked for analysis or context only.\n\n- Work item URL or issue key: `pc-userstory` (backlog CLI) to parse it, `pc-plan-propose` for the plan, confirm, `pc-plan-apply` to build, `pc-ops-ship` (repo CLI) to ship.\n- An existing OpenSpec change, plus any of `implement` / `start` / `go`: `pc-plan-apply`, then ship.\n- A PR or MR URL with a feedback or fix request: read its comments through the repo CLI, fix, update it.",
-        "skillsGuide": "Mixed platform setup: the two platform skills target different hosts:\n- `@pc-userstory` → fetches work items from the backlog platform. Load when a work-item URL or issue key is provided.\n- `pc-ops-ship` → creates PRs/MRs and triages review feedback on the repo platform. Load in ship mode or PR-feedback mode."
-      }
-    },
-    "jira": {
-      "workflow": "A Jira URL or a bare issue key (`PROJ-123`) means run the pipeline, in whatever words it arrives, unless they asked for analysis or context only.\n\n- Either one: `pc-userstory` to fetch it through `acli jira`, `pc-plan-propose` for the plan, confirm, `pc-plan-apply` to build, then ship.\n- An existing OpenSpec change, plus any of `implement` / `start` / `go`: `pc-plan-apply`, then ship.\n\nJira has no pull requests: PR work runs on the repo platform in `platform.repo`.",
-      "skillsGuide": "### Backlog Platform: Jira\n- `pc-userstory` -> fetches Jira work items via `acli jira` CLI. Load when a Jira URL or issue key is provided.\n\n### Repo Platform\n- PR skills are loaded based on `platform.repo` (GitHub or Azure DevOps)."
-    },
-    "gitlab": {
-      "workflow": "A backlog work item URL, or a GitLab MR URL with a feedback request, means run the pipeline, in whatever words it arrives, unless they asked for analysis or context only.\n\n- Work item URL: `pc-userstory` to fetch it through the backlog CLI, `pc-plan-propose` for the plan, confirm, `pc-plan-apply` to build, then ship.\n- An existing OpenSpec change, plus any of `implement` / `start` / `go`: `pc-plan-apply`, then ship.\n- An MR URL with a feedback or fix request: `glab mr note list`, triage, fix, update the MR.\n\nGitLab has no backlog here: work items come from the platform in `platform.backlog`.",
-      "skillsGuide": "### Repo Platform: GitLab\n- `pc-ops-ship` -> creates GitLab merge requests via `glab` CLI. Load when shipping a branch or processing MR feedback.\n\n### Backlog Platform\n- Work item skills are loaded based on `platform.backlog` (GitHub / Azure / Jira)."
-    },
-    "browser": {
-      "workflow": "Any work item URL means run the pipeline, whichever tool it points at, unless the user asked for analysis or context only.\n\n- The URL: `pc-userstory` to open and read the page, `pc-plan-propose` for the plan, confirm, `pc-plan-apply` to build, then ship.\n- An existing OpenSpec change, plus any of `implement` / `start` / `go`: `pc-plan-apply`, then ship.\n\nBrowser is backlog-only: PR work runs on the repo platform in `platform.repo`.",
-      "skillsGuide": "### Backlog Platform: Others (Browser)\n- `pc-userstory` -> opens work item URLs via agent-browser, reads page content, creates OpenSpec changes. Load when a URL the user provides does not match GitHub/Azure/Jira CLI platforms.\n\n### Repo Platform\n- PR skills are loaded based on `platform.repo` (GitHub / Azure DevOps / GitLab)."
-    }
-  }
-}
+{
+  "platform": {
+    "none": {
+      "workflow": "There is no backlog and no PR integration here, so the work arrives in the conversation and the local repository is the only context.\n\n- A described feature, bug or refactor: clarify if needed, then `pc-plan-propose` when the change is worth planning, or straight to `pc-plan-apply`.\n- An existing OpenSpec change, plus any of `implement` / `start` / `go`: `pc-plan-apply`.\n- `just do it` or `quick fix`: work in this session, no proposal, no ceremony.\n\nA GitHub or Azure DevOps URL is not a trigger in this mode; re-run onboarding to configure a platform.",
+      "skillsGuide": "No platform skills installed (platform: none). Work from direct user instructions and local OpenSpec artifacts only."
+    },
+    "azure": {
+      "workflow": "An Azure DevOps work item or PR URL in the user's message means run the pipeline, in whatever words it arrives, unless they asked for analysis or context only.\n\n- Work item URL: `pc-userstory` to parse it, `pc-plan-propose` for the plan, confirm, `pc-plan-apply` to build, then ship.\n- An existing OpenSpec change, plus any of `implement` / `start` / `go`: `pc-plan-apply`, then ship.\n- A PR URL with a feedback or fix request: read the PR comments, fix, update the PR.",
+      "skillsGuide": "Platform skills (Azure DevOps):\n- `@pc-userstory`: load when an Azure DevOps work item URL is detected. Fetches the work item via `az` CLI and creates an OpenSpec change. NEVER use browser tools for Azure DevOps operations.\n- `pc-ops-ship`: load in ship mode to create a PR and link the work item, or in feedback mode to read and classify PR review comments."
+    },
+    "github": {
+      "workflow": "A GitHub Issue or PR URL in the user's message means run the pipeline, in whatever words it arrives, unless they asked for analysis or context only.\n\n- Issue URL: `pc-userstory` to parse it, `pc-plan-propose` for the plan, confirm, `pc-plan-apply` to build, then ship.\n- An existing OpenSpec change, plus any of `implement` / `start` / `go`: `pc-plan-apply`, then ship.\n- A PR URL with a feedback or fix request: read the PR comments, fix, update the PR.",
+      "skillsGuide": "Platform skills (GitHub):\n- `@pc-userstory`: load when a GitHub Issue URL is detected. Fetches the issue via `gh` CLI and creates an OpenSpec change. NEVER use webfetch to access GitHub URLs.\n- `pc-ops-ship`: load in ship mode to create a PR with screenshots, or in feedback mode to read and classify PR review comments."
+    },
+    "mixed": {
+      "default": {
+        "workflow": "The backlog and the repo are on different platforms here: `.opencode/harness.json` → `platform.backlog` and `platform.repo`. Never cross them. Work items always come from the backlog CLI and pull requests always from the repo CLI, or the command fails against the wrong host and the fallback is a page fetch that is denied.\n\nA work item URL, or a PR URL with a feedback request, means run the pipeline, in whatever words it arrives, unless the user asked for analysis or context only.\n\n- Work item URL or issue key: `pc-userstory` (backlog CLI) to parse it, `pc-plan-propose` for the plan, confirm, `pc-plan-apply` to build, `pc-ops-ship` (repo CLI) to ship.\n- An existing OpenSpec change, plus any of `implement` / `start` / `go`: `pc-plan-apply`, then ship.\n- A PR or MR URL with a feedback or fix request: read its comments through the repo CLI, fix, update it.",
+        "skillsGuide": "Mixed platform setup: the two platform skills target different hosts:\n- `@pc-userstory` → fetches work items from the backlog platform. Load when a work-item URL or issue key is provided.\n- `pc-ops-ship` → creates PRs/MRs and triages review feedback on the repo platform. Load in ship mode or PR-feedback mode."
+      }
+    },
+    "jira": {
+      "workflow": "A Jira URL or a bare issue key (`PROJ-123`) means run the pipeline, in whatever words it arrives, unless they asked for analysis or context only.\n\n- Either one: `pc-userstory` to fetch it through `acli jira`, `pc-plan-propose` for the plan, confirm, `pc-plan-apply` to build, then ship.\n- An existing OpenSpec change, plus any of `implement` / `start` / `go`: `pc-plan-apply`, then ship.\n\nJira has no pull requests: PR work runs on the repo platform in `platform.repo`.",
+      "skillsGuide": "### Backlog Platform: Jira\n- `pc-userstory` -> fetches Jira work items via `acli jira` CLI. Load when a Jira URL or issue key is provided.\n\n### Repo Platform\n- PR skills are loaded based on `platform.repo` (GitHub or Azure DevOps)."
+    },
+    "gitlab": {
+      "workflow": "A backlog work item URL, or a GitLab MR URL with a feedback request, means run the pipeline, in whatever words it arrives, unless they asked for analysis or context only.\n\n- Work item URL: `pc-userstory` to fetch it through the backlog CLI, `pc-plan-propose` for the plan, confirm, `pc-plan-apply` to build, then ship.\n- An existing OpenSpec change, plus any of `implement` / `start` / `go`: `pc-plan-apply`, then ship.\n- An MR URL with a feedback or fix request: `glab mr note list`, triage, fix, update the MR.\n\nGitLab has no backlog here: work items come from the platform in `platform.backlog`.",
+      "skillsGuide": "### Repo Platform: GitLab\n- `pc-ops-ship` -> creates GitLab merge requests via `glab` CLI. Load when shipping a branch or processing MR feedback.\n\n### Backlog Platform\n- Work item skills are loaded based on `platform.backlog` (GitHub / Azure / Jira)."
+    },
+    "browser": {
+      "workflow": "Any work item URL means run the pipeline, whichever tool it points at, unless the user asked for analysis or context only.\n\n- The URL: `pc-userstory` to open and read the page, `pc-plan-propose` for the plan, confirm, `pc-plan-apply` to build, then ship.\n- An existing OpenSpec change, plus any of `implement` / `start` / `go`: `pc-plan-apply`, then ship.\n\nBrowser is backlog-only: PR work runs on the repo platform in `platform.repo`.",
+      "skillsGuide": "### Backlog Platform: Others (Browser)\n- `pc-userstory` -> opens work item URLs via agent-browser, reads page content, creates OpenSpec changes. Load when a URL the user provides does not match GitHub/Azure/Jira CLI platforms.\n\n### Repo Platform\n- PR skills are loaded based on `platform.repo` (GitHub / Azure DevOps / GitLab)."
+    }
+  }
+}

package/cli/presets/browser.json

@@ -1,10 +1,10 @@
-{
-  "installer": {
-    "command": "npm",
-    "args": ["install", "-g", "agent-browser@0.36.0"]
-  },
-  "chromeSetup": {
-    "command": "agent-browser",
-    "args": ["install"]
-  }
-}
+{
+  "installer": {
+    "command": "npm",
+    "args": ["install", "-g", "agent-browser@0.36.0"]
+  },
+  "chromeSetup": {
+    "command": "agent-browser",
+    "args": ["install"]
+  }
+}

package/cli/presets/clean.json

@@ -1,21 +1,21 @@
-{
-  "preserve": ["DESIGN.md", "ARCHITECTURE.md", "openspec"],
-  "detectFiles": [
-    "AGENTS.md",
-    "CLAUDE.md",
-    "ARCHITECTURE.md",
-    "DESIGN.md",
-    ".cursorrules",
-    ".clinerules",
-    ".windsurfrules",
-    ".github/copilot-instructions.md",
-    "copilot-instructions.md",
-    ".aider.conf.yml",
-    ".aider",
-    ".opencode",
-    ".agents"
-  ],
-  "directoryTargets": [".opencode", ".agents"],
-  "preserveSubfolders": ["skills"],
-  "selectionMessage": "Select AI config files to remove:"
-}
+{
+  "preserve": ["DESIGN.md", "ARCHITECTURE.md", "openspec"],
+  "detectFiles": [
+    "AGENTS.md",
+    "CLAUDE.md",
+    "ARCHITECTURE.md",
+    "DESIGN.md",
+    ".cursorrules",
+    ".clinerules",
+    ".windsurfrules",
+    ".github/copilot-instructions.md",
+    "copilot-instructions.md",
+    ".aider.conf.yml",
+    ".aider",
+    ".opencode",
+    ".agents"
+  ],
+  "directoryTargets": [".opencode", ".agents"],
+  "preserveSubfolders": ["skills"],
+  "selectionMessage": "Select AI config files to remove:"
+}