@mmerterden/multi-agent-pipeline 14.2.2 → 15.0.0

package/install/copilot.mjs

@@ -24,11 +24,18 @@ import {
   wipeDir,
   writeFile,
 } from "./_common.mjs";
-import { copyExternalSkillsFiltered } from "./_platform-filter.mjs";
+import {
+  partitionExternalSkillsByPlugins,
+  writeExternalSkillsManifest,
+} from "./_platform-filter.mjs";
 import { DEV_ONLY_SCRIPTS, countDevOnlyFiles } from "./_dev-only-files.mjs";
 import { generateCopilotInstructions } from "./_copilot-instructions.mjs";
 import { legacyTrailingContent, mergeManagedBlock } from "./_managed-block.mjs";
-import { installAuthoredPluginSkills, pipelineOwnedSkillNames } from "./_plugin-skills.mjs";
+import {
+  installAuthoredPluginSkills,
+  pipelineOwnedSkillNames,
+  pluginsToDeliver,
+} from "./_plugin-skills.mjs";
 import { registerMcpServer } from "./_mcp-register.mjs";
 
 /**
@@ -357,16 +364,34 @@ function installSkills(opts) {
   }
 
   if (existsSync(sharedExternalSrc)) {
-    const { copied, skipped } = copyExternalSkillsFiltered(sharedExternalSrc, dest, {
-      platformFlag,
-      useSymlinks,
-    });
-    copilotSkillCount += copied;
-    if (skipped > 0) {
-      console.log(
-        `    -> --platform=${platformFlag} filter skipped ${skipped} external skill dir(s)`,
-      );
+    // Active-stack filter: Copilot has no plugin loader, so its local copy is the
+    // only stack-skill source it has - but it should still carry the SAME stack
+    // set the enabled plugins serve on Claude Code, not the whole catalog. The
+    // enabled set comes from ~/.claude/settings.json (pluginsToDeliver); the
+    // --platform flag stays as the fallback for machines without one.
+    const { names: enabled, source: selectionSource } = pluginsToDeliver(home, platformFlag);
+    const { keep, skipped } = partitionExternalSkillsByPlugins(sharedExternalSrc, enabled);
+    ensureDir(dest);
+    for (const name of keep) {
+      const src = join(sharedExternalSrc, name);
+      const dst = join(dest, name);
+      if (!useSymlinks) wipeDir(dst);
+      copyDir(src, dst, { useSymlinks });
+      copilotSkillCount += countFiles(src);
+    }
+    // Stale prune: a skill delivered by a previous, wider stack selection must
+    // leave when the selection narrows, or the old stack lingers forever.
+    for (const name of skipped) {
+      const stale = join(dest, name);
+      if (!existsSync(stale) || isDryRun()) continue;
+      try {
+        rmSync(stale, { recursive: true, force: true });
+      } catch {
+        /* non-fatal */
+      }
     }
+    writeExternalSkillsManifest(dest, keep);
+    console.log(`    -> stack filter (${selectionSource}): ${keep.length} kept, ${skipped.length} skipped`);
   }
 
   // The pre-migration figma-* skill copies are gone; the plugin owns component work

package/install/index.mjs

