@mmerterden/multi-agent-pipeline 20.2.1 → 20.3.0

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

@@ -1,15 +1,17 @@
 ---
 description: "Multi-channel reporter  -  Jira/Confluence/Wiki/PR description/Board status. Multi-select channels + content, humanizer pass, reviewer-preserving Bitbucket PR PUT, GitHub Projects v2 board status move. Phase 5 delegates to this skill; users can invoke post-hoc by Jira ID / PR URL / branch."
 description-tr: "Çok kanallı raporlayıcı - Jira/Confluence/Wiki/PR açıklaması/Board durumu. Çoklu kanal + içerik seçimi, humanizer geçişi, reviewer'ı koruyan Bitbucket PR PUT, GitHub Projects v2 board durum taşıma. Faz 5 bu skill'e delege eder; Jira ID / PR URL / branch ile sonradan da çağrılabilir."
-argument-hint: '<Jira-id | PR-url | #N | Jira-url> [--channels pr,jira,confluence,wiki,board] [--content normal,technical,test,auto-diff,note] [--message "..."] [--message-file path] [--board-status <key>] [--dry-run] [--append] [--ready]'
+argument-hint: '[Jira-id | PR-url | #N | Jira-url] [--channels pr,jira,confluence,wiki,board] [--content normal,technical,test,auto-diff,note] [--message "..."] [--message-file path] [--board-status <key>] [--dry-run] [--append] [--ready]'
+parameters: [{"name":"target","kind":"text"},{"name":"--channels","kind":"enum","repeat":true,"enum":["pr","jira","confluence","wiki","board"]},{"name":"--content","kind":"enum","repeat":true,"enum":["normal","technical","test","auto-diff","note"]},{"name":"--message","kind":"text"},{"name":"--message-file","kind":"path"},{"name":"--board-status","kind":"text"},{"name":"--dry-run","kind":"flag"},{"name":"--append","kind":"flag"},{"name":"--ready","kind":"flag"}]
+gui: form
+destructive: false
+confirm: none
 allowed-tools: Read, Write, Edit, Bash, Grep, WebFetch, AskUserQuestion
 ---
 
 # /multi-agent channels  -  Multi-Channel Reporter
 
 > **TLDR**  -  Single entry point for posting task reports to external channels. Supports Jira, Confluence, Wiki (component-only), and PR description updates. Multi-select channels × multi-select content sources. Phase 5 of the pipeline delegates to this command; users can also invoke it post-hoc by Jira ID / PR URL / branch.
->
-> Replaces the old `enrich` command  -  all enrich capabilities (diff auto-summarize, manual mode, reviewer-preserving Bitbucket PR PUT) preserved and extended with two additional channels.
 
 **Claude Code invocation:** `/multi-agent:channels <target>`
 **Copilot CLI invocation:** `multi-agent-channels <target>` (top-level command, dash-separated per Copilot no-namespace convention)
@@ -31,8 +33,6 @@ allowed-tools: Read, Write, Edit, Bash, Grep, WebFetch, AskUserQuestion
 /multi-agent:channels PROJ-12345 --dry-run                  # preview, no POST
 ```
 
-Target resolution is identical to the pre-existing enrich flow  -  any of the 6 forms above works.
-
 ## Flow
 
 `resolve target → fetch context → menu (or flags) → generator → humanizer → approval → dispatch → summary`. Channels: Jira comment, Confluence page, Wiki pages, PR description, Board status (GitHub Projects v2).
@@ -127,7 +127,7 @@ Then 3b renders:
 
 **Why auto-tick:** the user JUST saw the summary and is likely sending it somewhere  -  otherwise they would have stopped before running `/multi-agent:channels`. Auto-tick matches the 80% case; the 20% case (preview was enough, no remote post needed) is a single keystroke to uncheck.
 
-**Autopilot interaction (Step 4):** when `state.autopilot === true`, autopilot still pauses at channels (documented exception to zero-interaction contract). The Work Summary preview renders in-line before the menu, same as normal mode.
+**Autopilot interaction (Step 4):** `state.autopilot === true` still pauses at channels (documented exception to zero-interaction contract), preview in-line. Under `MULTI_AGENT_UNATTENDED=1` it posts nothing: `$HOME/.claude/multi-agent-refs/features/unattended-security.md`.
 
 #### Step 3b  -  Channel + content picker
 
@@ -328,7 +328,7 @@ Skipped in exactly two cases:
 
 | Case | Why |
 |---|---|
-| Autopilot (`state.autopilot === true` or `MULTI_AGENT_AUTOPILOT=1`) | Explicit consent for side-effect creation  -  posts directly with prefs/flag selections, zero interaction |
+| Autopilot (`state.autopilot === true` or `MULTI_AGENT_AUTOPILOT=1`), attended | Explicit consent for side-effect creation: posts directly with prefs/flag selections |
 | `--dry-run` | Already prints without posting; a question would be redundant |
 
 **Preview render** (one block per selected channel, final body after humanizer  -  shown in readable Markdown, channel-specific markup conversion happens after approval).
@@ -413,7 +413,7 @@ Full contract: [`$HOME/.claude/multi-agent-refs/channels/confluence.md`]($HOME/.
 
 **Default target column:** `inReview`  -  read from `figmaConfig.github.fieldOptions.status.inReview` (the option ID, e.g. `bdb0d8ef`). Other column targets (e.g. `done`, `bugfix`) overridable via flag `--board-status <key>` where `<key>` matches a key under `fieldOptions.status`.
 
-**Token:** `prefs.global.keychainMapping.github_projects` (preferred  -  must include `project,read:project` scopes). Fallback chain: `keychainMapping.github` → standard key `${USER}_Github_Access_Token`. Resolve via `~/.claude/lib/credential-store.sh get <key>` (cross-platform  -  delegates to macOS Keychain / Linux libsecret / Windows Credential Manager). Token must NOT be passed on the CLI  -  export as `GH_TOKEN` env var only (per memory rule on token leakage).
+**Token:** `prefs.global.keychainMapping.github_projects` (preferred  -  must include `project,read:project` scopes). Fallback chain: `keychainMapping.github` → standard key `${USER}_Github_Access_Token`. Resolve via `~/.claude/lib/credential-store.sh get <key>` (reads the macOS Keychain). Token must NOT be passed on the CLI  -  export as `GH_TOKEN` env var only (per memory rule on token leakage).
 
 **Item lookup:** the issue's project item ID is fetched via GraphQL `repository.issue(number).projectItems(first:5)` filtered to `project.id === figmaConfig.github.projectV2Id`. If the issue is not yet in the project, dispatch silently no-ops with reason `"issue not on board"` in the summary.
 
@@ -536,7 +536,7 @@ Progress emission on Copilot (no native TaskCreate UI): `bash ~/.copilot/scripts
   → resolves → PROJ-67890
   → prints Jira + PR body preview to stdout, no POST
 
