@mmerterden/multi-agent-pipeline 12.4.0 → 12.6.0

package/pipeline/skills/shared/core/multi-agent-refactor/SKILL.md

@@ -1,39 +1,41 @@
 ---
 name: multi-agent-refactor
 language: en
-description: "Analyse the project: extract adapted best-practices, hunt real bugs + improvement areas, check upstream drift of derived skills, draft one plan, take approval, develop, then ask whether to sync."
+description: "Analyse the project: extract adapted best-practices, hunt real bugs + improvement areas, check upstream drift of derived skills, research the companion dev-toolkit MCP server against current MCP practice, draft one plan, take approval, develop, then ask whether to sync."
 user-invocable: true
-argument-hint: 'bugs | best-practices | drift | security | tests | performance | docs | ci | deps'
+argument-hint: 'bugs | best-practices | drift | dev-toolkit | security | tests | performance | docs | ci | deps'
 ---
 
 # Multi-Agent Refactor
 
-**One command. Best-practices + Bug hunt + Upstream drift -> Score -> Plan -> Approval -> Develop -> Sync.**
+**One command. Best-practices + Bug hunt + Upstream drift + Dev-toolkit -> Score -> Plan -> Approval -> Develop -> Sync.**
 
-Deep-analyses the current project, extracts the global best-practices worth adopting (adapted to our stack), hunts real bugs and improvement areas, checks whether any skills we derived from an upstream source have drifted, scores everything, drafts a single prioritized plan, takes approval, applies the approved items, and asks about sync when done.
+Deep-analyses the current project, extracts the global best-practices worth adopting (adapted to our stack), hunts real bugs and improvement areas, checks whether any skills we derived from an upstream source have drifted, researches the companion dev-toolkit MCP server against current MCP practice, scores everything, drafts a single prioritized plan, takes approval, applies the approved items, and asks about sync when done.
 
-**Input**: $ARGUMENTS (optional  -  area to focus on: "security", "performance", "tests", "bugs", "best-practices", "drift", etc.)
+**Input**: $ARGUMENTS (optional  -  area to focus on: "security", "performance", "tests", "bugs", "best-practices", "drift", "dev-toolkit", etc.)
 
 ## Flow
 
 ```
 Step 0:  BEST-PRACTICES  Research the field, extract the best approaches, ADAPT them to our stack -> plan band A
 Step 0b: DRIFT           Check upstream-derived skills for updates we have not pulled -> plan band D
+Step 0c: DEV-TOOLKIT     Research current MCP practice + audit the companion dev-toolkit repo -> plan band E
 Step 1:  SCAN            Scan the project structure (files, LOC, dependencies, CI, tests)
 Step 2:  ANALYZE         10 categories + an explicit BUG HUNT (real defects, not just scores) -> plan bands B, C
 Step 3:  SCORE           Each category out of 10, total /100
-Step 4:  PLAN            Merge bands A (best-practice) + B (bugs) + C (improvements) + D (drift), priority-ordered
+Step 4:  PLAN            Merge bands A (best-practice) + B (bugs) + C (improvements) + D (drift) + E (dev-toolkit)
 Step 5:  ASK             "Shall I start developing?"  -  take approval
 Step 6:  IMPLEMENT       Apply approved items in order (lint, test, commit)
 Step 7:  VERIFY          Confirm all tests + lint pass
 Step 8:  ASK SYNC        "Shall I run multi-agent-sync?"  -  take approval
 ```
 
-Plan bands (all four feed the single Step 4 table):
+Plan bands (all five feed the single Step 4 table):
 - **A - Best-practice**: the best field approaches, adapted so they actually fit this repo.
 - **B - Bug**: real defects found in the code (correctness, security, data-loss, crashes).
 - **C - Improvement**: quality/perf/DX gaps surfaced by the 10-category analysis.
 - **D - Drift**: upstream updates to skills we derived from an external source.