@@ -187,7 +187,9 @@ function printSummary(opts) {
   // hand-registered entry became the only reason it worked on any given machine.
   console.log("  For UI testing, the dev-toolkit MCP server is registered automatically:");
   if (forClaude) {
-    console.log("    Claude Code: claude mcp add --scope user dev-toolkit  (user scope, all projects)");
+    console.log(
+      "    Claude Code: claude mcp add --scope user dev-toolkit  (user scope, all projects)",
+    );
   }
   if (forCopilot) {
     console.log("    Copilot CLI: copilot mcp add dev-toolkit");
@@ -195,7 +197,9 @@ function printSummary(opts) {
   if (forCodex) {
     console.log("    Codex CLI:   codex mcp add dev-toolkit");
   }
-  console.log("    Skipped only when the host CLI is not on PATH - the command to run is printed above.");
+  console.log(
+    "    Skipped only when the host CLI is not on PATH - the command to run is printed above.",
+  );
   console.log("");
   console.log("  Uninstall everything: npx @mmerterden/multi-agent-pipeline uninstall");
   console.log("  (Personal access tokens in keychain are preserved.)");

package/install/templates/codex-instructions.md

@@ -62,7 +62,7 @@ failure this layout exists to prevent.
 
 Codex assembles every discovered skill's name + description into one prompt block
 and **silently drops entries when that block overflows**. The pipeline therefore
-contributes exactly **one** skill (`multi-agent`) and keeps its 42 sub-command
+contributes exactly **one** skill (`multi-agent`) and keeps every sub-command
 specs as reference files that cost nothing until read. Do not convert those specs
 into peer skills: doing so evicts other skills, including ones from installed
 plugins, with no error surfaced.

package/install/templates/copilot-instructions.md

@@ -245,7 +245,7 @@ Cost block reads `phase-tracker.sh tokens` accumulators × `cost-table.json` pri
 
 ## Stack Selection
 
-Stack skill sets ship as versioned plugins in the `multi-agent-plugins` marketplace. Selecting a stack enables the matching plugin(s) in the target repo's `.claude/settings.json` `enabledPlugins`; the `ai-common-engineering-toolkit` is always enabled alongside. There is no session-start auto-swap script. Select or change the stack with:
+Stack skill sets ship as versioned plugins in the `multi-agent-plugins` marketplace. Selecting a stack enables the matching plugin(s) in the target repo's `.claude/settings.json` `enabledPlugins`; the `ai-common-toolkit` is always enabled alongside. There is no session-start auto-swap script. Select or change the stack with:
 
 ```bash
 multi-agent-stack [ios|android|mobile|backend|frontend|fullstack|all]
@@ -302,8 +302,8 @@ if [ "$(jq '.projects | length' "$STATE_FILE")" -ge 2 ]; then
 fi
 ```
 
-Full contract: `~/.copilot/skills/multi-agent/refs/multi-repo-integration-build.md`
-(or on GitHub: https://github.com/mmerterden/multi-agent-pipeline/blob/main/pipeline/multi-agent-refs/multi-repo-integration-build.md)
+Full contract: https://github.com/mmerterden/multi-agent-pipeline/blob/main/pipeline/multi-agent-refs/multi-repo-integration-build.md
+(the Copilot install ships no local refs tree, so the contract lives on GitHub only)
 
 ## Permissions Expectation
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mmerterden/multi-agent-pipeline",
-  "version": "14.2.2",
+  "version": "15.0.0",
   "description": "8-phase AI development pipeline with full orchestration on Claude Code, Copilot CLI and Codex CLI. Analysis, planning, TDD, CLI-aware parallel review with consensus surfacing + Fable triage, default-FAIL evidence gates, secret + intent guards, per-phase cost ledger, persistent learnings memory, wiki generation, commit automation. Token-preserving uninstall.",
   "type": "module",
   "main": "index.js",
@@ -89,7 +89,6 @@
     "!pipeline/scripts/sync-parity-check.sh",
     "!pipeline/scripts/benchmark-phase-0.sh",
     "!pipeline/scripts/fixtures/**",
-    "!pipeline/scripts/test-gap-rules/**",
     "!pipeline/eval/**",
     "pipeline/scripts/smoke-schema-validation.sh",
     "pipeline/scripts/smoke-cross-cli-behavior.sh"

package/pipeline/commands/multi-agent/SKILL.md

@@ -78,6 +78,7 @@ Lib scripts (`~/.claude/lib/`):
 | `review-jira [KEY\|url]` | Grade a Jira issue's readiness for the pipeline (scope / AC / repro / design / API / stack), then post the gaps as a Jira comment. Read-only on code. |
 | `review-issue [#N\|repo#N\|url]` | Grade a GitHub issue's readiness for the pipeline, then post the gaps as an issue comment. Read-only on code. |
 | `analysis ["<feature>"]` | Standalone feature-spec analizi: Figma / Swagger / Confluence / Jira / repo girdileri sabit 7-bölümlük şablona dökülür, humanizer'dan geçer, Local/Confluence/Jira hedef(ler)ine post edilir. Worktree veya commit yok. Dev'e zincirleme yok. |
+| `complaint-analysis ["<run-name>"] [--file <path>] [<jira-id\|confluence-url> ...]` | Müşteri şikayeti triyajı: şikayetler (serbest metin / csv-xlsx-txt-json dosya / Jira issue / Confluence URL) redakte edilerek alınır, trxId/conversationId ile Graylog kanıtı çekilir, seçili client + BFF repolarında salt-okunur eşleştirme yapılır; verdict: client/bff (kök neden + citation + mevcut mimariyi referans alan fix planı + hazır dev prompt'u) veya core (core ekibine yönlendirme önerisi) veya insufficient-evidence. Rapor + Stop; worktree, commit, dev zinciri yok. |
 | `build-optimize` | iOS-only Xcode build performance wrapper. Vendored `xcode-build-orchestrator`'a dispatch eder; benchmark + compilation / project / SPM analyzer'lar + recommend-first plan `.build-benchmark/optimization-plan.md`. Non-iOS stack'lerde fail-fast. |
 | `channels [PR-url\|#N\|Jira-url\|Jira-id] [--channels pr,jira,confluence,wiki] [--content normal,test,auto-diff,note] [--message "..."]` | Post task report to multi-select channels (PR description, Jira comment, Confluence page, Wiki pages) with multi-select content sources. Humanizer pass per-channel. Bitbucket PR updates use reviewer-preserving PUT. Phase 7 delegates to this command; also invocable post-hoc for fixes made outside the pipeline. No worktree. |
 | `create-jira ["desc"] [figma-url] [swagger-url]` | Create a standards-compliant Jira issue: asks the type (**Task** / **Bug** / **Story**), mines the project's recent same-type issues for conventions (summary format, labels, priority, test-scenario style), detects the active sprint, drafts from a standard template with auto-sizing sections (Design Reference / API Contract / Screenshots appear only when their source is given), asks about unknown fields, then full draft preview + explicit approval before create. No worktree, no commits. |
@@ -120,6 +121,7 @@ This command uses lazy loading for token efficiency. Read the relevant sub-file
 | `review-jira` | `$HOME/.claude/commands/multi-agent/review-jira/SKILL.md` (loads `$HOME/.claude/multi-agent-refs/readiness-review.md`) |
 | `review-issue` | `$HOME/.claude/commands/multi-agent/review-issue/SKILL.md` (loads `$HOME/.claude/multi-agent-refs/readiness-review.md`) |
 | `analysis` | `$HOME/.claude/commands/multi-agent/analysis/SKILL.md` |
+| `complaint-analysis` | `$HOME/.claude/commands/multi-agent/complaint-analysis/SKILL.md` |
 | `build-optimize` | `$HOME/.claude/commands/multi-agent/build-optimize/SKILL.md` |
 | `local` | `$HOME/.claude/commands/multi-agent/local/SKILL.md` |
 | `local-autopilot` | `$HOME/.claude/commands/multi-agent/local-autopilot/SKILL.md` |

package/pipeline/commands/multi-agent/analysis/SKILL.md

@@ -505,9 +505,9 @@ For each `platform` in `state.analysisSpec.platforms[]`:
 
 2. **Per-platform markdown render**: for each platform in `state.analysisSpec.platforms[]`, concatenate the per-platform spec into one markdown file. Tables in pipe-syntax. Numbering uses plain `## 1.`, `## 2.`, ... - omitted sections do **not** create gaps. Visible numbering is sequential 1..N over the rendered set.
 
-3. **Humanizer pass (MANDATORY: actually invoke the `humanizer` skill on the rendered markdown - the punctuation grep alone does NOT satisfy this step)** (`technical-explanatory` tone for the scratch buffer; per-channel re-humanize happens in Phase 4 when actually emitting):
+3. **Humanizer pass (MANDATORY: actually invoke the `ai-common-toolkit:humanizer` skill on the rendered markdown - the punctuation grep alone does NOT satisfy this step)** (`technical-explanatory` tone for the scratch buffer; per-channel re-humanize happens in Phase 4 when actually emitting):
    ```
-   humanizer skill input:
+   ai-common-toolkit:humanizer skill input:
      language: <tr|en>
      tone: technical-explanatory
      stripFancyPunctuation: true
@@ -662,7 +662,7 @@ When `phase == "cancelled_at_pass_b_preview"`:
 | `~/.claude/lib/extract-conventions.sh` | Phase 1c convention extractor (7 pattern groups, JSON output, confidence levels) |
 | `~/.claude/lib/figma-screenshot.sh` | Phase 2b Tier 2 Figma image downloader (REST API, section drill, 2x scale PNG, manifest.json) |
 | `~/.claude/lib/md2confluence-v3.py` | Phase 4 Confluence dispatch (multipart attachments, `<ac:image>` injection, mermaid macro + fallback, tooltip footnote macro, punctuation gate) |
-| `$HOME/.claude/skills/humanizer/SKILL.md` | Phase 3 tone pass |
+| `ai-common-toolkit:humanizer` | Phase 3 tone pass |
 | 8-locale set (ar, de, en, es, fr, it, ru, tr) + localization-key naming (inline) | Section 10 localization generation |
 | `$HOME/.claude/multi-agent-refs/channels/confluence.md` | Phase 4 Confluence dispatch |
 | `$HOME/.claude/multi-agent-refs/channels/jira.md` | Phase 4 Jira dispatch |

package/pipeline/commands/multi-agent/analysis-resolve/SKILL.md

@@ -1,5 +1,5 @@
 ---
-description: "Resolve the Section 20 Risks and Open Questions of an analysis v3 document one row at a time. Proposes up to 3 source-labeled answer candidates per row (from evidence / from repo / AI reasoned), merges the chosen answer into the target body section, and updates the doc in place with a Section 23 changelog bump. Companion to /multi-agent:analysis - same Locked decisions apply (citation discipline, humanizer punctuation, no MCP, no auto-commit). Optional sibling propagation for per-platform file sets. Use when an analysis document's open questions and risks need answering row by row before development starts."
+description: "Resolve the Section 20 Risks and Open Questions of an analysis v3 document one row at a time: up to 3 source-labeled answer candidates per row (evidence / repo / AI reasoned), chosen answer merged into the target section, doc updated in place with a changelog bump. Same locked decisions as /multi-agent:analysis. Use when an analysis document's open questions need answering before development starts."
 description-tr: "Analiz v3 dokümanının Bölüm 20 Riskler ve Açık Sorular satırlarını tek tek çözer. Satır başına en fazla 3 kaynak-etiketli cevap adayı önerir (kanıttan / repodan / AI çıkarımı), seçilen cevabı ilgili gövde bölümüne işler ve dokümanı Bölüm 23 changelog artışıyla yerinde günceller. /multi-agent:analysis'in eşlikçisi - aynı Kilitli kararlar geçerli (alıntı disiplini, humanizer noktalama, MCP yok, otomatik commit yok). Platform bazlı dosya setleri için isteğe bağlı kardeş yayılımı."
 argument-hint: "[path/to/analysis/<feature>-<platform>.md] [--autonomous]"
 ---
@@ -121,7 +121,7 @@ For each open row in source order:
 | `$HOME/.claude/multi-agent-refs/analysis-template.md` | Section 20 / Section 23 table contracts, front-matter shape, omission re-flow |
 | `$HOME/.claude/multi-agent-refs/conventions-defaults.md` | `convention-fallback` default values per platform |
 | `~/.claude/lib/extract-conventions.sh` | fresh single-field extraction for convention-fallback candidates |
-| `$HOME/.claude/skills/humanizer/SKILL.md` | tone reference for longer merged fragments (short fragments only need the punctuation gate) |
+| `ai-common-toolkit:humanizer` | tone reference for longer merged fragments (short fragments only need the punctuation gate) |
 
 ## Notes
 

package/pipeline/commands/multi-agent/build-optimize/SKILL.md

@@ -40,7 +40,7 @@ Before dispatch, fail fast on non-iOS repos. Detect iOS context via the standard
 
 3. **Dispatch** to `xcode-build-orchestrator` via the Skill tool:
    ```
-   Skill(skill="xcode-build-orchestrator", args="")
+   Skill(skill="ai-ios-toolkit:xcode-build-orchestrator", args="")
    ```
    The orchestrator's Phase 1 (Analyze) runs `xcode-build-benchmark`, the three specialist analyzers, and writes `.build-benchmark/optimization-plan.md`. No project files are modified during Phase 1.
 
@@ -48,7 +48,7 @@ Before dispatch, fail fast on non-iOS repos. Detect iOS context via the standard
 
 5. **Phase 2 (apply + verify)** is initiated by the user. The wrapper does not auto-execute Phase 2 because the upstream contract requires explicit approval via the checkboxes in the plan file. When the user signals "implement the approved items", the wrapper dispatches to `xcode-build-fixer`:
    ```
-   Skill(skill="xcode-build-fixer", args="")
+   Skill(skill="ai-ios-toolkit:xcode-build-fixer", args="")
    ```
    The fixer applies only the approved changes and re-benchmarks for wall-clock delta verification.
 
@@ -62,13 +62,13 @@ Before dispatch, fail fast on non-iOS repos. Detect iOS context via the standard
 
 | Path | Reason |
 |------|--------|
-| `$HOME/.claude/skills/xcode-build-orchestrator/SKILL.md` | The orchestrator this wrapper dispatches to |
-| `$HOME/.claude/skills/xcode-build-benchmark/SKILL.md` | Baseline timing |
-| `$HOME/.claude/skills/xcode-compilation-analyzer/SKILL.md` | Swift compile hotspots |
-| `$HOME/.claude/skills/xcode-project-analyzer/SKILL.md` | Build settings / script phases / parallelism |
-| `$HOME/.claude/skills/spm-build-analysis/SKILL.md` | SPM graph + plugins |
-| `$HOME/.claude/skills/xcode-build-fixer/SKILL.md` | Apply approved fixes + re-benchmark |
-| `$HOME/.claude/skills/NOTICE-xcode-build-skills.md` | MIT attribution + upstream pin |
+| `ai-ios-toolkit:xcode-build-orchestrator` | The orchestrator this wrapper dispatches to |
+| `ai-ios-toolkit:xcode-build-benchmark` | Baseline timing |
+| `ai-ios-toolkit:xcode-compilation-analyzer` | Swift compile hotspots |
+| `ai-ios-toolkit:xcode-project-analyzer` | Build settings / script phases / parallelism |
+| `ai-ios-toolkit:spm-build-analysis` | SPM graph + plugins |
+| `ai-ios-toolkit:xcode-build-fixer` | Apply approved fixes + re-benchmark |
+| ai-ios-toolkit plugin NOTICE (xcode build skills) | MIT attribution + upstream pin |
 
 ## Notes
 

package/pipeline/commands/multi-agent/channels/SKILL.md

@@ -401,7 +401,7 @@ Full contract: [`$HOME/.claude/multi-agent-refs/channels/confluence.md`]($HOME/.
 
 **Wiki → Jira comment auto-link** (triad contract, preserved from v5.6): when the Wiki adapter writes pages AND `state.jiraId` is set AND `prefs.global.wikiToJiraComment === true`, also post a humanizer-passed summary of the wiki pages (component name + variant count + wiki URL) as an additional Jira comment on the same issue. Independent of the main Jira channel's comment  -  both can coexist. Full contract in `$HOME/.claude/multi-agent-refs/issue-jira-triad.md`.
 
-**If preconditions met (Case A):** scope multi-select prompt (Main page / iOS sub-page / Screenshots / Index updates / Other); adapter dispatched to the plugin skill `ai-ios-engineering-toolkit:figma-component-wiki` (or `ai-android-engineering-toolkit:figma-component-wiki`).
+**If preconditions met (Case A):** scope multi-select prompt (Main page / iOS sub-page / Screenshots / Index updates / Other); adapter dispatched to the plugin skill `ai-ios-toolkit:figma-component-wiki` (or `ai-android-toolkit:figma-component-wiki`).
 
 Full contract: [`$HOME/.claude/multi-agent-refs/channels/wiki.md`]($HOME/.claude/multi-agent-refs/channels/wiki.md)  -  all four `figma-config.wiki.mode` adapters (submodule / in-repo / github-wiki / separate-repo), full Case A scope menu, screenshot quadrant gate.
 

package/pipeline/commands/multi-agent/complaint-analysis/SKILL.md

@@ -0,0 +1,186 @@
+---
+description: "Customer-complaint triage. Ingests complaints (paste, csv/xlsx/txt/json file, Jira issue, Confluence URL), fetches Graylog evidence per trx/conversation id, correlates read-only against the selected client + BFF repos; per complaint: client/bff root cause + fix plan + dev prompt, or core routing recommendation, or insufficient-evidence. Report only, no dev chaining. Use when customer-reported errors need layer triage."
+description-tr: "Müşteri şikayeti / müşteri kaynaklı hata triyajı. Şikayetleri alır (serbest metin, csv/xlsx/txt/json dosya, Jira issue, Confluence URL), trxId/conversationId ile Graylog kanıtı çeker, seçilen client + BFF repolarıyla salt-okunur eşleştirir ve her şikayeti sınıflandırır: client / bff (bizim sorumluluğumuz, kök neden analizi) veya core (core ekibine yönlendirme önerisi) veya insufficient-evidence. Rapor üretip durur - branch, worktree, commit, PR veya dev zinciri yok."
+argument-hint: "[\"<run-name>\"] [--file <path>] [<jira-id | jira-url | confluence-url> ...]"
+---
+
+# multi-agent complaint-analysis - Customer Complaint Triage
+
+**Input**: $ARGUMENTS (optional run name, optional `--file <path>`, optional Jira ids / Jira URLs / Confluence URLs; remaining free text is treated as pasted complaints)
+
+Triage of customer-reported errors across the layers the team owns (client apps + BFFs). Per complaint: Graylog log evidence by trx/conversation id, read-only repo correlation, and a verdict. **Core failures get a routing recommendation, never a fix analysis.**
+
+**Side-effect contract**: may write a local markdown report, post a Confluence page, or add a Jira comment/description - but **never** creates branches, worktrees, commits, or PRs. Stops at the report.
+
+> **Language**: Per `$HOME/.claude/multi-agent-refs/rules.md` Language Application matrix - instruction prose stays English. `AskUserQuestion.label` and `header` stay English. `question` and `description` follow `outputLanguage`. The report body follows `outputLanguage`; Graylog excerpts, verdict tokens, and external payload metadata stay English.
+
+## Locked decisions (do not re-ask)
+
+1. **Graylog is primary evidence (deliberate departure).** `features/external-context-injection.md` declares Graylog advisory-only for the dev pipeline; in THIS command Graylog IS the evidence backbone. A per-complaint fetch failure still never halts the run, but that complaint's verdict is capped at `insufficient-evidence` - never fabricated.
+2. **Ids are never guessed.** A complaint with no trxId and no convId enters the Phase 0 Step 5 confirmation loop: the user supplies the id(s) or explicitly marks the complaint `skip-graylog`. Empty submit is not consent (`feedback_no-inferred-defaults-from-empty-answer`); re-ask.
+3. **Read-only ops command.** No worktree, branch, commit, PR, or dev chaining. Report + Stop.
+4. **Redaction before any output.** Complaint text is redacted at intake (`parse-complaints.sh`, default on). Jira / Confluence-sourced complaint text passes through the same redaction (`--stdin` mode) after fetch. Raw PII never enters state, drafts, or any dispatch target.
+5. **Core is a residual classification, not a repo.** Verdict `core` produces a routing recommendation only - no fix analysis, no core-repo grepping, no core code speculation.
+6. **Layer mapping is user-confirmed.** Name-based layer inference (Step 3b) is a proposal; the confirmation table must be approved before Phase 1.
+7. **Output default = Local file.** The Phase 4.5 picker keeps `Local file` pre-selected; Confluence and Jira are never default-selected.
+8. **Humanizer punctuation policy is non-negotiable.** No em-dash, en-dash, ellipsis, curly quotes, or section sign in any emitted text. Turkish diacritics are preserved verbatim - never ASCII-fold the prose.
+9. **Language split.** Report body follows `outputLanguage`; verdict tokens (`client:ios`, `bff:mobile-bff`, `core`, `insufficient-evidence`), Graylog evidence excerpts, and Confluence/Jira payload metadata stay English.
+10. **Verdict citation discipline.** Every `client`/`bff` verdict cites at least one Graylog message (timestamp + source) AND one repo evidence row (`file:line`). Anything less is `insufficient-evidence`. Every `core` verdict cites the Graylog message that names the upstream service.
+11. **One complaint batch per run.** Mixed batches spanning unrelated products are user error: surface it and ask to split.
+12. **No auto-commit.** The local report is written to the working tree; the user commits it themselves if they want.
+13. **Client/bff verdicts carry a development handoff.** Every `client`/`bff` verdict renders a fix plan grounded in the EXISTING architecture (the `repoEvidence[]` files are the reference: name the concrete files/components to touch, reuse-first, no invented structures) plus a ready-to-run dev prompt (English, one fenced block, `/multi-agent:dev`-compatible). The handoff is part of the report - this command still never runs dev itself (Locked 3). Core and insufficient-evidence verdicts never get a fix plan (Locked 5).
+
+## Steps
+
+### Phase 0 - Intake
+
+Sequential `AskUserQuestion` chain, answers land under `state.complaintSpec.*` (schema: `$HOME/.claude/schemas/complaint-analysis-spec.schema.json`). Step narration per `$HOME/.claude/multi-agent-refs/picker-contract.md`: print `<localized: "Step <i>/<n>: <what this step decides>">` before each picker; auto-resolved steps still print their breadcrumb.
+
+#### Step 0 - Language resolution (BLOCKING)
+
+Read `prefs.global.outputLanguage` (`tr` or `en`, default `tr`) before the first picker. Every `<localized: "...">` marker in this file is rendered in that language, never emitted literally.
+
+#### Step 1 - Run name
+
+From `$ARGUMENTS` quoted string if present, else default `complaints-<YYYYMMDD>` (announce, do not ask). Result: `state.complaintSpec.runName`.
+
+#### Step 2 - Account picker
+
+Reuse `$HOME/.claude/multi-agent-refs/_account-picker.md`. Needed for Graylog-adjacent Jira/Confluence fetches and dispatch; skipped only when the run is fully local (no Jira/Confluence input, local output only) - then `account: null`.
+
+#### Step 3 - Repo multi-select
+
+Reuse `$HOME/.claude/multi-agent-refs/_repo-picker.md` (multi-select via `~/.claude/lib/repo-cache.sh`). Guidance line in the question: <localized: "Select the client and BFF repos your team owns (e.g. ios / android / web / mobile-bff / web-bff). Core services are NOT selected - core is a triage outcome, not a repo.">
+
+#### Step 3b - Layer tagging (single confirmation table)
+
+Infer a layer per selected repo from its name (`ios|iphone` -> ios, `android` -> android, `web(?!.*bff)` -> web, `mobile.?bff|bff.?mobile` -> mobile-bff, `web.?bff|bff.?web` -> web-bff, else other). Present ONE AskUserQuestion with the full `repo -> layer` table in the question body: options `Approve mapping` / `Override rows`. On override, one follow-up per rejected row with the 6 layer options. Result: `state.complaintSpec.repos[] = {name, layer, localPath?, provider?}` (Locked 6).
+
+#### Step 4 - Complaint input (multi-source)
+
+Classify every `$ARGUMENTS` remainder and any pasted input via `~/.claude/lib/context-link-extractor.sh`, then collect per source type. If nothing was supplied, ask: <localized: "Paste the complaints, or give a file path (csv / xlsx / txt / json), a Jira issue, or a Confluence URL. Mixed input is fine.">
+
+| Source | Ingestion |
+|---|---|
+| File path (`--file` or detected) | `~/.claude/lib/parse-complaints.sh --file <path>` (format auto-detected; exit 5 = xlsx degrade -> surface `degradeReason`, ask for a CSV export path, re-run) |
+| Pasted free text | `parse-complaints.sh --stdin` (splits blocks, pre-fills ids via the shared label set) |
+| Jira id / URL | Fetch issue summary + description + comments via Jira REST (account token); concatenate as text blocks, pipe through `parse-complaints.sh --stdin` (Locked 4) |
+| Confluence URL | `~/.claude/lib/fetch-confluence.sh <url>`; page body paragraphs/table rows become text blocks, piped through `parse-complaints.sh --stdin` |
+
+Merge all outputs into one list, re-numbering ids `C-01..C-NN`. Result: `state.complaintSpec.input` + `state.complaintSpec.complaints[]`.
+
+#### Step 5 - Id confirmation loop (Locked 2)
+
+Render the parsed table (id, redacted excerpt <= 80 chars, trxId, convId, platformHint) to the user. For every complaint missing BOTH ids, one AskUserQuestion: <localized: "Complaint <id> has no trx/conversation id. Supply one, or skip Graylog for it?"> with options `Skip Graylog for this complaint` (-> `skipGraylog: true`) and Other for the id (`trx:<value>` / `conv:<value>`). Empty submit re-asks. Set `phase: "fetching_graylog"`.
+
+### Phase 1 - Graylog evidence fan-out
+
+For each complaint with at least one id and `skipGraylog: false`:
+
+```bash
+~/.claude/lib/fetch-graylog.sh --trx <trxId> --conv <convId>   # pass whichever exist
+```
+
+Record per complaint: `graylog: {status: ok|degraded|skipped, totalResults, degradeReason}` plus the top messages (timestamp, source, level, message excerpt) kept in working context for Phase 2/3. Failure handling:
+
+- Exit 0 with `degraded: true` -> `status: degraded`, keep the reason, continue.
+- Exit 2 / 3 / 6 (credential / auth / host) -> per `$HOME/.claude/multi-agent-refs/keychain.md` non-critical rule: warn ONCE (`WARN: Graylog unavailable (<reason>); remaining complaints proceed without log evidence.`), mark this and all remaining fetches `status: degraded`, continue. Never halt (Locked 1).
+- `skipGraylog: true` -> `status: skipped`.
+
+Set `phase: "correlating_repos"`.
+
+### Phase 2 - Repo evidence correlation (read-only)
+
+From each complaint's Graylog messages extract candidate signals: endpoint paths, error codes, exception class names, distinctive message templates, and the `source` service name. Then grep the selected repos (skip dirs: `.build`, `DerivedData`, `Pods`, `node_modules`, `.next`, `build/`, `.gradle`, `vendor/`):
+
+```bash
+grep -rn --include='*.swift' --include='*.kt' --include='*.ts' --include='*.tsx' --include='*.js' --include='*.java' -E "<signal>" "$REPO_PATH"
+```
+
+Bucket hits per complaint as `repoEvidence[] = {repo, layer, file, line, signal, matchKind: direct|partial}` (`direct` = exact endpoint/error-code/template match; `partial` = fuzzy/name-only). Grep only - no convention extraction, no Figma, no Swagger. Complaints with `status: degraded|skipped` still get a text-similarity pass (grep the complaint's distinctive nouns/error phrases), tagged `partial`. Set `phase: "triaging"`.
+
+### Phase 3 - Triage classification
+
+Per complaint, in order:
+
+| Condition | Verdict |
+|---|---|
+| Graylog error originates in an owned layer: signal matched `direct` in a selected repo, OR the failing `source` maps to an owned BFF | `client:<ios|android|web>` or `bff:<mobile-bff|web-bff>` + root-cause rationale + citations (Locked 10) |
+| Graylog shows the failure downstream of owned layers: `source` is an unowned core service, 5xx from an upstream nobody selected owns, no repo match | `core` + routing recommendation (below) |
+| No/degraded Graylog AND no direct repo signal | `insufficient-evidence` + open question row |
+
+**Routing recommendation** (core only, Locked 5): `{suspectedService: <Graylog source>, endpoint, errorCode, evidenceExcerpt (EN, redacted), suggestedQueue: prefs.projects[<project>].routing.coreTeamLabel ?? null, confidence}`.
+
+Verdict shape: `verdict: {category, layer, confidence: high|medium|low, rationale}`. Ambiguous client-vs-bff attribution lowers `confidence`, never invents evidence.
+
+**Development handoff (client/bff only, Locked 13)**: for each `client`/`bff` verdict, derive from the `repoEvidence[]` rows:
+
+- **Fix plan**: 2-5 numbered steps referencing the existing architecture by `file:line` - which service/view/handler to change, what to reuse (reuse-first: prefer extending the cited components over adding new ones), which tests to add. No speculative rewrites.
+- **Dev prompt**: one fenced English block the user can paste into `/multi-agent:dev` (or a Jira description): complaint summary, root cause, the cited files, the fix plan steps, and the acceptance check. Include the complaint id (`[C-NN]`) for traceability.
+
+Set `phase: "drafting"`.
+
+### Phase 4 - Draft, humanize, buffer
+
+1. Render the report per `$HOME/.claude/multi-agent-refs/complaint-analysis-template.md` (8 fixed sections; single-language body in `outputLanguage`; verdict tokens English per Locked 9) to `/tmp/complaint-analysis-<run-slug>-<UTC-iso8601>/report.md`. Store `outputs.draftDir`.
+2. **Humanizer pass (MANDATORY: actually invoke the `ai-common-toolkit:humanizer` skill; the punctuation grep alone does NOT satisfy this)** with `language: <tr|en>`, `tone: technical-explanatory`, `stripFancyPunctuation: true`. Diacritics preserved (Locked 8).
+3. Punctuation gate: `grep -P '[\x{2013}\x{2014}\x{2026}\x{201C}\x{201D}\x{2018}\x{2019}\x{00A7}]'` over the draft returns zero matches.
+4. Show the draft path + size to the user. Set `phase: "awaiting_output_decision"`.
+
+### Phase 4.5 - Output destination picker
+
+AskUserQuestion (multiSelect=true), `Local file` pre-selected (Locked 7):
+
+```
+header: "Output"
+question: <localized: "Where should the triage report be written?">
+options:
+  - label: "Local file"        (description: complaints/<run-name>.md in the primary repo's working tree)
+  - label: "Confluence page"
+  - label: "Jira"
+```
+
+Follow-ups: Confluence -> ask parent page (Other, LRU recents from `prefs.projects[<project>].confluenceUrls`); Jira -> pick from Step 4 Jira ids if any, else ask via Other. Result: `outputs.destinations[]`. Set `phase: "dispatching"`.
+
+### Phase 5 - Validate, dispatch, report. Stop.
+
+**Pre-dispatch gate (BLOCKING)**: `node $HOME/.claude/scripts/validate-complaint-doc.mjs <draft>` - front-matter, required sections, verdict tokens per triage row, routing entry per core verdict, punctuation, redaction-leak scan. Any ERROR blocks dispatch: fix the draft, re-validate.
+
+| Target | Action |
+|---|---|
+| Local | `cp` the draft to `complaints/<run-name>.md` in the primary repo's working tree. **No commit** (Locked 12). |
+| Confluence | Re-humanize with `formal-stakeholder` tone; post one page under the chosen parent via `$HOME/.claude/multi-agent-refs/channels/confluence.md` + `~/.claude/lib/md2confluence-v3.py`. |
+| Jira | Re-humanize with `informal-technical` tone; markdown -> wiki markup per `$HOME/.claude/multi-agent-refs/channels/jira.md`; post as a comment on the chosen issue (never close/transition the issue). |
+
+Then print the summary in `outputLanguage`: complaint count, verdict counts (`X client / Y bff / Z core / W insufficient-evidence`), degraded services, output paths/URLs. When any `core` verdict exists, add: <localized: "N complaint(s) route to the core team - see the routing section before forwarding.">
+
+**Stop. Do not chain into `/multi-agent:dev`. Do not open a worktree. Do not create a branch.** Set `phase: "done"`.
+
+### Resume contract
+
+`state.complaintSpec.phase`: `intake | fetching_graylog | correlating_repos | triaging | drafting | awaiting_output_decision | dispatching | reporting | done`.
+
+`/multi-agent:resume` at `awaiting_output_decision`: if `outputs.draftDir` still holds `report.md`, jump to Phase 4.5; if gone, re-render Phase 4 from state (evidence is retained). Earlier phases resume at their own boundary; Graylog results already in state are never re-fetched.
+
+## Reusable refs
+
+| Path | Reason |
+|---|---|
+| `~/.claude/lib/parse-complaints.sh` | Phase 0 Step 4 normalization + redaction (all formats + stdin) |
+| `~/.claude/lib/context-link-extractor.sh` | Phase 0 Step 4 input classifier (jira / confluence / graylog id labels) |
+| `~/.claude/lib/fetch-graylog.sh` | Phase 1 log evidence (`--trx` / `--conv`) |
+| `~/.claude/lib/fetch-confluence.sh` | Phase 0 Step 4 Confluence-sourced complaints |
+| `$HOME/.claude/multi-agent-refs/_account-picker.md`, `_repo-picker.md`, `picker-contract.md` | Phase 0 pickers |
+| `$HOME/.claude/multi-agent-refs/keychain.md` | Phase 1 non-critical credential handling |
+| `$HOME/.claude/multi-agent-refs/complaint-analysis-template.md` | Phase 4 report template (8 sections) |
+| `ai-common-toolkit:humanizer` | Phase 4 tone pass |
+| `$HOME/.claude/scripts/validate-complaint-doc.mjs` | Phase 5 pre-dispatch gate |
+| `$HOME/.claude/multi-agent-refs/channels/confluence.md`, `channels/jira.md`, `~/.claude/lib/md2confluence-v3.py` | Phase 5 dispatch |
+| `$HOME/.claude/schemas/complaint-analysis-spec.schema.json` | State contract |
+
+## Notes
+
+- Fully generic: hosts come from `prefs.global.hosts.*`, tokens from `prefs.global.keychainMapping.*`; no company name, host, or real repo name in this file.
+- `prefs.projects[<project>].routing.coreTeamLabel` is optional; when unset, `suggestedQueue` renders as `-` and the routing entry still stands.
+- If Confluence / Jira dispatch returns 401 / 403, surface the error and offer the Local fallback (the draft stays on disk).
+- The `complaints/` directory is not gitignored; the user commits manually if desired.

package/pipeline/commands/multi-agent/dev/SKILL.md

@@ -217,7 +217,7 @@ That is the whole list. Phase 0 (Init full picker), Phase 4 (Review), Phase 5 (U
 | Duration | ~10-15 min | ~7-10 min |
 ## Intake warnings (`--dev` family)
 
-Two checks belong at the top of every `--dev` run and are specified once in `$HOME/.claude/multi-agent-refs/phases/modes.md` "Intake warnings shared by the whole `--dev` family": an analysis document supplied to a mode that skips Analysis and Planning, and a branch that already carries the work (which wants `/multi-agent:ship`, not a second Dev pass). Read that section rather than reasoning about it from scratch.
+Two checks belong at the top of every `--dev` run and are specified once in `$HOME/.claude/multi-agent-refs/phases/modes.md` "Intake warnings shared by the whole `--dev` family": an analysis document supplied to a mode that skips Analysis and Planning, and a branch that already carries the work (which wants `/multi-agent:resume-local`, not a second Dev pass). Read that section rather than reasoning about it from scratch.
 
 ## Required: outward-facing payload contracts
 

package/pipeline/commands/multi-agent/dev-autopilot/SKILL.md

@@ -61,7 +61,7 @@ Phase 7: Report     → short terminal summary
 | Estimated duration | ~12 min | ~7 min | ~10 min | **~5 min** |
 ## Intake warnings (`--dev` family)
 
-Two checks belong at the top of every `--dev` run and are specified once in `$HOME/.claude/multi-agent-refs/phases/modes.md` "Intake warnings shared by the whole `--dev` family": an analysis document supplied to a mode that skips Analysis and Planning, and a branch that already carries the work (which wants `/multi-agent:ship`, not a second Dev pass). Read that section rather than reasoning about it from scratch.
+Two checks belong at the top of every `--dev` run and are specified once in `$HOME/.claude/multi-agent-refs/phases/modes.md` "Intake warnings shared by the whole `--dev` family": an analysis document supplied to a mode that skips Analysis and Planning, and a branch that already carries the work (which wants `/multi-agent:resume-local`, not a second Dev pass). Read that section rather than reasoning about it from scratch.
 
 ## Required: outward-facing payload contracts
 

package/pipeline/commands/multi-agent/dev-local/SKILL.md

@@ -106,7 +106,7 @@ Routes to the orchestrator with `--dev --local` flags. Apply the `$HOME/.claude/
 
 ## Intake warnings (`--dev` family)
 
-Two checks belong at the top of every `--dev` run and are specified once in `$HOME/.claude/multi-agent-refs/phases/modes.md` "Intake warnings shared by the whole `--dev` family": an analysis document supplied to a mode that skips Analysis and Planning, and a branch that already carries the work (which wants `/multi-agent:ship`, not a second Dev pass). Read that section rather than reasoning about it from scratch.
+Two checks belong at the top of every `--dev` run and are specified once in `$HOME/.claude/multi-agent-refs/phases/modes.md` "Intake warnings shared by the whole `--dev` family": an analysis document supplied to a mode that skips Analysis and Planning, and a branch that already carries the work (which wants `/multi-agent:resume-local`, not a second Dev pass). Read that section rather than reasoning about it from scratch.
 
 ## Required: outward-facing payload contracts
 

package/pipeline/commands/multi-agent/dev-local-autopilot/SKILL.md

@@ -47,7 +47,7 @@ Routes to the orchestrator with `--dev --local autopilot` flags. The pipeline co
 ```
 ## Intake warnings (`--dev` family)
 
-Two checks belong at the top of every `--dev` run and are specified once in `$HOME/.claude/multi-agent-refs/phases/modes.md` "Intake warnings shared by the whole `--dev` family": an analysis document supplied to a mode that skips Analysis and Planning, and a branch that already carries the work (which wants `/multi-agent:ship`, not a second Dev pass). Read that section rather than reasoning about it from scratch.
+Two checks belong at the top of every `--dev` run and are specified once in `$HOME/.claude/multi-agent-refs/phases/modes.md` "Intake warnings shared by the whole `--dev` family": an analysis document supplied to a mode that skips Analysis and Planning, and a branch that already carries the work (which wants `/multi-agent:resume-local`, not a second Dev pass). Read that section rather than reasoning about it from scratch.
 
 ## Required: outward-facing payload contracts
 

package/pipeline/commands/multi-agent/garbage-collect/SKILL.md

@@ -62,7 +62,7 @@ deletes nothing until you confirm.
    residue in the index (`.worktrees/{id}` recorded as a "Subproject commit"
    entry by a pre-guard `git add -A`), and a missing `.worktrees/` line in
    `.git/info/exclude`. Registered, healthy worktrees are NEVER touched  -
-   those belong to `/multi-agent:ship` / `/multi-agent:kill`.
+   those belong to `/multi-agent:resume-local` / `/multi-agent:kill`.
 
    - Output says `nothing to do` -> skip silently, no question.
    - Otherwise surface a second `AskUserQuestion` (in `outputLanguage`):

package/pipeline/commands/multi-agent/help/SKILL.md

@@ -91,7 +91,7 @@ Dedicated commands (same as flags above):
   /multi-agent:local-autopilot "task"           = multi-agent "task" --local autopilot
   /multi-agent:dev-local "task"                 = multi-agent "task" --dev --local
   /multi-agent:dev-local-autopilot "task"       = multi-agent "task" --dev --local autopilot
-  /multi-agent:ship [jira-id] [autopilot]     Continue already-done LOCAL work: Review → Build+Test → PR → Jira analysis + test scenarios (no dev)
+  /multi-agent:resume-local [jira-id] [autopilot]     Continue already-done LOCAL work: Review → Build+Test → PR → Jira analysis + test scenarios (no dev)
 
 ------------------------------------------------------------
 
@@ -102,6 +102,7 @@ Status & Resume:
   /multi-agent:resume [#id]   Resume a paused or failed task from where it stopped
   /multi-agent:kill [#id]     Stop task + delete worktree (logs preserved)
   /multi-agent:prune-logs     Delete per-task project logs (audit + metrics kept; age/project/task filters, dry-run first)
+  /multi-agent:prune-prompts  Zero-base prompt review: measure always-on instruction footprint, propose keep/trial/delete per rule (report first, apply on approval)
   /multi-agent:garbage-collect  Sweep leftover /tmp scratch from past runs (dry-run first)
   /multi-agent:purge          Worktree + logs  -  full reset (double confirm)
 
@@ -113,6 +114,7 @@ Post-Hoc & Side-Channel:
   /multi-agent:review-issue   Grade a GitHub issue's pipeline-readiness -> comment the gaps on it
   /multi-agent:analysis ["analysis-name"]  Feature-spec analysis (Figma + Swagger + Confluence + repos) → per-platform v3 doc (23-section Full / 7-section Lite)
   /multi-agent:analysis-resolve [doc]      Resolve Section 20 open questions of an analysis doc, one at a time with source-labeled candidates
+  /multi-agent:complaint-analysis ["run-name"] [--file path]  Customer-complaint triage: Graylog evidence per trx/conv id + read-only repo correlation → client/bff root cause + fix plan + dev prompt, or core routing recommendation
   /multi-agent:build-optimize iOS-only Xcode build perf wrapper → benchmark + analyze + recommend-first .build-benchmark/optimization-plan.md
   /multi-agent:create-jira ["desc"] [figma-url] [swagger-url]  Create a Jira Task/Bug/Story matching team conventions (asks type + mining + active sprint + auto-sizing sections + preview & approval)
   /multi-agent:diff-explain   Map a Phase 4 triage finding back to specific diff lines
@@ -132,13 +134,18 @@ Setup & Maintenance:
 
   /multi-agent:setup          First-run wizard  -  Keychain tokens + Git identity + language
   /multi-agent:language [en|tr]   Show or set outputLanguage (promptLanguage stays English)
-  /multi-agent:stack <id>     Select stack by enabling the matching marketplace plugin(s) (ios / android / mobile / backend / frontend / fullstack / all)
+  /multi-agent:stack [ids...]  Enable stack plugin(s); multi-select: ids together (ios backend) or no arg -> native picker (common always on)
   /multi-agent:sync           Sync ecosystem (Claude Code + Copilot CLI + pipeline + website + dev-toolkit MCP)
   /multi-agent:update         Pull latest pipeline + reinstall + run migrations
   /multi-agent:uninstall      Uninstall pipeline from every CLI (--all-data also clears settings + logs; Keychain tokens always intact, double confirm)
 
 ------------------------------------------------------------
 
+Stack plugin skills: call directly as ai-<stack>-toolkit:<skill>. Catalog:
+  ai-<stack>-toolkit:help. Active plugins per repo: /multi-agent:stack.
+
+------------------------------------------------------------
+
 Routines (your own reusable jobs):
 
   /multi-agent:save [name]    Save a recurring job as a reusable /multi-agent:<name> command
@@ -353,7 +360,7 @@ Dedicated komutlar (yukarıdaki flag'lerin eşdeğeri):
   /multi-agent:local-autopilot "task"           = multi-agent "task" --local autopilot
   /multi-agent:dev-local "task"                 = multi-agent "task" --dev --local
   /multi-agent:dev-local-autopilot "task"       = multi-agent "task" --dev --local autopilot
-  /multi-agent:ship [jira-id] [autopilot]     Lokalde biten işi sürdür: Review → Build+Test → PR → Jira teknik analiz + test senaryoları (dev yok)
+  /multi-agent:resume-local [jira-id] [autopilot]     Lokalde biten işi sürdür: Review → Build+Test → PR → Jira teknik analiz + test senaryoları (dev yok)
 
 ------------------------------------------------------------
 
@@ -364,6 +371,7 @@ Status & Resume:
   /multi-agent:resume [#id]   Duraklamış / hata almış task'ı kaldığı yerden devam ettir
   /multi-agent:kill [#id]     Task'ı durdur + worktree'yi sil (log'lar korunur)
   /multi-agent:prune-logs     Task bazlı proje log'larını sil (audit + metrics korunur; yaş/proje/task filtresi, önce dry-run)
+  /multi-agent:prune-prompts  Sıfır-tabanlı prompt incelemesi: sürekli yüklü talimat yükünü ölç, kural başına tut/dene/sil öner (önce rapor, onayla uygula)
   /multi-agent:garbage-collect  Geçmiş koşumların /tmp artıklarını süpür (önce dry-run)
   /multi-agent:purge          Worktree + log'lar  -  tam reset (çift onay)
 
@@ -375,6 +383,7 @@ Post-Hoc & Side-Channel:
   /multi-agent:review-issue   GitHub issue'nun pipeline'a hazırlığını değerlendir -> eksikleri yorum olarak ekle
   /multi-agent:analysis ["analysis-name"]  Feature-spec analizi (Figma + Swagger + Confluence + repolar) → platform başına v3 doküman (23 bölüm Full / 7 bölüm Lite)
   /multi-agent:analysis-resolve [doc]      Analiz dokümanının Bölüm 20 açık sorularını kaynak etiketli adaylarla teker teker çözer
+  /multi-agent:complaint-analysis ["run-adı"] [--file yol]  Müşteri şikayeti triyajı: trx/conv id ile Graylog kanıtı + salt-okunur repo eşleştirme → client/bff kök neden + fix planı + dev prompt'u, veya core'a yönlendirme önerisi
   /multi-agent:build-optimize iOS-only Xcode build performance wrapper → benchmark + analiz + recommend-first .build-benchmark/optimization-plan.md
   /multi-agent:create-jira ["açıklama"] [figma-url] [swagger-url]  Takım standartlarına uygun Jira Task/Bug/Story oluştur (tip sorar + convention mining + aktif sprint + auto-sizing bölümler + önizleme & onay)
   /multi-agent:diff-explain   Phase 4 triage bulgusunu diff satırlarına eşle
@@ -394,13 +403,19 @@ Setup & Maintenance:
 
   /multi-agent:setup              İlk kurulum sihirbazı  -  Keychain token + Git kimliği + dil
   /multi-agent:language [en|tr]   outputLanguage'ı göster veya ayarla (promptLanguage İngilizce kalır)
-  /multi-agent:stack <id>         Stack'i eşleşen marketplace plugin'i etkinleştirerek seç (ios / android / mobile / backend / frontend / fullstack / all)
+  /multi-agent:stack [ids...]     Stack plugin'lerini etkinleştir; çoklu seçim: id'ler yan yana (ios backend) ya da argümansız -> native picker (common hep açık)
   /multi-agent:sync               Ekosistemi senkronize et (Claude Code + Copilot CLI + pipeline + website + dev-toolkit MCP)
   /multi-agent:update             En son pipeline'ı çek + reinstall + migration çalıştır
   /multi-agent:uninstall          Pipeline'ı tüm CLI'lerden kaldır (--all-data ayar + logları da siler; Keychain token her zaman dokunulmaz, çift onay)
 
 ------------------------------------------------------------
 
+Stack plugin skill'leri: doğrudan ai-<stack>-toolkit:<skill> olarak çağrılır
+  (örn. ai-ios-toolkit:create-component). Lokal kopya ve sarmalayıcı yok. Katalog:
+  ai-<stack>-toolkit:help. Aktif plugin'ler repo bazında: /multi-agent:stack.
+
+------------------------------------------------------------
+
 Rutinler (kendi tekrar eden işlerin):
 
   /multi-agent:save [ad]          Sık yaptığın bir işi yeniden kullanılabilir /multi-agent:<ad> komutu olarak kaydet

package/pipeline/commands/multi-agent/ios-coding-standard/SKILL.md

@@ -9,9 +9,9 @@ allowed-tools: Skill, Bash, Read, Edit, Write, AskUserQuestion
 
 **Input**: $ARGUMENTS  -  optionally a module name or path. When absent, Phase 1 discovers and asks.
 
-This routine is the **procedure**. The rules live in the `ios-coding-standard` skill, whose registry is
+This routine is the **procedure**. The rules live in the `ai-ios-toolkit:ios-coding-standard` skill, whose registry is
 `references/rules.yml` and whose teaching doc is `references/STANDARD.md`. Load that
-skill first; it is installed on every host and carried by the iOS stack plugin, so
+skill first; Claude Code loads it from the iOS stack plugin, Copilot/Codex from their local copy, so
 there is one registry rather than a copy per CLI. Never restate a rule here  -  cite its ID. A rule that is not in the
 registry is not a rule; if the audit needs one, propose it as `status: proposed` and say so.