-/multi-agent:channels --message "root: PNR empty, UI silent. fix: length>0 guard in HomeVC.m"
+/multi-agent:channels --message "root: order id empty, UI silent. fix: length>0 guard in HomeVC.m"
   → auto-diff from cwd+branch PR + user note combined
   → posts to default channels (PR + Jira)
 ```

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

@@ -2,6 +2,10 @@
 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> ...]"
+parameters: [{"name":"name","kind":"text"},{"name":"--file","kind":"path"},{"name":"sources","kind":"text","repeat":true}]
+gui: form
+destructive: false
+confirm: none
 ---
 
 # multi-agent complaint-analysis - Customer Complaint Triage
@@ -128,7 +132,7 @@ Set `phase: "drafting"`.
 
 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 (required: 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: `node $HOME/.claude/scripts/validate-complaint-doc.mjs <draft>` reports no banned-punctuation error. It checks the policy in Node, so the same result holds on macOS, Linux and Windows; `grep -P` is absent from BSD grep and would never run there.
+3. Punctuation gate: `node $HOME/.claude/scripts/validate-complaint-doc.mjs <draft>` reports no banned-punctuation error. It checks the policy in Node; `grep -P` is absent from BSD grep and would never run.
 4. Show the draft path + size to the user. Set `phase: "awaiting_output_decision"`.
 
 ### Phase 4.5 - Output destination picker

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

@@ -2,6 +2,10 @@
 description: "Create a standards-compliant Jira issue (Task / Bug / Story): asks the type, mines project conventions, drafts from a standard template with auto-sizing sections, full preview + explicit approval before create. Use when a Jira Task, Bug or Story has to be written to the project's own conventions."
 description-tr: "Standartlara uygun Jira issue oluşturur (Task / Bug / Story): türü sorar, proje konvansiyonlarını çıkarır, otomatik boyutlanan bölümlerle standart şablondan taslak hazırlar, oluşturmadan önce tam önizleme + açık onay alır."
 argument-hint: "[\"<free-text description>\"] [figma-url] [swagger-url]  -  all optional, asked interactively when missing"
+parameters: [{"name":"description","kind":"text"},{"name":"figma-url","kind":"text"},{"name":"swagger-url","kind":"text"}]
+gui: form
+destructive: false
+confirm: none
 ---
 
 # multi-agent create-jira  -  Standards-Compliant Jira Issue Creator

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

@@ -2,6 +2,10 @@
 description: "Mock-mode vs Figma design audit (iOS / Android, local-only). Pick repo + module, gate on mock support, enumerate every state driver into a countable target set, build Debug in a worktree, launch in mock mode, fetch Figma variants, compare each pixel + px-spacing + typography + color, and export a side-by-side annotated report (HTML + PDF + Confluence) to ~/DesignChecks. A coverage gate fails the run when a target is neither audited nor skipped with a reason."
 description-tr: "Mock-mod vs Figma tasarım denetimi (iOS / Android, yalnızca lokal). Repo + modül seç, mock desteğini geçitle, her state sürücüsünü sayılabilir bir hedef kümesine çıkar, worktree'de Debug derle, mock modda aç, Figma varyantlarını çek, her varyantı piksel + px-boşluk + tipografi + renk düzeyinde karşılaştır, yan yana annotasyonlu raporu (HTML + PDF + Confluence) ~/DesignChecks altına aktar. Bir hedef ne denetlenmiş ne de gerekçeyle atlanmışsa kapsam geçidi koşuyu başarısız sayar."
 argument-hint: '[scope]  -  empty = whole module; screen name; screen@variant; Figma URL(s); --resume'
+parameters: [{"name":"scope","kind":"text"},{"name":"--resume","kind":"flag"}]
+gui: form
+destructive: false
+confirm: none
 allowed-tools: Agent, Bash, Read, Write, Edit, Glob, Grep, TaskCreate, TaskUpdate, AskUserQuestion, Skill, mcp__claude_ai_Figma__get_metadata, mcp__claude_ai_Figma__get_design_context, mcp__claude_ai_Figma__get_screenshot, mcp__multi-agent-toolkit__design_mock_detect, mcp__multi-agent-toolkit__design_scenario_inventory, mcp__multi-agent-toolkit__design_mock_launch, mcp__multi-agent-toolkit__design_ui_geometry, mcp__multi-agent-toolkit__design_visual_compare, mcp__multi-agent-toolkit__design_report, mcp__multi-agent-toolkit__ios_list_devices, mcp__multi-agent-toolkit__ios_boot_device, mcp__multi-agent-toolkit__ios_launch_app, mcp__multi-agent-toolkit__ios_terminate_app, mcp__multi-agent-toolkit__ios_screenshot, mcp__multi-agent-toolkit__ios_tap, mcp__multi-agent-toolkit__ios_swipe, mcp__multi-agent-toolkit__ios_type_text, mcp__multi-agent-toolkit__ios_open_url, mcp__multi-agent-toolkit__ios_get_ui_tree, mcp__multi-agent-toolkit__ios_status_bar, mcp__multi-agent-toolkit__ios_set_appearance, mcp__multi-agent-toolkit__ios_set_locale, mcp__multi-agent-toolkit__ios_xcodebuild, mcp__multi-agent-toolkit__ios_xcresult, mcp__multi-agent-toolkit__android_list_devices, mcp__multi-agent-toolkit__android_screenshot, mcp__multi-agent-toolkit__android_tap, mcp__multi-agent-toolkit__android_swipe, mcp__multi-agent-toolkit__android_type_text, mcp__multi-agent-toolkit__android_open_url, mcp__multi-agent-toolkit__android_launch_app, mcp__multi-agent-toolkit__android_stop_app
 ---
 
@@ -25,16 +29,16 @@ The scope decides which **inventory targets** (Phase 0 step 5) the run must audi
 | Form | Example | Scope |
 |------|---------|-------|
 | empty / `module` | `/multi-agent:design-check` | Every target in the module's inventory |
-| screen name | `boarding-pass` | Every target whose `screen` matches (case/separator-insensitive) |
-| `screen@variant` | `boarding-pass@expired` | One target |
-| target id | `scenario-case:boardingpassoutcome-expired` | One target, exactly |
+| screen name | `order-status` | Every target whose `screen` matches (case/separator-insensitive) |
+| `screen@variant` | `order-status@expired` | One target |
+| target id | `scenario-case:orderstatusoutcome-expired` | One target, exactly |
 | Figma URL(s) | `https://figma.com/design/...?node-id=1-2` | Only the frames those URLs name |
 | `--resume` | `/multi-agent:design-check --resume` | The unaudited remainder of the most recent run for this repo + module |
 | combinations | `seat-map summary@semi-success` | Union of the above, space- or newline-separated |
 