+- **E - Dev-toolkit**: current-practice gaps in the companion dev-toolkit MCP server (the pipeline's device and browser hands), applied in that repo.
 
 ## Step 0: BEST-PRACTICES  -  research the field, adapt to us
 
@@ -94,6 +96,54 @@ Procedure:
 
 5. For each drifted entry, add a band-D plan item: "port upstream <plugin> <version> changes into <localPath>". Do not auto-apply  -  it goes through Step 5 approval; after porting, bump the entry's `derivedFromVersion`.
 
+## Step 0c: DEV-TOOLKIT  -  current MCP practice for the companion toolkit
+
+The pipeline's device and browser hands are MCP tools served by a companion repo (`dev-toolkit-mcp`), and several pipeline skills declare a minimum toolkit version. This step researches current MCP practice and audits that repo against it.
+
+**Resolution**  -  configuration first, never a hardcoded path:
+
+1. `prefs.global.devToolkit`: `{ enabled, label, localPath, mcpServerName, packageName, registry, repoUrl }`.
+2. If unset, auto-detect from the MCP registration: `mcpServers` in `~/.claude.json` (plus `projects[*].mcpServers`) and `~/.claude/settings.json`; for a stdio `node` entry take `dirname(args[0])`, and accept it only if that directory is a git repo whose `package.json` depends on `@modelcontextprotocol/sdk`.
+3. Neither resolves (or `enabled: false`) -> skip and report "no dev-toolkit configured". Never guess a path, never clone.
+
+**Research axes**  -  a finding without a source link is not a finding:
+
+| # | Axis | Where to look | What to extract |
+|---|------|---------------|-----------------|
+| 1 | MCP protocol | spec revisions + `@modelcontextprotocol/sdk` releases | features released since the pinned SDK that the server does not use: tool annotations, `outputSchema` + structured content, resource links, progress + cancellation, `tools/list_changed`, pagination |
+| 2 | Host clients | Claude Code / Copilot CLI / Cursor / Antigravity docs | description budget, tool-count ceilings, naming, output size limits, permission ergonomics |
+| 3 | Peer servers | GitHub search on the same domain + `stars:>50` | surfaces we lack, conventions peers converged on, what to discard |
+| 4 | Wrapped tooling | `simctl`, `idb`, `adb`, `xcodebuild`, Playwright notes, Apple ITMS + review guidelines | deprecated flags in use, new capabilities worth a tool, audit rules that changed |
+| 5 | Field practice | X / Twitter, Reddit, MCP community | what server authors changed recently (transport, output-token diets, error shape) |
+
+**Audit the toolkit**  -  run the checks, do not assume:
+
+```bash
+DT="<resolved localPath>"
+node --check "$DT/index.js"; find "$DT/tools" -name "*.js" -exec node --check {} \;
+grep -rn "console\.log(" "$DT/index.js" "$DT/tools" || echo "stdout clean"   # stdout = JSON-RPC channel
+grep -nE "[0-9]+ tools" "$DT/README.md" "$DT/package.json"                    # advertised count vs reality
+node -p "require('$DT/package.json').files.join('\n')"; ls -d "$DT"/tools/*/  # files[] covers runtime dirs
+cd "$DT" && npm outdated; npm audit --omit=dev 2>/dev/null | tail -20
+```
+
+Also check: every tool has a description + `inputSchema`; token-heavy results (screenshots, UI trees) are truncated or file-backed; failures return an error result, not a throw; `CHANGELOG.md`, CI and tests exist.
+
+Output (plan band E):
+
+```
+| # | Axis | Finding | Source | Adaptation in the toolkit (file) | Effort | Impact | In plan? |
+|---|------|---------|--------|----------------------------------|--------|--------|----------|
+| 1 | Protocol | read-only tools carry no annotations | <spec link> | add `annotations` to the read-only tools in index.js | Low | Medium | Yes (P1) |
+| 2 | Peer servers | peer exposes <surface> | <repo link> | does not fit: outside the pipeline's phases | - | - | No |
+```
+
+Rules for this band:
+
+- Band-E work lands in the toolkit repo, never mirrored into this one. Shipping it is `multi-agent-sync` Step 3d.
+- A finding that changes the tool surface pairs with a pipeline-side item: bump the minimum toolkit version wherever a pipeline skill declares one.
+- If the current working directory IS the toolkit repo, skip band E and let bands A/B/C cover it.
+
 ## Step 1: SCAN
 
 ```
@@ -166,7 +216,7 @@ Each category is scored out of 10. Output format:
 
 ## Step 4: PLAN  -  one merged, prioritized table
 
-Merge all four bands into a single plan. Tag each row with its band (A best-practice / B bug / C improvement / D drift).
+Merge all five bands into a single plan. Tag each row with its band (A best-practice / B bug / C improvement / D drift / E dev-toolkit).
 
 ```
 | # | Priority | Band | Category | Item | Impact |
@@ -175,7 +225,8 @@ Merge all four bands into a single plan. Tag each row with its band (A best-prac
 | 2 | P0 | B | Testing | Fix nil-deref on empty response (src/y:42) | High |
 | 3 | P1 | A | CI/CD | Adopt matrix build (adapt: .github/workflows/ci.yml) | Medium |
 | 4 | P1 | D | Skills | Port upstream <plugin> 0.3.0 fixes into <localPath> | Medium |
-| 5 | P2 | C | DevEx | Rename npm scripts for consistency | Low |
+| 5 | P1 | E | Toolkit | Add read-only annotations to the dev-toolkit device tools | Medium |
+| 6 | P2 | C | DevEx | Rename npm scripts for consistency | Low |
 ```
 
 Priority levels:
@@ -187,13 +238,14 @@ Priority levels:
 
 After showing the plan, ask:
 
-> "I found X items (P0: N, P1: M, P2: K) across bugs, best-practices, improvements, and upstream drift. Shall I start developing?"
+> "I found X items (P0: N, P1: M, P2: K) across bugs, best-practices, improvements, upstream drift, and dev-toolkit practice. Shall I start developing?"
 
 Options:
 - "Yes, do all of them"
 - "Do only the P0 ones"
 - "Do only P0 + P1"
 - "Only the bugs (band B)"
+- "Only the dev-toolkit (band E)"
 - (the user can make a specific selection)
 
 **NEVER start developing without approval.**
@@ -204,6 +256,7 @@ Apply approved items in order:
 
 1. For each item:
    - Make the change (for band D, port the upstream diff into `localPath`, then bump that entry's `derivedFromVersion`)
+   - Band-E items are applied inside the toolkit repo, never mirrored here: edit there, re-run its gates (`node --check`, `tools/list` handshake, advertised tool count matching reality), commit there. Publishing is `multi-agent-sync` Step 3d.
    - Run the relevant tests
    - If successful, move to the next
    - If it fails, revert and notify the user
@@ -227,6 +280,8 @@ echo "Lint: PASS/FAIL"
 echo "Test: PASS/FAIL (X/Y passed)"
 ```
 
+If any band-E item was applied, verify the toolkit repo too: syntax-check every file it loads, handshake the server and confirm `tools/list` still answers, and confirm the advertised tool counts match the count the server reports.
+
 ## Step 8: ASK SYNC
 
 After all approved items are applied, ask:
@@ -234,7 +289,7 @@ After all approved items are applied, ask:
 > "Development complete. Shall I run multi-agent-sync?"
 
 Options:
-- "Yes" -> run the `/sync` command (full ecosystem sync)
+- "Yes" -> run the `/sync` command (full ecosystem sync  -  its Step 3d ships any band-E work in the toolkit repo)
 - "No" -> report and finish
 - "Only commit + push" -> push only the current repo without sync
 
@@ -247,6 +302,7 @@ If $ARGUMENTS is specified, focus on that band/category only:
 | `bugs` | Bug hunt only (band B) |
 | `best-practices` | Field research + adapted plan only (band A) |
 | `drift` | Upstream derived-skill drift only (band D) |
+| `dev-toolkit` | Companion MCP toolkit research + audit only (band E) |
 | `security` | Security analysis only |
 | `tests` | Test coverage and quality only |
 | `performance` | Performance optimization only |

package/pipeline/skills/shared/core/multi-agent-review/SKILL.md

@@ -46,7 +46,7 @@ Skip Phase 0-3 and review a diff only. Input shapes: a PR (`#N`, `repo#N`, GitHu
 
    | Platform | Trigger files | Catalog to load |
    |---|---|---|
-   | iOS | `**/Info.plist`, `**/PrivacyInfo.xcprivacy`, `**/*.entitlements`, `**/*App.swift`, `**/AppDelegate*.swift`, `**/SceneDelegate*.swift`, `**/project.pbxproj` | `pipeline/skills/shared/core/apple-archive-compliance/SKILL.md`  -  17 rules + ITMS refs |
+   | iOS | `**/Info.plist`, `**/PrivacyInfo.xcprivacy`, `**/*.entitlements`, `**/*App.swift`, `**/AppDelegate*.swift`, `**/SceneDelegate*.swift`, `**/project.pbxproj` | `pipeline/skills/shared/core/apple-archive-compliance/SKILL.md`  -  18 rules + ITMS refs |
    | Android | `**/AndroidManifest.xml`, `**/build.gradle(.kts)`, `**/proguard-rules.pro`, `**/network_security_config.xml` | `pipeline/skills/shared/core/google-play-compliance/SKILL.md`  -  21 rules + Play policy refs |
 
    It appends the catalog's `ruleID` + the Apple ITMS / Play policy ref to each finding:

package/pipeline/skills/shared/core/multi-agent-sync/SKILL.md

@@ -1,9 +1,9 @@
 ---
 name: multi-agent-sync
 language: en
-description: "One-shot sync of the entire multi-agent ecosystem: Claude Code, Copilot CLI, pipeline repo, and website."
+description: "One-shot sync of the entire multi-agent ecosystem: Claude Code, Copilot CLI, pipeline repo, website, and the dev-toolkit MCP server."
 user-invocable: true
-argument-hint: 'release | "change description"'
+argument-hint: 'release | dev-toolkit | "change description"'
 ---
 
 # Multi-Agent Sync
@@ -22,6 +22,7 @@ When invoked, it synchronizes all targets in order. It detects what changed, upd
 | 2 | Copilot CLI | `~/.copilot/copilot-instructions.md` + `~/.copilot/skills/` | <- from Claude |
 | 3 | multi-agent-pipeline repo | `~/multi-agent-pipeline/pipeline/` | <- from Claude (genericized) |
 | 4 | Website | `{owner}/{website-host}` | <- version + features |
+| 5 | dev-toolkit MCP server | resolved from `prefs.global.devToolkit` or the `mcpServers` registration | own repo: gate, commit, publish |
 
 ## Default Behavior (no argument)
 
@@ -29,11 +30,12 @@ Run all steps automatically:
 
 ```
 Step 1: DETECT      Compare timestamps, find stale targets
-Step 2: COPILOT     Claude Code -> Copilot CLI (instructions + 41 sub-command skills)
+Step 2: COPILOT     Claude Code -> Copilot CLI (instructions + 42 sub-command skills)
 Step 3: REPO        Claude Code -> pipeline repo (genericized, personal data scrub)
+Step 3d: DEV-TOOLKIT Companion MCP server -> detect movement, ship gates, commit + publish
 Step 4: WEBSITE     Version + phase/model counts -> {website-host} (i18n + projects.ts)
 Step 5: Commit      Commit + push all changed repos
-Step 6: Report      Summary: synced targets, changed files, deploy status
+Step 6: Report      Summary: synced targets, changed files, deploy status, dev-toolkit version
 ```
 
 If nothing is stale -> report "All targets up to date" and stop.
@@ -44,6 +46,7 @@ If nothing is stale -> report "All targets up to date" and stop.
 |-------|----------|
 | (no argument) | Full ecosystem sync (default) |
 | `release` | Full sync + version bump + tag + npm publish + website deploy |
+| `dev-toolkit` | Run Step 3d only: gate, commit and publish the companion MCP server |
 | `"change description"` | Apply the description to ALL targets at once |
 
 
@@ -90,6 +93,43 @@ If nothing is stale -> report "All targets up to date" and stop.
    - `~/.claude/settings.json`
 
 
+## Dev-Toolkit Sync (Step 3d)
+
+The companion MCP server (`dev-toolkit-mcp`) is its own repo with its own registry. Pipeline skills call its tools and several declare a minimum version, so when it moves it has to ship.
+
+**Resolution**: identical to `multi-agent-refactor` Step 0c  -  `prefs.global.devToolkit` first, then the `mcpServers` registration, then skip.
+
+**Detect movement**: dirty working tree, unpushed commits, or no `v<version>` tag for the version in `package.json`. Nothing moved -> report "up to date" and continue.
+
+**Ship gates** (a failure aborts this step only, with file + line; the rest of the sync continues).
+When the toolkit ships its own gate script (`npm run gates` / `scripts/gates.sh`), run that instead of the list below - the repo owns the definition, this skill owns the requirement. The list is the fallback, and the coverage the script must have:
+
+1. `node --check index.js` plus every `tools/**/*.js`.
+2. stdio handshake (`initialize` -> `notifications/initialized` -> `tools/list`) must answer with a non-zero tool count.
+3. That count must match every advertised count (`package.json` description, README header and per-family rows). Fix the docs, never the gate.
+4. `npm pack --dry-run` must list every `tools/*/` directory the server loads  -  a missing `files[]` entry publishes a broken package.
+5. `grep -rn "console\.log(" index.js tools/` must be empty: stdout carries the JSON-RPC frames, diagnostics go to `console.error`.
+6. Personal-data scan: no absolute `/Users/<name>` paths, no tokens, no corporate hostnames.
+7. Version contract: every pipeline-side minimum version must be satisfied by what is about to ship; a new tool a pipeline skill now needs -> bump that minimum in the same sync.
+
+**Version bump**: patch for fixes and docs, minor for a new tool, major for a removed or renamed tool.
+
+**Ship**: commit with that repo's own convention, tag `v<version>`, push with `--tags`, then publish to the registry from `publishConfig` using a throwaway userconfig  -  never edit `~/.npmrc`, never a bare `npm publish`. The token depends on the registry: `npm.pkg.github.com` needs a GitHub PAT with `write:packages` (logical key `github`), `registry.npmjs.org` needs the `npm` key.
+
+```bash
+NPMRC=$(mktemp); trap 'rm -f "$NPMRC"' EXIT
+REG=$(node -p "require('./package.json').publishConfig?.registry || 'https://registry.npmjs.org'")
+HOST=${REG#https://}; HOST=${HOST%/}
+case "$HOST" in npm.pkg.github.com*) KEY=github ;; *) KEY=npm ;; esac
+TOKEN=$(bash "$HOME/.claude/lib/credential-store.sh" get "$KEY")
+[ -n "$TOKEN" ] || echo "ABORT: no '$KEY' token - onboard it via /multi-agent:setup before publishing"
+printf '%s\n' "registry=$REG" "//$HOST/:_authToken=$TOKEN" > "$NPMRC"
+npm publish --userconfig "$NPMRC"
+```
+
+**Approval**: outside autopilot and outside `release`, ask first: commit + push / commit + push + publish / skip. Never ship unapproved band-E work from `multi-agent-refactor` silently.
+
+
 ## Website Sync (Step 4)
 
 Propagate the pipeline version, phase count, model count, and feature descriptions to the website.
@@ -124,9 +164,10 @@ When invoked with the `release` argument:
 4. VERSION       package.json version bump (patch/minor/major)
 5. Commit + TAG  git commit + git tag v{VERSION}
 6. PUSH          git push --tags -> release.yml auto-publish
-7. WEBSITE       Version + features -> {website-host}
-8. COPILOT       Copilot CLI instructions + skills sync
-9. Report        Summary: version, touched repos, deploy status
+7. DEV-TOOLKIT   Ship the companion MCP server if it moved (Step 3d gates, then publish)
+8. WEBSITE       Version + features -> {website-host}
+9. COPILOT       Copilot CLI instructions + skills sync
+10. Report       Summary: version, touched repos, deploy status
 ```
 
 
@@ -136,10 +177,10 @@ When invoked with the `release` argument:
 |-------------|-------------|
 | `~/.claude/commands/multi-agent/{cmd}.md` | `~/.copilot/skills/multi-agent-{cmd}/SKILL.md` |
 
-**41 commands are synced** (canonical inventory  -  must match `cross-cli-contract.md` section 1; drift = contract violation):
+**42 commands are synced** (canonical inventory  -  must match `cross-cli-contract.md` section 1; drift = contract violation):
 
 ```
-analysis, analysis-resolve, autopilot, build-optimize, channels, create-jira, dev,
+analysis, analysis-resolve, autopilot, build-optimize, channels, create-jira, design-check, dev,
 dev-autopilot, dev-local, dev-local-autopilot, diff-explain, finish, forget, garbage-collect,
 help, issue, jira, kill, language, local,
 local-autopilot, log, manual-test, prune-logs, purge, refactor, resume, review, review-issue, review-jira,
@@ -159,6 +200,7 @@ routines, save, scan, search, setup, stack, status, sync, test, uninstall, updat
 | `gh` CLI (personal) | `{owner}` gh auth (Keychain) |
 | `gh` CLI (work) | `${USER}_{work-gh-alias}` gh auth (Keychain) |
 | npm publish | `NODE_AUTH_TOKEN`  -  `GITHUB_TOKEN` in CI, Keychain PAT locally |
+| dev-toolkit publish (Step 3d) | `npm` logical Keychain key -> throwaway `--userconfig`, registry from that repo's `publishConfig` |
 
 ```bash
 gh auth switch --user {owner}  # for personal repos

package/pipeline/skills/shared/core/multi-agent-test/SKILL.md

@@ -39,6 +39,6 @@ Pass `$ARGUMENTS` through verbatim  -  the target doc picks the right test matri
 
 - **iOS**: Xcode + booted Simulator (`xcrun simctl list | grep Booted`)
 - **Android**: Android SDK + running emulator or USB device (`adb devices`)
-- **MCP**: `dev-toolkit` MCP server registered (tool names start with `mcp__dev_toolkit__*`)
+- **MCP**: `dev-toolkit` MCP server registered (tool names start with `mcp__dev-toolkit__*`)
 
 For the Phase 5 manual test mode (branch checkout + Xcode hint), use `multi-agent-manual-test` instead.

package/pipeline/skills/skills-index.md

@@ -3,7 +3,7 @@
 > Auto-generated by `pipeline/scripts/build-skills-index.mjs`  -  do not hand-edit.
 > Regenerate with `node pipeline/scripts/build-skills-index.mjs`.
 
-**189 skills** across 2 groups.
+**193 skills** across 2 groups.
 
 | Group | Name | Platform | Description |
 |-------|------|----------|-------------|
@@ -23,7 +23,7 @@
 | external | `app-store-changelog` |  -  | Generate user-facing App Store release notes from git history since the last tag. |
 | external | `app-store-optimization` |  -  | Optimize App Store product pages for search visibility and conversion. Use for App Store Optimization (ASO), keyword research, app name/subt |
 | external | `app-store-review` |  -  | Prepare for App Store review and prevent rejections. Covers App Store review guidelines, app rejection reasons, PrivacyInfo.xcprivacy privac |
-| core | `apple-archive-compliance` |  -  | Apple App Store Review compliance  -  wraps the dev-toolkit-mcp `ios_app_store_audit` tool (17-rule deep scan) with ITMS error code mapping  |
+| core | `apple-archive-compliance` |  -  | Apple App Store Review compliance  -  wraps the dev-toolkit-mcp `ios_app_store_audit` tool (18-rule deep scan) with ITMS error code mapping  |
 | external | `apple-on-device-ai` |  -  | Integrate on-device AI using Foundation Models framework, Core ML, and open-source LLM runtimes on Apple Silicon. Covers Foundation Models ( |
 | external | `architecture` |  -  | Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisi |
 | external | `authentication` |  -  | Implement iOS authentication flows with AuthenticationServices and LocalAuthentication. Use when building Sign in with Apple, passkey/WebAut |
@@ -95,12 +95,14 @@
 | core | `multi-agent-build-optimize` |  -  | Wrapper that dispatches to xcode-build-orchestrator on iOS repos. Benchmarks the current Xcode build, runs compilation / project / SPM analy |
 | core | `multi-agent-channels` |  -  | Multi-channel reporter  -  Jira/Confluence/Wiki/PR description. Multi-select channels + content, humanizer pass, reviewer-preserving Bitbuck |
 | core | `multi-agent-create-jira` |  -  | Create a standards-compliant Jira issue (Task / Bug / Story): asks the type, mines project conventions, drafts from a standard template with |
+| core | `multi-agent-design-check` |  -  | Mock-mode vs Figma design audit (iOS / Android, local-only). Pick repo + module, gate on mock support, enumerate every state driver into a c |
 | core | `multi-agent-dev` |  -  | Fast development mode: Init → Dev (Opus) → Test → Commit → Report. Analysis, planning, and review phases are skipped. |
 | core | `multi-agent-dev-autopilot` |  -  | Fastest mode: Dev (Opus) plus Autopilot. Init → Dev → Commit → Report with zero confirmations. |
 | core | `multi-agent-dev-local` |  -  | Fast mode + local  -  Init → Dev(Opus) → Commit → Report, no worktree. |
 | core | `multi-agent-dev-local-autopilot` |  -  | Fastest + local  -  Dev(Opus) + autopilot, no worktree, zero interaction. |
 | core | `multi-agent-diff-explain` |  -  | Map Phase 4 triage findings to branch diff lines. Read-only post-hoc command, used after review to answer 'which finding lines up with which |
 | core | `multi-agent-finish` |  -  | Continue already-done LOCAL work through the pipeline tail: Review → Build+Test → Commit/PR → Report (technical analysis + Jira test-scenari |
+| core | `multi-agent-forget` |  -  | Remove a saved /multi-agent routine (created by /multi-agent:save): deletes its local-only command and its registry entry. Asks which one an |
 | core | `multi-agent-garbage-collect` |  -  | Sweep leftover /tmp scratch (picker state, review diffs, channel payloads, analysis drafts) from past runs. Dry-run first; confirms before d |
 | core | `multi-agent-help` |  -  | Multi-agent pipeline usage guide  -  renders in EN or TR per prefs.global.outputLanguage (falls back to promptLanguage for backward compatib |
 | core | `multi-agent-issue` |  -  | List unassigned GitHub issues, pick one, auto-assign, and launch the multi-agent pipeline. |
@@ -113,17 +115,19 @@
 | core | `multi-agent-manual-test` |  -  | Switch to the active task's branch and prepare it for manual testing in Xcode. Phase 5 standalone (the UI Bug Hunter lives at multi-agent-te |
 | core | `multi-agent-prune-logs` |  -  | Delete per-task project logs under ~/.claude/logs/multi-agent (filter by age/project/task). Audit trail + metrics are preserved. Dry-run fir |
 | core | `multi-agent-purge` |  -  | ⚠️ Wipes every worktree, branch, log, and state file. Irreversible; asks for double confirmation. |
-| core | `multi-agent-refactor` |  -  | Analyse the project: extract adapted best-practices, hunt real bugs + improvement areas, check upstream drift of derived skills, draft one p |
+| core | `multi-agent-refactor` |  -  | Analyse the project: extract adapted best-practices, hunt real bugs + improvement areas, check upstream drift of derived skills, research th |
 | core | `multi-agent-resume` |  -  | Resume a stopped or failed task from the phase where it left off. |
 | core | `multi-agent-review` |  -  | Run parallel review on a branch diff or a Pull Request: 2 models on Claude Code (Fable + Sonnet), 3 models on Copilot CLI (GPT + Opus + Sonn |
 | core | `multi-agent-review-issue` |  -  | Assess whether a GitHub issue is ready for multi-agent development: fetch it, grade scope / acceptance criteria / repro / design / API / sta |
 | core | `multi-agent-review-jira` |  -  | Assess whether a Jira issue is ready for multi-agent development: fetch it, grade scope / acceptance criteria / repro / design / API / stack |
+| core | `multi-agent-routines` |  -  | List your saved /multi-agent routines (from /multi-agent:save) with what each one does, rendered in outputLanguage. |
+| core | `multi-agent-save` |  -  | Save a recurring job as a reusable /multi-agent:<name> command. Reviews the conversation + your CLAUDE.md for candidate routines, you pick o |
 | core | `multi-agent-scan` |  -  | Skill security scan: walks local skill directories against a tiered pattern catalog. |
 | core | `multi-agent-search` |  -  | Log search across every agent-log.md with smart ranking and filters. Optional --semantic flag queries the per-repo triage corpus. |
 | core | `multi-agent-setup` |  -  | First-run setup wizard: keychain token discovery, Git Identity onboarding, and pipeline preparation. |
 | core | `multi-agent-stack` |  -  | Select the active stack for this repo by enabling the matching marketplace plugin(s) in .claude/settings.json (ios/android/mobile/backend/fr |
 | core | `multi-agent-status` |  -  | Show every multi-agent task's ID, phase, branch, and status. |
-| core | `multi-agent-sync` |  -  | One-shot sync of the entire multi-agent ecosystem: Claude Code, Copilot CLI, pipeline repo, and website. |
+| core | `multi-agent-sync` |  -  | One-shot sync of the entire multi-agent ecosystem: Claude Code, Copilot CLI, pipeline repo, website, and the dev-toolkit MCP server. |
 | core | `multi-agent-test` |  -  | UI Bug Hunter  -  iOS Simulator (simctl) + Android Emulator (adb). Auto-detects platform. Screenshot + tap + analyze on the booted device. T |
 | core | `multi-agent-uninstall` |  -  | Uninstall the pipeline from Claude Code + Copilot CLI. Keychain access tokens are always left untouched; --all-data also clears pipeline set |
 | core | `multi-agent-update` |  -  | Update the pipeline to the latest version: git pull, install, migrate. |