--- 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)." --- # multi-agent help Called with no args or `help`, show the usage guide in the user's preferred language. ## Language resolution Help is the assistant's own explanation to the user - render it in `prefs.global.outputLanguage`. Fall back to `prefs.global.promptLanguage` for legacy prefs files where `outputLanguage` did not exist yet. Two valid values: `"en"` (default) and `"tr"`. If both fields are missing / malformed → treat as `"en"`. ```bash PREFS="$HOME/.claude/multi-agent-preferences.json" LANG=$(jq -r '.global.outputLanguage // .global.promptLanguage // "en"' "$PREFS" 2>/dev/null || echo "en") ``` Render **exactly one** of the two blocks below - the one matching `LANG`. Do not print both; the user asked for a display, not a bilingual dump. --- ## Render when `LANG == "en"` - English guide ``` +----------------------------------------------------------+ | Multi-Agent Task Orchestrator | +----------------------------------------------------------+ 5 different input types supported - all enter the same flow: /multi-agent "{JIRA_KEY}-XXXXX" -> Jira ID /multi-agent "https://{JIRA_HOST}/browse/..." -> Jira URL /multi-agent "https://github.com/.../issues/N" -> GitHub Issue URL /multi-agent "#316" -> GitHub Issue # /multi-agent "bug/feature description" -> Free-text ------------------------------------------------------------ How It Works (Phase 0 - Interactive Flow): 1. PARSE Classify input, fetch info from Jira/GitHub 2. PROJECT $HOME scanned, projects listed -> select by number 3. BRANCH Remote branches fetched (develop* first) -> select 4. DESIGN? Any Figma URL or screenshot? (optional) 5. BRANCH NAME bugfix/{jiraId} or feature/{jiraId} -> confirm 6. GIT ID Select identity from preferences (multiple supported) 7. INSTRUCTION Auto-detect if .instructions/ exists (figma etc.) 8. WORKSPACE Create worktree (default) or local branch (--local) ------------------------------------------------------------ Pipeline (after Phase 0) - shown as visual cards in terminal: Phase 0: Init -> The 8 steps above Phase 1: Analysis -> Stack detection + codebase scan (Fable) Phase 2: Planning -> Task breakdown + architecture review + Plan Approval Gate (clarification max 2 rounds + approval loop - Full + interactive only; a Short run has no plan, autopilot may not ask) Phase 3: Dev -> TDD: test -> code -> build (Sonnet) + build queue Phase 4: Review -> Deterministic gates + parallel AI review + Fable triage (Claude Code: Fable + Sonnet · Copilot CLI: GPT-5.4 + Opus + Sonnet) Phase 5: Test -> Optional: switch to branch, test in Xcode (only /multi-agent has it; every autopilot and local entry drops it) Phase 6: Commit -> Commit -> push -> PR + issue body update (never auto-closes) Phase 7: Report -> Channels dispatcher (PR · Jira · Confluence · Wiki, multi-select) + internal capture (agent-log · knowledge · memory) Autopilot always pauses at the Phase 7 channels menu (30-min timeout → session ends cleanly). Pipeline depth is asked at Phase 0 Step 7.5, not passed as a flag: Full Analysis -> Plan -> Dev(Sonnet) -> Review -> Test -> Commit -> Report Short Dev(Opus, self-contained) -> Review -> Test -> Commit -> Report Short skips Phases 1-2 only. Review is NEVER skipped. Recommended from taskType: bugfix/chore -> Short, feature/refactor/component -> Full. Autopilot never asks and always runs Full. Every step is logged. Error in any phase -> pause -> resume to continue. ------------------------------------------------------------ Modes: Four pipeline entries: /multi-agent "task" Worktree, asks Full or Short /multi-agent:local "task" No worktree, asks Full or Short /multi-agent:autopilot "task" Worktree, no questions, always Full /multi-agent:local-autopilot "task" No worktree, no questions, always Full --local on the base command is the same as the :local entry. autopilot skips every confirmation INCLUDING the plan gate and the depth question, and auto commit/PR - EXCEPT the Phase 7 channels menu, which always pauses. /multi-agent:resume-local [jira-id] [autopilot] Continue already-done LOCAL work: Review → Build+Test → PR → Jira analysis + test scenarios (no dev) Removed in v16.0.0: :dev -> /multi-agent + Short · :dev-local -> :local + Short :dev-autopilot and :dev-local-autopilot have no equivalent - fast plus unattended is gone; pick unattended-and-Full or fast-and-attended. ------------------------------------------------------------ Status & Resume: /multi-agent:status List tasks across all projects (id, phase, branch, state) /multi-agent:log [#id] Show task log (defaults to most recent) /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) Post-Hoc & Side-Channel: /multi-agent:channels Post multi-channel report (Jira / Confluence / Wiki / PR description) /multi-agent:feedback "msg" Tell the maintainer something broke; only your text is sent /multi-agent:review Parallel review of a PR or branch diff; no URL -> pick open GitHub/Bitbucket PRs /multi-agent:review-jira Grade a Jira issue's pipeline-readiness -> comment the gaps on it /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). 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:review-analysis [doc] Review a written analysis; findings cite the rule they break /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 /multi-agent:search Cross-task log search with smart ranking; --semantic queries triage corpus /multi-agent:scan Skill security scan against tiered pattern catalog /multi-agent:refactor Best practices + bug hunt + upstream drift + toolkit MCP research -> one plan, approval, dev + sync /multi-agent:store-ready [repo] [--archive=|--ipa=|--aab=|--apk=] [--skip-sweep] 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:testflight-validation [repo] [--ipa=|--archive=] iOS-pinned alias of :store-ready, kept because it is the name you reach for when the target is TestFlight. 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 or :local. Read-only, never edits source. 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 [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 + 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--toolkit:. Catalog: ai--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: command /multi-agent:routines List your saved routines and what each does /multi-agent:forget [name] Remove a saved routine ------------------------------------------------------------ Interactive Launchers: /multi-agent:jira List MY open Jira issues → pick → branch → mode → go /multi-agent:issue List UNASSIGNED GitHub issues → pick → auto-assign → go Both follow the same flow after selection: 1. Branch selection (develop/release/main) 2. Depth: Full or Short 3. Autopilot: yes/no 4. Pipeline starts with the selected issue ------------------------------------------------------------ UI Testing (standalone - not part of pipeline phases): /multi-agent:test Full simulator test (screenshot all screens) Fixed-scenario commands - no quoting, and they autocomplete off `test-`: /multi-agent:test-dark-mode Dark mode bug test /multi-agent:test-accessibility Accessibility audit (labels, tap targets, contrast) /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. /multi-agent:test "dark mode" | "accessibility" | "dynamic type" | "screenshot " `store-ready` is NOT a UI test: it validates a built package, on iOS and Android, through three gates per platform, and lives at /multi-agent:store-ready. The old /multi-agent:test "store-ready" [path] tag still works and hands off there. Uses xcrun simctl / adb (native, no external app needed). Booted simulator/emulator required. Auto-detects bundle ID from project. Manual Test (Phase 5 standalone - Xcode hint flow): /multi-agent:manual-test Checkout task branch, print Xcode/SourceTree hints, /multi-agent:manual-test #N wait for your "ok" / "fix: ..." verdict. Design Check (mock-mode vs Figma, local-only - powered by the toolkit MCP design_* tools): /multi-agent:design-check Whole-module design audit: pick repo+module, gate on mock support, enumerate every state driver (launch args, scenario cases, scenario codes, fixtures, deep links) into a countable target set, build Debug in a worktree, drive each target in mock mode via idb, compare each vs its Figma frame (padding/width/spacing/font/color/component/localization), and export a report (HTML+PDF, ~/DesignChecks). /multi-agent:design-check Scope to one screen's targets (e.g. boarding-pass). /multi-agent:design-check Scope to a single variant (e.g. boarding-pass@expired). /multi-agent:design-check Scope to the frame(s) those URLs name. /multi-agent:design-check --resume Audit the unaudited remainder of the last run for this repo+module. # COVERAGE GATE: every target is either audited or skipped WITH a concrete reason. Anything else fails the # gate and the run is reported INCOMPLETE with the missing target ids - a partial audit never reads as clean. # "Requires a scenario / prefix / launch-arg" is not a reason; reaching those states is the run's job. # When a live screen has no confident Figma match, it SHOWS you the screenshot and asks for the node-id. Drives the toolkit design_* tools (+ ios_* / android_* device control). ------------------------------------------------------------ Setup: /multi-agent:setup Interactive onboarding: 1. Dynamic Keychain Discovery - finds existing tokens by keyword 2. Token Mapping - maps found keys to services (preferences) 3. Jira Project Key - your team's key (MOBILE, APP, ENG, etc.) 4. Git Identity - corporate + personal (saved to preferences) 5. Missing Tokens - standard key names + ready-to-paste commands 6. Verify - re-scan, confirm ready ------------------------------------------------------------ Key Features: Multi-Platform iOS, Android, Backend, Frontend - auto-detected Build Queue xcodebuild/Gradle serialized with lock file - parallel safe Stack Aware Auto-detects iOS/Android/Python/Node/Go/Docker, uses the enabled stack plugin's skills Det. Gates Build + lint + test + secret scan BEFORE AI review Multi-Repo Per-repo worktrees, per-repo identity, integration build before commit Identity Routing Git identity auto-picked from repo origin URL (corporate vs personal) Issue Safety Never auto-closes issues (4 approvals required, GitHub + Jira) Store Compliance /multi-agent:test "store-ready" runs 18-rule iOS audit (ITMS / Privacy Manifest / code signing / debug-tool leak / IPv6 / SDK list / etc.) and 21-rule Android audit Bilingual EN + TR - outputLanguage toggles assistant explanations; promptLanguage is locked en Quality & Telemetry (advisory, on by default - flip prefs.global.* to disable): Diff Risk Score Phase 4 Step 1.75 ranks files before reviewer dispatch (security paths, schema migrations, no-test-change, complexity delta) - heuristic, sub-second Test Gap Report Phase 5 Step 0 surfaces public symbols added in this branch with no paired test Cost Breakdown Phase 7 appends per-phase tokens (in/out) + estimated USD to agent-log.md Triage Memory Phase 7 ingests accepted/deferred/rejected findings into a per-repo corpus Prior-Art Lookup Phase 1 + Phase 4 query the corpus for similar past findings, inject as context Per-Persona Reviewer/agent dispatch reads `preferredModel` from persona file; per-call override via PHASE_MODEL_OVERRIDE; ladder fable -> opus -> sonnet -> haiku ------------------------------------------------------------ Examples: # Full pipeline with Jira (key configured during setup) /multi-agent "MOBILE-12345" # GitHub issue, fast mode, local /multi-agent:local "#42" # then choose Short # Interactive launchers - browse and pick /multi-agent:jira # Pick from my Jira issues /multi-agent:issue # Pick from unassigned GitHub issues # Free-text - any platform /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" # Frontend, choose Short # Review current diff only /multi-agent:review # 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" ------------------------------------------------------------ Logs: $HOME/.claude/logs/multi-agent/{project}/{task-id}/ ``` --- ## Render when `LANG == "tr"` - Türkçe rehber ``` +----------------------------------------------------------+ | Multi-Agent Görev Orkestratörü | +----------------------------------------------------------+ 5 farklı girdi tipi desteklenir - hepsi aynı akışa girer: /multi-agent "{JIRA_KEY}-XXXXX" -> Jira ID /multi-agent "https://{JIRA_HOST}/browse/..." -> Jira URL /multi-agent "https://github.com/.../issues/N" -> GitHub Issue URL /multi-agent "#316" -> GitHub Issue # /multi-agent "bug/özellik açıklaması" -> Serbest metin ------------------------------------------------------------ Nasıl Çalışır (Phase 0 - İnteraktif Akış): 1. PARSE Girdiyi sınıflandır, Jira/GitHub'dan bilgi çek 2. PROJECT $HOME taranır, projeler listelenir -> numarayla seç 3. BRANCH Remote branch'ler çekilir (develop* önde) -> seç 4. DESIGN? Figma URL'si ya da screenshot var mı? (opsiyonel) 5. BRANCH NAME bugfix/{jiraId} veya feature/{jiraId} -> onayla 6. GIT ID Kimlik seç (prefs'ten; birden fazla desteklenir) 7. INSTRUCTION .instructions/ varsa otomatik algıla (figma vs.) 8. WORKSPACE Worktree yarat (default) ya da local branch (--local) ------------------------------------------------------------ Pipeline (Phase 0'dan sonra) - terminalde görsel kart olarak görünür: Phase 0: Init -> Yukarıdaki 8 adım Phase 1: Analysis -> Stack tespiti + codebase taraması (Fable) Phase 2: Planning -> Task kırılımı + mimari inceleme + Plan Onay Kapısı (clarification max 2 tur + onay döngüsü - sadece Tam + etkileşimli; Kısa'da plan yok, autopilot soru soramaz) Phase 3: Dev -> TDD: test -> kod -> build (Sonnet) + build queue Phase 4: Review -> Deterministik kapılar + paralel AI review + Fable triage (Claude Code: Fable + Sonnet · Copilot CLI: GPT-5.4 + Opus + Sonnet) Phase 5: Test -> Opsiyonel: branch'e geç, Xcode'da test (yalnız /multi-agent'ta var; her autopilot ve local girişi düşürür) Phase 6: Commit -> Commit -> push -> PR + issue body güncelleme (hiç auto-close yok) Phase 7: Report -> Channels dispatcher (PR · Jira · Confluence · Wiki, multi-select) + internal capture (agent-log · knowledge · memory) Autopilot Phase 7'deki 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 Analiz -> Plan -> Dev(Sonnet) -> Review -> Test -> Commit -> Report Kısa Dev(Opus, kendi kendine yeten) -> Review -> Test -> Commit -> Report Kısa yalnız Faz 1-2'yi atlar. Review ASLA atlanmaz. taskType'a göre önerilir: bugfix/chore -> Kısa, feature/refactor/component -> Tam. Autopilot hiç sormaz, her zaman Tam koşar. Her adım loglanır. Herhangi bir fazdaki hata -> pause -> resume ile devam et. ------------------------------------------------------------ Modlar: Dört pipeline girişi: /multi-agent "task" Worktree var, Tam mı Kısa mı diye sorar /multi-agent:local "task" Worktree yok, Tam mı Kısa mı diye sorar /multi-agent:autopilot "task" Worktree var, soru yok, her zaman Tam /multi-agent:local-autopilot "task" Worktree yok, soru yok, her zaman Tam Ana komuta --local eklemek :local girişiyle aynıdır. autopilot plan kapısı ve derinlik sorusu dahil her onayı atlar, otomatik commit/PR açar - İSTİSNA: Faz 7 channels menüsü, o her zaman durur. /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) v16.0.0'da kaldırılanlar: :dev -> /multi-agent + Kısa · :dev-local -> :local + Kısa :dev-autopilot ve :dev-local-autopilot'un karşılığı yok - hızlı+gözetimsiz bitti; ya gözetimsiz-ve-Tam ya hızlı-ve-insan-başında seçilir. ------------------------------------------------------------ Status & Resume: /multi-agent:status Tüm projelerdeki task'ları listele (id, faz, branch, durum) /multi-agent:log [#id] Task log'unu göster (varsayılan: en son task) /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) Post-Hoc & Side-Channel: /multi-agent:channels Multi-channel rapor gönder (Jira / Confluence / Wiki / PR description) /multi-agent:feedback "mesaj" Bakımcıya bir şeyin bozulduğunu bildir; yalnızca yazdığın metin gider /multi-agent:review PR veya branch diff'ini paralel review et; URL yoksa -> açık GitHub/Bitbucket PR'larını seçtir /multi-agent:review-jira Jira maddesinin pipeline'a hazırlığını değerlendir -> eksikleri yorum olarak ekle /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:review-analysis [doc] Yazılmış analizi review eder; bulgular ihlal edilen kuralı gösterir /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 /multi-agent:search Task log'larında akıllı arama; --semantic triage corpus'unu sorgular /multi-agent:scan Skill güvenlik taraması (tiered pattern catalog) /multi-agent:refactor Uyarlanmış best-practice + bug avı + upstream-drift + multi-agent-toolkit MCP araştırması -> tek plan, onay, dev + sync /multi-agent:store-ready [repo] [--archive=|--ipa=|--aab=|--apk=] [--skip-sweep] 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:testflight-validation [repo] [--ipa=|--archive=] :store-ready'nin iOS'a sabitlenmiş alias'ı; hedef TestFlight olduğunda akla gelen isim olduğu için korunuyor. 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 veya :local'e devreder. Read-only, kaynağı hiç düzenlemez. 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 [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 + 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 + logları da siler; Keychain token her zaman dokunulmaz, çift onay) ------------------------------------------------------------ Stack plugin skill'leri: doğrudan ai--toolkit: olarak çağrılır (örn. ai-ios-toolkit:create-component). Lokal kopya ve sarmalayıcı yok. Katalog: ai--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: komutu olarak kaydet /multi-agent:routines Kayıtlı rutinlerini ve ne yaptıklarını listele /multi-agent:forget [ad] Kayıtlı bir rutini kaldır ------------------------------------------------------------ İnteraktif Launcher'lar: /multi-agent:jira BENİM açık Jira issue'larımı listele → seç → branch → mode → başla /multi-agent:issue ATANMAMIŞ GitHub issue'ları listele → seç → auto-assign → başla İ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 ------------------------------------------------------------ UI Testing (standalone - pipeline fazlarından bağımsız): /multi-agent:test Tam simulator testi (tüm ekran screenshot'ları) Sabit-senaryo komutları - tırnak gerekmez, `test-` ile autocomplete'e düşer: /multi-agent:test-dark-mode Dark mode bug testi /multi-agent:test-accessibility Erişilebilirlik denetimi (label/tap-target/kontrast) /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'ı. /multi-agent:test "dark mode" | "accessibility" | "dynamic type" | "screenshot " `store-ready` bir UI testi DEĞİL: üretilmiş paketi platform başına üç kapıdan geçirerek doğrular, iOS + Android, ve /multi-agent:store-ready altında. Eski /multi-agent:test "store-ready" [path] etiketi çalışır ve oraya devreder. xcrun simctl / adb kullanır (harici app gerekmez). Booted simulator/emulator şart. Bundle ID proje'den otomatik algılanır. Manuel Test (Phase 5 standalone - Xcode hint akışı): /multi-agent:manual-test Task branch'ine checkout, Xcode/SourceTree hint basar, /multi-agent:manual-test #N "ok" / "fix: ..." yanıtını bekler. Design Check (mock-mod vs Figma, yalnızca lokal - multi-agent-toolkit-mcp design_* tool'larıyla): /multi-agent:design-check Tüm modül tasarım denetimi: repo+modül seç, mock desteğini geçitle, her state sürücüsünü (launch arg, senaryo case'leri, senaryo kodları, fixture'lar, deep link'ler) sayılabilir bir hedef kümesine çıkar, worktree'de Debug derle, her hedefi mock modda idb ile sür, her birini Figma frame'iyle karşılaştır (padding/genişlik/spacing/font/renk/ component/localization), rapor çıkar (HTML+PDF, ~/DesignChecks). /multi-agent:design-check Tek ekranın hedeflerine kapsa (örn. boarding-pass). /multi-agent:design-check Tek varyanta kapsa (örn. boarding-pass@expired). /multi-agent:design-check URL'lerin işaret ettiği frame'lere kapsa. /multi-agent:design-check --resume Bu repo+modül için son koşunun denetlenmemiş kalanını denetle. # KAPSAM GEÇİDİ: her hedef ya denetlenir ya da SOMUT bir gerekçeyle atlanır. Başka her durum geçidi # düşürür ve koşu eksik hedef id'leriyle EKSİK raporlanır - kısmi denetim asla temiz görünmez. # "Senaryo / prefix / launch-arg gerektirir" gerekçe değildir; o state'lere ulaşmak koşunun işidir. # Canlı ekranın Figma karşılığı kesin bulunamazsa SANA screenshot'ı gösterip node-id sorar. multi-agent-toolkit-mcp design_* tool takımını sürer (+ ios_* / android_* cihaz kontrolü). ------------------------------------------------------------ Setup: /multi-agent:setup İnteraktif onboarding: 1. Dynamic Keychain Discovery - mevcut token'ları keyword ile bulur 2. Token Mapping - bulunanları servislere eşler (prefs) 3. Jira Project Key - takımının key'i (MOBILE, APP, ENG vb.) 4. Git Kimliği - kurumsal + kişisel (prefs'e kaydedilir) 5. Eksik Token'lar - standart key isimleri + ready-to-paste komutlar 6. Doğrulama - yeniden tarama, hazır mı kontrol ------------------------------------------------------------ Temel Özellikler: Multi-Platform iOS, Android, Backend, Frontend - otomatik tespit Build Queue xcodebuild/Gradle lock file ile seri - parallel güvenli Stack Aware iOS/Android/Python/Node/Go/Docker algılanır, etkin stack plugin'inin skilleri kullanılır Det. Gates AI review'dan ÖNCE build + lint + test + secret scan Multi-Repo Repo başına worktree, repo başına identity, commit öncesi entegrasyon build'i Identity Routing Repo origin URL'sinden git kimliği seçimi (kurumsal vs kişisel) Issue Safety Issue'lar asla auto-close edilmez (GitHub + Jira için 4 onay gerekir) Store Compliance /multi-agent:test "store-ready" - iOS için 18 kurallık audit (ITMS / Privacy Manifest / code signing / debug-tool leak / IPv6 / SDK list / vb.) + Android için 21 kurallık audit Bilingual EN + TR - outputLanguage assistant açıklamasını değiştirir; promptLanguage en kilitli Quality & Telemetry (advisory, default açık - prefs.global.* ile kapatılabilir): Diff Risk Score Phase 4 Step 1.75 reviewer dispatch'tan önce dosyaları sıralar (güvenlik path'leri, schema migration, test eklenmemiş değişiklik, complexity delta) - heuristik, saniyenin altı Test Gap Report Phase 5 Step 0 - bu branch'te eklenmiş public sembol + eşleşen test yoksa raporlar Cost Breakdown Phase 7 agent-log.md'ye faz başına token (in/out) + tahmini USD ekler Triage Memory Phase 7 accepted/deferred/rejected bulguları repo başına corpus'a yazar Prior-Art Lookup Phase 1 + Phase 4 corpus'tan benzer geçmiş bulgu sorgular, ek context olarak enjekte Per-Persona Reviewer/agent dispatch persona dosyasından `preferredModel` okur; per-call override PHASE_MODEL_OVERRIDE ile; merdiven fable -> opus -> sonnet -> haiku ------------------------------------------------------------ Örnekler: # Jira ile tam pipeline (key setup'ta yapılandırıldı) /multi-agent "MOBILE-12345" # GitHub issue, hızlı mode, local /multi-agent:local "#42" # sonra Kısa seç # İnteraktif launcher'lar - göz at ve seç /multi-agent:jira # Jira issue'larımdan seç /multi-agent:issue # Atanmamış GitHub issue'lardan seç # Serbest metin - herhangi bir platform /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" # Frontend, Kısa seç # 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" ------------------------------------------------------------ Log'lar: $HOME/.claude/logs/multi-agent/{project}/{task-id}/ ```