-Multiple forms may be combined. A scope that matches **no** inventory target is an error, not an empty run: print the closest inventory ids and halt.
+A scope that matches **no** inventory target is an error, not an empty run: print the closest inventory ids and halt.
 
-**Whole-module is the default, and it is meant to finish.** The inventory prices each target (`cost: relaunch | in-app`) and batches them into a run `plan`, so a 50-target module is typically about a dozen relaunches rather than fifty  -  a full audit is one sitting, not a project. Scope exists for resuming an interrupted run and for re-checking one screen after a fix, **not** for trimming an audit down to what feels affordable. The coverage gate applies to the **scoped** target set, so a deliberate scoped run is never penalised for out-of-scope targets, and `--resume` closes the remainder.
+**Whole-module is the default, and it is meant to finish.** The inventory prices each target (`cost: relaunch | in-app`) and batches them into a run `plan`, so a 50-target module is typically about a dozen relaunches rather than fifty. Scope exists for resuming an interrupted run and for re-checking one screen after a fix, **not** for trimming an audit down to what feels affordable. The coverage gate applies to the **scoped** target set, so a deliberate scoped run is never penalised for out-of-scope targets, and `--resume` closes the remainder.
 
 ## Pipeline
 
@@ -73,7 +77,7 @@ Every Phase 0 / Phase 2 decision uses a native `AskUserQuestion` picker per `pic
 
 ## Phase 0 - Init, Feasibility Gate & Inventory
 
-0. **MCP CURRENCY GATE (first, before anything expensive)** - an MCP stdio server publishes its tool list once at `initialize` and never re-reads the code, so a session connected to a server process that started before the last update keeps serving the OLD tool list while still reporting "connected". Discovering that after a Debug build and a device drive wastes the whole run and produces a report missing the very checks this spec relies on.
+0. **MCP CURRENCY GATE (first, before anything expensive)** - an MCP stdio server publishes its tool list once at `initialize` and never re-reads the code, so a session connected to a server process that started before the last update keeps serving the OLD tool list while still reporting "connected". Finding that out after a Debug build wastes the whole run.
 
    Assert both halves before continuing:
 
@@ -106,7 +110,7 @@ for l in sys.stdin:
 
 1. **Repo picker** - reuse `$HOME/.claude/multi-agent-refs/_repo-picker.md`. The account picker is skipped (Figma token is user-supplied, no Jira/GitHub fetch happens) unless Confluence export is enabled, in which case resolve the Confluence token via `account-resolver.sh`.
 2. **Module / dev-context picker** - reuse `$HOME/.claude/multi-agent-refs/_dev-context.md`. Auto-suggest submodules from `.gitmodules` (`submodule-detector.sh`); the user selects the single module to audit (multi-module allowed - each is audited independently).
-3. **Platform detect** - `.xcodeproj` / `Package.swift` → iOS; `build.gradle*` → Android (same markers as `phase-0-init.md`). Persist `state.platform`.
+3. **Platform detect** - `.xcodeproj` / `Package.swift` → iOS; `build.gradle*` → Android (same markers as `phase-0-init.md`). Persist `state.designCheck.platform`.
 4. **MOCK FEASIBILITY GATE** - run against the selected module path:
    ```
    mcp__multi-agent-toolkit__design_mock_detect({ repo_path: "<module path>", platform: "<ios|android>",
@@ -119,14 +123,15 @@ for l in sys.stdin:
 5. **SCENARIO INVENTORY (this is the audit's target set)**:
    ```
    mcp__multi-agent-toolkit__design_scenario_inventory({ repo_path: "<module path>", platform,
+     targets_file:      <config inventory.targetsFile>,
      extra_launch_args: <config inventory.extraLaunchArgs>,
      extra_targets:     <config inventory.extraTargets>,
      ignore_targets:    <config inventory.ignoreTargets> })
    ```
    Returns `targets[]` - each `{ id, kind, label, screen, driver, cost, evidence }` - plus `plan[]`, `relaunchCount`, `groups[]`, `byKind`, `byCost`, `ignored[]`, `truncated`, `scanStrategy`. Kinds: `launch-arg`, `scenario-case`, **`prefix-code`** (a mock repository branching on the prefix of the reference the user types - usually the LARGEST group, and the one a selector-only search misses entirely), `code-scenario`, `fixture`, `deep-link`.
 
-   This list, not the agent's reading of the code and not what the UI happens to expose to tapping, is what the run is measured against. Persist verbatim to `state.designCheck.inventory`.
-   - `targetCount: 0` → warn that no state driver was found and that only the default launch state can be audited; a `debug-only` project legitimately lands here.
+   This list, not the agent's reading of the code or what the UI exposes to tapping, is what the run is measured against. Persist verbatim to `state.designCheck.inventory`.
+   - `targetCount: 0` → warn that no state driver was found and that only the default launch state can be audited; a `debug-only` project lands here.
    - `truncated: true` → the inventory hit its cap, so the target set is INCOMPLETE. Say so now, and pass `coverage.truncatedInventory: true` in Phase 4 so the gate fails rather than reporting a clean percentage of a partial denominator. Narrow the scope to a screen and work through the module in `--resume` steps.
    - `ignored[]` non-empty → list what the config dropped, so a stale `ignoreTargets` cannot quietly shrink the audit.
 6. **Scope resolve** - intersect `$ARGUMENTS` (grammar above) with `inventory.targets`. Persist `state.designCheck.scope = { argument, targetIds[] }`.
@@ -136,7 +141,7 @@ for l in sys.stdin:
 8. **Report dir** - create `~/DesignChecks/{repo}__{module}/{UTC-timestamp}/` (and `assets/` inside it) now, and persist it as `state.designCheck.reportDir`. Phase 3 writes captures, comparison images, and `run-state.json` into it, so it must exist before driving starts - not at export time. This is report output, not a worktree; $HOME is intended here.
 9. **Worktree** - build the Debug app in an isolated worktree so the user's tree is untouched. Follow the `phase-0-init.md` Step 6 worktree location convention exactly: `{projectRoot}/.worktrees/{taskId}` with `taskId` = `DC-<shortId>`, **never under $HOME** (the `.worktrees` segment is fixed, not a preference). Stale-lock heal (`git worktree prune`) + residue guard (`.worktrees/` in `.git/info/exclude`) first. Local mode is not offered - the audit always uses a worktree checkout of the current branch's HEAD (no fetch/push).
 
-Persist `agent-state.json` with `taskId`, `mode: "design-check"`, `platform`, `projectRoot`, `worktreePath`, `module`, `designCheck`.
+Persist `agent-state.json` with `taskId`, `mode: "design-check"`, `projectRoot`, `worktreePath` and `designCheck` (which carries `module` and `platform`).
 
 ## Phase 1 - Build & Launch (mock)
 
@@ -202,7 +207,7 @@ While a target's state is on screen, also capture the **sub-states reachable fro
 
 For each capture: `ios_screenshot` (save PNG into the Phase 0 report dir) + `mcp__multi-agent-toolkit__design_ui_geometry` (live boxes + screen size) → append to `state.designCheck.captured[]` with the target id and a human label. **Persist `state` and `run-state.json` after every capture**, so a run that dies mid-way resumes from where it stopped instead of starting over.
 
-If a target cannot be reached, record it immediately as `{ id, reason }` in `state.designCheck.skipped[]` with a concrete reason ("scenario picker not present in this build", "needs a live PNR", "crashes on launch: <symbol>"). "Requires a scenario / prefix / launch-arg" is **not** a reason - that is a description of the work, and the work is this phase's job.
+If a target cannot be reached, record it immediately as `{ id, reason }` in `state.designCheck.skipped[]` with a concrete reason ("scenario picker not present in this build", "needs a live order", "crashes on launch: <symbol>"). "Requires a scenario / prefix / launch-arg" is **not** a reason - it describes the work, which is this phase's job.
 
 ### 3.2 Match each capture → Figma frame (auto)
 

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

@@ -2,6 +2,10 @@
 description: "Map Phase 3 triage findings to branch diff lines. Read-only post-hoc command, used after review to answer 'which finding lines up with which code change'. Use when a review finding has to be traced to the exact lines that caused it."
 description-tr: "Faz 3 triyaj bulgularını branch diff satırlarına eşler. Review sonrası kullanılan salt-okunur komut: hangi bulgu hangi kod değişikliğine denk geliyor sorusunu cevaplar."
 argument-hint: "[#task-id | --triage <path> | --state <path>] [--branch <name>] [--base <name>]"
+parameters: [{"name":"task","kind":"run-id"},{"name":"--triage","kind":"path"},{"name":"--state","kind":"path"},{"name":"--branch","kind":"branch"},{"name":"--base","kind":"branch"}]
+gui: form
+destructive: false
+confirm: none
 ---
 
 # multi-agent diff-explain  -  Phase 4 Triage to Diff Bridge

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

@@ -3,6 +3,10 @@ description: "Health check for the installed pipeline: layout, preferences, cred
 description-tr: "Kurulu pipeline için sağlık kontrolü: yerleşim, tercihler, kimlik bilgileri, hook'lar ve host yetenekleri; her biri tek uygulanabilir adımla. Çıkış kodu verdiktin kendisi."
 allowed-tools: Bash, Read
 argument-hint: "[--probe] [--explain] [--json] [--list-checks]  -  optional; --probe also makes one network request per configured service"
+parameters: [{"name":"--probe","kind":"flag"},{"name":"--explain","kind":"flag"},{"name":"--json","kind":"flag"},{"name":"--list-checks","kind":"flag"}]
+gui: button
+destructive: false
+confirm: none
 not-for: scan, setup
 ---
 

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

@@ -1,7 +1,11 @@
 ---
 description: "Send one message to the maintainer: a bug, an idea or a question. Only the text you type is sent - no logs, no repo names, no paths. Shows the payload and asks before sending."
 description-tr: "Bakımcıya tek mesaj gönderir: hata, fikir ya da soru. Yalnızca yazdığın metin gider - log yok, repo adı yok, yol yok. Göndermeden önce içeriği gösterip onay ister."
-argument-hint: "\"<message>\" [bug | idea | question]  -  with no argument, you are asked for the text"
+argument-hint: "[\"<message>\"] [bug | idea | question]  -  with no argument, you are asked for the text"
+parameters: [{"name":"message","kind":"text"},{"name":"category","kind":"enum","enum":["bug","idea","question"]}]
+gui: form
+destructive: false
+confirm: none
 ---
 
 # multi-agent feedback  -  tell the maintainer

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

@@ -2,6 +2,10 @@
 description: "Remove a saved /multi-agent routine (created by /multi-agent:save): deletes its local-only command and its registry entry. Asks which one and confirms. Use when a saved routine is no longer wanted and should be removed."
 description-tr: "Kaydedilmiş bir /multi-agent rutinini (/multi-agent:save ile oluşturulan) siler: local-only komutunu ve registry kaydını kaldırır. Hangisini soracak ve onay alacak."
 argument-hint: "[name]  -  routine to remove; asked if omitted"
+parameters: [{"name":"name","kind":"text"}]
+gui: form
+destructive: true
+confirm: required
 allowed-tools: Bash, Read, AskUserQuestion
 ---
 

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

@@ -2,6 +2,10 @@
 description: "Sweep leftover /tmp scratch (picker state, review diffs, channel payloads, analysis drafts), worktree residue (orphan .worktrees dirs, gitlink index entries) and offloaded tool payloads under .multi-agent/refs/ from past runs. With --abandoned, also reaps runs that stopped and were never picked back up, stashing any uncommitted work. Dry-run first; confirms before deleting. Use when scratch files from earlier runs need clearing out, or when stopped runs are holding worktrees."
 description-tr: "Geçmiş çalışmalardan kalan /tmp scratch'ini (picker durumu, review diff'leri, kanal payload'ları, analiz taslakları), worktree kalıntılarını (sahipsiz .worktrees klasörleri, gitlink index kayıtları) ve .multi-agent/refs/ altındaki offload edilmiş araç çıktılarını süpürür. --abandoned ile durup bir daha dönülmemiş koşuları da toplar, commit edilmemiş işi stash'ler. Önce dry-run; silmeden önce onay alır."
 argument-hint: "[--older-than=<minutes>] [--abandoned [--days=N]] [--yes]  -  dry-run unless confirmed"
+parameters: [{"name":"--older-than","kind":"text"},{"name":"--abandoned","kind":"flag"},{"name":"--days","kind":"text"},{"name":"--yes","kind":"flag"}]
+gui: button
+destructive: true
+confirm: required
 ---
 
 # multi-agent garbage-collect  -  Sweep /tmp Scratch

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

@@ -2,6 +2,10 @@
 description: "Build and query this repo's code graph: a deterministic, LLM-free map of symbols, imports and references used to narrow Phase 1's Explore scope and to keep the knowledge base current. Read-only on code, costs no API tokens. Use when a task needs to know where something lives or what depends on it before reading files."
 description-tr: "Bu repo'nun kod grafiğini kurar ve sorgular: sembolleri, import'ları ve referansları LLM'siz, deterministik biçimde haritalar. Faz 1'in Explore kapsamını daraltmak ve bilgi tabanını güncel tutmak için kullanılır. Kodda salt-okunur, API maliyeti yok."
 argument-hint: "[build | refresh | ask \"<question>\" | affected \"<symbol>\" | report | status]"
+parameters: [{"name":"action","kind":"text"}]
+gui: form
+destructive: false
+confirm: none
 ---
 
 # multi-agent graph  -  code graph build and query

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

@@ -1,6 +1,10 @@
 ---
 description: "Multi-agent pipeline usage guide  -  renders in EN or TR per prefs.global.outputLanguage (falls back to promptLanguage for backward compatibility). Use when asked what the pipeline can do, which mode to pick, or what a command means."
 description-tr: "Multi-agent pipeline kullanım kılavuzu - prefs.global.outputLanguage'e göre EN veya TR render edilir (geriye uyumluluk için promptLanguage'e düşer)."
+parameters: []
+gui: hidden
+destructive: false
+confirm: none
 ---
 
 # multi-agent help
@@ -79,10 +83,10 @@ Pipeline (after Phase 0)  -  shown as visual cards in terminal:
 
 Modes:
 
-Four pipeline entries:
+Pipeline entries:
 
   /multi-agent "task"                  Worktree
-  /multi-agent:autopilot "task"        Worktree, no questions, always Full
+  /multi-agent:autopilot "task"        Worktree, no questions
 
   Phase 0 Step 5b asks where the branch lives; there is no flag for it.
   autopilot skips every confirmation INCLUDING the plan gate and the workspace
@@ -107,6 +111,7 @@ Status & Resume:
   /multi-agent:autopilot-on   Continuous mode on this machine: pick repos, labelled items run to a PR
   /multi-agent:autopilot-status  Running, queued, awaiting an answer, today's PRs
   /multi-agent:autopilot-off  Stop picking work up (running work finishes; --now stops it)
+  /multi-agent:serve          Contract server for a client: 127.0.0.1, token, stops when idle
 
 Post-Hoc & Side-Channel:
 
@@ -117,11 +122,12 @@ Post-Hoc & Side-Channel:
   /multi-agent:review-issue   Grade a GitHub issue's pipeline-readiness -> comment the gaps on it
   /multi-agent:analysis ["name"]  Feature-spec analysis (Figma + Swagger + Confluence + repos). Asks the standard first: global (23-section dev handoff) or corporate (IG→UC→FG requirements doc). Stack optional; References built from the evidence record
   /multi-agent:analysis-resolve [doc]      Resolve Section 20 open questions of an analysis doc, one at a time with source-labeled candidates
+  /multi-agent:research <id>  Research an item's gaps in tracker, docs and repo before asking; a gate decides what closed
   /multi-agent:review-analysis [doc]  Review a written analysis; findings cite the rule they break
   /multi-agent:analysis-jira [doc]    A final analysis -> a Jira story tree; coverage two-way, existing nodes skipped
-  /multi-agent:complaint-analysis ["run-name"]  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:complaint-analysis ["run-name"]  Customer-complaint triage: Graylog evidence per trx/conv id + read-only repo correlation → root cause + fix plan, or core routing
   /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:create-jira ["desc"] [figma-url] [swagger-url]  Create a Jira Task/Bug/Story matching team conventions (type, sprint, preview + approval)
   /multi-agent:diff-explain   Map a Phase 3 triage finding back to specific diff lines
   /multi-agent:graph         Build and query the repo code graph (symbols, imports, references), LLM-free
   /multi-agent:search         Cross-task log search with smart ranking; --semantic queries triage corpus
@@ -130,7 +136,7 @@ Post-Hoc & Side-Channel:
   /multi-agent:doctor         Would a run work here? Layout, prefs, credentials, hooks; exit code is the verdict
   /multi-agent:refactor       Best practices + bug hunt + upstream drift + toolkit MCP research -> one plan, approval, dev + sync
   /multi-agent:refactor backlog  Decide the friction already recorded about the pipeline itself, nothing re-derived
-  /multi-agent:store-ready [repo] [flags]  Pre-submission store readiness, iOS + Android, local-only: three symmetric gates per platform plus the running-app sweep. A skipped gate is never a pass. Validates only, never uploads.
+  /multi-agent:store-ready [repo] [flags]  Pre-submission store readiness, iOS + Android, local-only; a skipped gate is never a pass; never uploads.
   /multi-agent:testflight-validation [repo] [--ipa=|--archive=]  iOS-pinned alias of :store-ready. Same three gates, one implementation.
   /multi-agent:ios-coding-standard [module]  Audit an iOS module against the 99-rule coding-standard registry -> remediation
                               plan + one-page onboarding summary -> hand off to /multi-agent. Read-only, never edits source.
@@ -144,6 +150,7 @@ Setup & Maintenance:
   /multi-agent:route-off      Disarm routing and KEEP the rules, so route-on does not re-ask
   /multi-agent:route-status   What is armed, which rule applies where, and the limit: subagents stay on Anthropic
   /multi-agent:stack [ids...]  Enable stack plugin(s); multi-select: ids together (ios backend) or no arg -> native picker (common always on)
+  /multi-agent:scaffold <stack> <name>  New project from the toolkit's scaffold skill; green before the first commit, no remote
   /multi-agent:sync           Sync ecosystem (Claude Code + Copilot CLI + pipeline + website + 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, memory + knowledge; tokens always intact)
@@ -153,8 +160,7 @@ Setup & Maintenance:
 Plugins & tools (called directly, no wrappers):
 
   Stack plugins    ai-<stack>-toolkit:<skill>, e.g. ai-ios-toolkit:create-component
-                   Catalog: ai-<stack>-toolkit:help   Enable per repo: /multi-agent:stack
-                   common + analyst are always on; the rest follow the repo's stack.
+                   Catalog: ai-<stack>-toolkit:help   Enable per repo: /multi-agent:stack (common + analyst always on)
   Toolkit MCP      multi-agent-toolkit  -  80+ tools for a RUNNING app, no pipeline run needed:
                    ios_* / android_* (launch, tap, screenshot, ui tree, logs, crashes,
                    locale, dark mode), web_*, design_* (Design Check above), and the
@@ -196,8 +202,7 @@ UI Testing (standalone  -  not part of pipeline phases):
   /multi-agent:test-dynamic-type     Large text size test
   /multi-agent:test-screenshots [tr] App Store screenshot set in a locale (default tr)
 
-  The scenario-tag form still works and is not deprecated  -  each command above is
-  an alias for it.
+  The scenario-tag form still works; each command above is its alias.
 
   /multi-agent:test "dark mode" | "accessibility" | "dynamic type" | "screenshot <lang>"
 
@@ -218,8 +223,8 @@ Design Check (mock-mode vs Figma, local-only):
   /multi-agent:design-check                Whole-module audit: enumerate every state driver into a countable
                                            target set, build Debug in a worktree, drive each in mock mode,
                                            diff against its Figma frame, export HTML+PDF to ~/DesignChecks.
-  /multi-agent:design-check <screen>       Scope to one screen (e.g. boarding-pass).
-  /multi-agent:design-check <screen@var>   Scope to one variant (e.g. boarding-pass@expired).
+  /multi-agent:design-check <screen>       Scope to one screen (e.g. order-status).
+  /multi-agent:design-check <screen@var>   Scope to one variant (e.g. order-status@expired).
   /multi-agent:design-check <figma-url...> Scope to the frame(s) those URLs name.
   /multi-agent:design-check --resume       Audit what the last run for this repo+module left unaudited.
   # COVERAGE GATE: every target is audited or skipped WITH a concrete reason; anything else reports
@@ -270,8 +275,6 @@ Examples:
   # Full pipeline with Jira (key configured during setup)
   /multi-agent "MOBILE-12345"
 
-  # GitHub issue, fast mode, local
-
   # Interactive launchers  -  browse and pick
   /multi-agent:jira                    # Pick from my Jira issues
   /multi-agent:issue                   # Pick from unassigned GitHub issues
@@ -287,7 +290,6 @@ Examples:
 
   # Create a Jira issue that matches team conventions (preview + approval before create)
   /multi-agent:create-jira "Profile screen empty state" https://figma.com/design/abc?node-id=1-2
-  /multi-agent:create-jira "Login crash on iOS 17, see attached log"
 
 ------------------------------
 
@@ -331,7 +333,7 @@ Pipeline (Phase 0'dan sonra)  -  terminalde görsel kart olarak görünür:
   Phase 0:   Init       -> Yukarıdaki 8 adım
   Phase 1:   Plan       -> Stack tespiti + codebase taraması, task kırılımı, mimari
                           inceleme, Plan Onay Kapısı (Opus; max 2 clarification turu,
-                          sadece Tam + etkileşimli  -  Kısa'da plan yok)
+                          sadece etkileşimli  -  autopilot'ta soracak kimse yok)
   Phase 2:   Dev        -> TDD: test -> kod -> build (Sonnet) + build queue, sonra Verify
                           çıkış kapısı: build, lint, test, sır taraması. Build koşu başına
                           BİR kez çalışır, log'u Review'a devreder
@@ -344,11 +346,10 @@ Pipeline (Phase 0'dan sonra)  -  terminalde görsel kart olarak görünür:
 
   Autopilot Phase 5'teki channels menüsünde HER ZAMAN durur (30 dk timeout → session temiz biter).
 
-  Pipeline derinliği Faz 0 Adım 7.5'te sorulur, bayrakla geçilmez:
-    Tam     Plan -> Dev(Sonnet) -> Review -> Commit -> Report
-    Kısa    Dev(Opus, kendi kendine yeten) -> Review -> Commit -> Report
-  Kısa yalnız Faz 1'i atlar; Review ASLA atlanmaz. taskType'a göre önerilir:
-  bugfix/chore -> Kısa, feature/refactor/component -> Tam. Autopilot her zaman Tam koşar.
+  Tek pipeline. Her mod kendi faz setinin tamamını koşar:
+    Plan -> Dev(Sonnet) -> Review -> Commit -> Report
+  Bir koşunun maliyeti, kanıt oluşmadan alınan bir cevaba değil, görevin
+  taşıdığı kanıta göre belirlenir.
 
   Her adım loglanır. Herhangi bir fazdaki hata -> pause -> resume ile devam et.
 
@@ -356,13 +357,13 @@ Pipeline (Phase 0'dan sonra)  -  terminalde görsel kart olarak görünür:
 
 Modlar:
 
-Dört pipeline girişi:
+Pipeline girişleri:
 
   /multi-agent "task"                  Worktree var
-  /multi-agent:autopilot "task"        Worktree var, soru yok, her zaman Tam
+  /multi-agent:autopilot "task"        Worktree var, soru yok
 
   Faz 0 Adım 5b branch'in nerede yaşayacağını sorar; bayrağı yok.
-  autopilot plan kapısı ve derinlik sorusu dahil her onayı atlar, otomatik
+  autopilot plan kapısı ve çalışma alanı sorusu dahil her onayı atlar, otomatik
   commit/PR açar  -  İSTİSNA: Faz 5 channels menüsü, o her zaman durur.
 
   /multi-agent:resume [#id|jira-id] [autopilot]       Yarım kalan işi sürdür: duran koşu ya da arkasında koşu olmayan branch (Review → Commit/PR → Report)
@@ -383,6 +384,7 @@ Status & Resume:
   /multi-agent:autopilot-on   Bu makinede sürekli mod: repo seç, etiketli maddeler PR'a kadar koşar
   /multi-agent:autopilot-status  Koşan, sıradaki, cevap bekleyen, bugünkü PR'lar
   /multi-agent:autopilot-off  Yeni madde alma (koşan iş biter; --now onu da durdurur)
+  /multi-agent:serve          İstemci için sözleşme sunucusu: 127.0.0.1, token, boşta durur
 
 Post-Hoc & Side-Channel:
 
@@ -393,11 +395,12 @@ 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). Önce standardı sorar: global (23 bölümlük geliştirme dokümanı) veya kurumsal (IG→UC→FG gereksinim dokümanı). Stack opsiyonel; Referanslar kanıt kaydından üretilir
   /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:research <id>  Maddenin boşluklarını sormadan önce tracker, doküman ve repoda araştırır; neyin kapandığına gate karar verir
   /multi-agent:review-analysis [doc]  Yazılmış analizi review eder; bulgular ihlal edilen kuralı gösterir
   /multi-agent:analysis-jira [doc]    Nihai analiz -> Jira story ağacı; kapsam iki yönlü kontrol edilir, var olan düğümler atlanır
-  /multi-agent:complaint-analysis ["run-adı"]  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:complaint-analysis ["run-adı"]  Müşteri şikayeti triyajı: trx/conv id ile Graylog kanıtı + salt-okunur repo eşleştirme → kök neden + fix planı, veya core'a yönlendirme
   /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:create-jira ["açıklama"] [figma-url] [swagger-url]  Takım standartlarına uygun Jira Task/Bug/Story oluştur (tip, sprint, önizleme + onay)
   /multi-agent:diff-explain   Phase 3 triage bulgusunu diff satırlarına eşle
   /multi-agent:graph         Repo kod grafiğini kur ve sorgula (semboller, import'lar, referanslar), LLM'siz
   /multi-agent:search         Task log'larında akıllı arama; --semantic triage corpus'unu sorgular
@@ -406,7 +409,7 @@ Post-Hoc & Side-Channel:
   /multi-agent:doctor         Burada bir koşu çalışır mı? Yerleşim, prefs, kimlik bilgileri, hook'lar; çıkış kodu kararı verir
   /multi-agent:refactor       Uyarlanmış best-practice + bug avı + upstream-drift + multi-agent-toolkit MCP araştırması -> tek plan, onay, dev + sync
   /multi-agent:refactor backlog  Pipeline'ın kendisi hakkında kaydedilmiş sürtünmeyi karara bağlar, sıfırdan türetmez
-  /multi-agent:store-ready [repo] [flags]  Yükleme öncesi store hazırlığı, iOS + Android, yalnızca lokal: platform başına 3 simetrik kapı artı çalışan-app sweep'i. Atlanan kapı asla pass sayılmaz. Sadece doğrular, asla yüklemez.
+  /multi-agent:store-ready [repo] [flags]  Yükleme öncesi store hazırlığı, iOS + Android, yalnızca lokal; atlanan kapı asla pass sayılmaz; asla yüklemez.
   /multi-agent:testflight-validation [repo] [--ipa=|--archive=]  :store-ready'nin iOS alias'ı. Aynı 3 kapı, tek implementasyon.
   /multi-agent:ios-coding-standard [modül]  Bir iOS modülünü 99 kurallık kodlama-standardı registry'sine göre denetler -> düzeltme
                               planı + tek sayfalık onboarding özeti -> /multi-agent'a devreder. Read-only, kaynağı hiç düzenlemez.
@@ -420,6 +423,7 @@ Setup & Maintenance:
   /multi-agent:route-off      Yönlendirmeyi kapatır, kuralları SAKLAR; route-on aynı şeyi tekrar sormaz
   /multi-agent:route-status   Ne açık, hangi kural nerede geçerli, ve sınır: subagent'lar Anthropic'te kalır
   /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:scaffold <stack> <ad>  Toolkit'in scaffold skill'i ile yeni proje; ilk commit'ten önce yeşil, uzak repo yok
   /multi-agent:sync               Ekosistemi senkronize et (Claude Code + Copilot CLI + pipeline + website + multi-agent-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, log, hafıza + bilgi tabanını da siler; token'a dokunulmaz)
@@ -429,8 +433,7 @@ Setup & Maintenance:
 Plugin'ler ve tool'lar (doğrudan çağrılır, sarmalayıcı yok):
 
   Stack plugin     ai-<stack>-toolkit:<skill>, örn. ai-ios-toolkit:create-component
-                   Katalog: ai-<stack>-toolkit:help   Repo bazında aç: /multi-agent:stack
-                   common + analyst hep açık; gerisi repo'nun stack'ini izler.
+                   Katalog: ai-<stack>-toolkit:help   Repo bazında aç: /multi-agent:stack (common + analyst hep açık)
   Toolkit MCP      multi-agent-toolkit  -  ÇALIŞAN uygulama için 80+ tool, pipeline koşusu
                    gerektirmez: ios_* / android_* (başlat, tap, screenshot, ui ağacı, log,
                    crash, locale, koyu mod), web_*, design_* (yukarıdaki Design Check), ve
@@ -456,9 +459,8 @@ Rutinler (kendi tekrar eden işlerin):
 
   İkisi de seçim sonrası aynı akışı takip eder:
     1. Branch seçimi (develop/release/main)
-    2. Derinlik: Tam ya da Kısa
-    3. Autopilot: evet/hayır
-    4. Pipeline seçilen issue ile başlar
+    2. Autopilot: evet/hayır
+    3. Pipeline seçilen issue ile başlar
 
 ------------------------------
 
@@ -473,8 +475,7 @@ UI Testing (standalone  -  pipeline fazlarından bağımsız):
   /multi-agent:test-dynamic-type     Büyük metin boyutu testi
   /multi-agent:test-screenshots [tr] Belirtilen dilde App Store screenshot seti (default tr)
 
-  Senaryo etiketli form çalışmaya devam eder, kaldırılmadı  -  yukarıdaki komutların
-  her biri onun alias'ı.
+  Senaryo etiketli form çalışır; yukarıdaki her komut onun alias'ı.
 
   /multi-agent:test "dark mode" | "accessibility" | "dynamic type" | "screenshot <dil>"
 
@@ -495,8 +496,8 @@ Design Check (mock-mod vs Figma, yalnızca lokal):
   /multi-agent:design-check                Tüm modül denetimi: her state sürücüsünü sayılabilir hedef kümesine
                                            çıkar, worktree'de Debug derle, her hedefi mock modda sür, Figma
                                            frame'iyle diff'le, HTML+PDF raporu ~/DesignChecks'e yaz.
-  /multi-agent:design-check <ekran>        Tek ekrana kapsa (örn. boarding-pass).
-  /multi-agent:design-check <ekran@varyant> Tek varyanta kapsa (örn. boarding-pass@expired).
+  /multi-agent:design-check <ekran>        Tek ekrana kapsa (örn. order-status).
+  /multi-agent:design-check <ekran@varyant> Tek varyanta kapsa (örn. order-status@expired).
   /multi-agent:design-check <figma-url...> URL'lerin işaret ettiği frame'lere kapsa.
   /multi-agent:design-check --resume       Son koşunun denetlenmemiş kalanını denetle.
   # KAPSAM GEÇİDİ: her hedef ya denetlenir ya da SOMUT gerekçeyle atlanır; başka her durum eksik hedef
@@ -546,8 +547,6 @@ Quality & Telemetry (advisory, default açık  -  prefs.global.* ile kapatılabi
   # Jira ile tam pipeline (key setup'ta yapılandırıldı)
   /multi-agent "MOBILE-12345"
 
-  # GitHub issue, hızlı mode, local
-
   # İnteraktif launcher'lar  -  göz at ve seç
   /multi-agent:jira                    # Jira issue'larımdan seç
   /multi-agent:issue                   # Atanmamış GitHub issue'lardan seç
@@ -556,14 +555,13 @@ Quality & Telemetry (advisory, default açık  -  prefs.global.* ile kapatılabi
   /multi-agent:autopilot "LoginView dark mode fix"               # iOS
   /multi-agent "Add pagination to /api/users endpoint"           # Backend
   /multi-agent "Fix bottom nav recomposition in HomeScreen"      # Android
-  /multi-agent "Responsive layout broken on tablet"              # Web, Kısa seç
+  /multi-agent "Responsive layout broken on tablet"              # Web
 
   # Sadece mevcut diff'i review et
   /multi-agent:review
 
   # Takım standartlarına uygun Jira issue oluştur (oluşturmadan önce önizleme + onay)
   /multi-agent:create-jira "Profil ekranı empty state" https://figma.com/design/abc?node-id=1-2
-  /multi-agent:create-jira "iOS 17'de login crash, log ekte"
 
 ------------------------------
 

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

@@ -2,6 +2,10 @@
 description: "Audit an iOS module against the shared coding-standard registry (99 stable-ID rules), produce a remediation plan, then hand off to /multi-agent. Use for a standards pass on a module, or when a review needs rule IDs rather than opinions."
 description-tr: "Bir iOS modulunu paylasilan kodlama-standardi registry'sine (99 sabit-ID kural) gore denetler, duzeltme plani cikarir, sonra /multi-agent'e devreder. Bir modulde standart gecisi icin, ya da bir review'un gorus yerine kural ID'si istedigi durumda kullan."
 argument-hint: "[module name or path]"
+parameters: [{"name":"target","kind":"path"}]
+gui: form
+destructive: false
+confirm: none
 allowed-tools: Skill, Bash, Read, Edit, Write, AskUserQuestion
 ---
 

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

@@ -2,6 +2,10 @@
 description: "List unassigned GitHub issues, pick one, auto-assign, and launch the multi-agent pipeline. Use when a GitHub issue should be picked up and started without knowing its number in advance."
 description-tr: "Atanmamış GitHub issue'larını listeler, birini seçtirir, otomatik atar ve multi-agent pipeline'ı başlatır."
 argument-hint: "[autopilot]  -  optional: run the pipeline without confirmations"
+parameters: [{"name":"autopilot","kind":"flag"}]
+gui: button
+destructive: false
+confirm: none
 not-for: jira
 ---
 
@@ -34,6 +38,8 @@ Fully interactive. Only one optional flag: `autopilot`.
 
 ### [3/4] Pick issue (aggregate)
 
+The same list, already merged, sorted and scrubbed of hosts and URLs, is `node "$HOME/.claude/scripts/issues.mjs" --json` (Jira and GitHub in one shape); prefer it over hand-rolled calls when it answers.
+
 ```bash
 for repo in "${SELECTED_REPOS[@]}"; do
   gh issue list --repo "$repo" --state open --assignee "" \
@@ -74,7 +80,7 @@ content, and only a DIFFERENT gap set ever earns a second comment. Read the item
 comments FIRST and derive the prior ask from the newest one of ours (`priorFromComments`):
 a scan is a new run with a fresh state file, so state alone would make every scan a first ask.
 
-`PROMPT_LANG=en` is passed to `issue-fetcher.sh` (`promptLanguage` is locked to `"en"`).
+The fetcher renders `maturity.summary` in `prefs.global.outputLanguage`; every other descriptor field is machine-readable and stays English.
 
 ### [4/4] Dev context (`_dev-context`)
 

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

@@ -2,6 +2,10 @@
 description: "List open Jira issues, pick one, and launch the multi-agent pipeline. Use when a Jira issue should be picked up and started without knowing its key in advance."
 description-tr: "Açık Jira issue'larını listeler, birini seçtirir ve multi-agent pipeline'ı başlatır."
 argument-hint: "[autopilot]  -  optional: run the pipeline without confirmations"
+parameters: [{"name":"autopilot","kind":"flag"}]
+gui: button
+destructive: false
+confirm: none
 ---
 
 # multi-agent jira  -  4-Step Picker (Account → Project → Issue → Dev Context)
@@ -36,6 +40,8 @@ curl -s -H "Authorization: Bearer $TOKEN" \
 
 ### [3/4] Pick issue (aggregate, priority-sorted)
 
+The same list, already merged, sorted and scrubbed of hosts and URLs, is `node "$HOME/.claude/scripts/issues.mjs" --json` (Jira and GitHub in one shape); prefer it over hand-rolled calls when it answers.
+
 Combine open issues across selected projects, sort by priority + status:
 ```bash
 JQL="assignee=currentUser() AND project in (${JIRA_PROJECT_KEYS}) AND resolution = EMPTY AND status not in (Done,Closed,Cancelled)"
@@ -114,7 +120,7 @@ a scan is a new run with a fresh state file, so state alone would make every sca
 
 > **fixVersions**: When `descriptor.fixVersions` is non-empty (e.g. `["v1.48.0"]`) and a matching `release/v1.48.0` branch exists in `prefs.projects[*].branches`, suggest that branch. Otherwise fall back to `develop`/cwd current.
 
-`PROMPT_LANG=en` is passed to `issue-fetcher.sh` (`promptLanguage` is locked to `"en"`).
+The fetcher renders `maturity.summary` in `prefs.global.outputLanguage`; every other descriptor field is machine-readable and stays English.
 
 ### [4/4] Dev context (`_dev-context`)