@mmerterden/multi-agent-pipeline 15.16.0 → 16.0.0

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

@@ -1,120 +1,17 @@
 ---
-description: "Fast mode + local  -  Init → Dev(Opus) → Review → Commit → Report, no worktree. Use when a change should be developed and reviewed on the current branch without creating a worktree."
-description-tr: "Hızlı mod + lokal - Init → Dev(Opus) → Review → Commit → Report, worktree yok."
-allowed-tools: Agent, Bash, Read, Write, Edit, Glob, Grep, TaskCreate, TaskUpdate, TaskList, TaskGet, AskUserQuestion, WebFetch, Skill
+description: "Removed in v16.0.0. Its worktree-free twin is /multi-agent:local, which asks the same depth question; answer Short there. Invoke only to see that redirect."
+description-tr: "v16.0.0'da kaldırıldı. /multi-agent:local çalıştırıp derinlik sorusunda Kısa seçin."
 ---
 
-# multi-agent dev-local  -  Fast + Local
+# multi-agent dev-local  -  Removed in v16.0.0
 
-> **Language (read FIRST)**: Before any status output, read `prefs.global.outputLanguage` and render every conversational line in it. `AskUserQuestion` `label`/`header` stay English, but its `question` and option `description`s render in `outputLanguage`; external payload bodies follow `outputLanguage` too (identifiers, commit messages, branch names stay English). Full contract: `$HOME/.claude/multi-agent-refs/rules.md` "Language Application".
+Depth stopped being a command name in v16.0.0. `--local` is still a command, because a worktree is a real difference in where the work happens; depth is not.
 
-Dedicated form of the `--dev` + `--local` combination. A 4-phase fast pipeline (no worktree).
-
-## Pipeline
-
-```
-Phase 0: Init       → project detection, branch check, state (NO worktree)
-Phase 3: Dev        → direct development on Opus (Analysis + Planning skipped)
-Phase 4: Review     → deterministic gates + parallel review + triage
-Phase 6: Commit     → pre-commit checkout prompt, commit + push + PR
-Phase 7: Report     → Jira / Wiki + log + knowledge/memory
-```
-
-`--dev local` skips Phase 1 (Analysis), Phase 2 (Planning + Approval Gate), and Phase 5 (User Test  -  local/autopilot variants skip the interactive test gate). It differs from `--dev` on two axes: no git worktree is created (development happens directly on the current branch in `$PROJECT_ROOT`), and the interactive User Test phase is skipped. **Review is not skipped**  -  Phase 4 runs its gates, resolves the criteria the dev phase was supposed to honour, reviews in parallel and triages, and accepted blocking findings return to Phase 3 (3-iteration cap).
-
-
-## When to use it
-
-- Quick bug fix or small feature  -  analysis and planning buy nothing here
-- You're working on the current branch and don't want to switch worktrees
-- A well-understood change  -  you want it reviewed, not designed
-## Required: Phase Tracker Contract
-
-**The phase tracker is mandatory**  -  the agent cannot skip it. Full spec: [`$HOME/.claude/multi-agent-refs/tracker-contract.md`]($HOME/.claude/multi-agent-refs/tracker-contract.md).
-
-> **Local mode:** no worktree is created, work happens on the current branch. Phase 0 Init still calls `init`  -  the `--local` flag is stored in tracker-state.json, and `:resume` restores the correct CWD.
-
-Two channels run in parallel at every phase boundary:
-
-1. **State channel** (every CLI, identical): `phase-tracker.sh` writes to `tracker-state.json`. Drives `:resume`, `:log`, `:status`.
-2. **Visual channel** (CLI-specific): native widget on Claude Code, ANSI render on every other CLI. Without it the user sees no phase progress.
-
-```bash
-# Phase 0, very first shell call (every CLI):
-bash $HOME/.claude/scripts/phase-tracker.sh init "$TASK_ID"
-for p in "0:Init" "3:Dev" "4:Review" "6:Commit" "7:Report"; do
-  bash $HOME/.claude/scripts/phase-tracker.sh add "${p%%:*}" "${p#*:}"
-done
-bash $HOME/.claude/scripts/phase-tracker.sh update 0 in_progress
-
-# Every phase boundary (every CLI):
-bash $HOME/.claude/scripts/phase-tracker.sh update <N> in_progress|completed|failed|skipped
-
-# After every LLM call (every CLI):
-bash $HOME/.claude/scripts/phase-tracker.sh tokens <N> <in> <out> [cached]
-```
-
-### Visual channel  -  Claude Code (native TaskList widget, required)
-
-In Claude Code the agent MUST also drive the native TaskList widget so the user sees a sticky phase tile stack  -  this is the only progress signal Claude Code surfaces. Skipping these calls is the #1 source of "I don't see any phases" complaints.
-
-**TaskCreate ordering (strict)**: All TaskCreate calls fire in strict phase-number order BEFORE any TaskUpdate is applied. The native widget renders by creation order, not by phase number  -  out-of-order calls produce visually scrambled tile stacks (e.g. `1 ✓ · 2 ✓ · 4 ✓ · 0 ▶ · 3 ☐`) even when the underlying state is correct. Pre-marking phases as completed/skipped before Phase 0 starts is FORBIDDEN  -  register the tile in order, then flip status via TaskUpdate when the phase actually short-circuits. Full contract in `$HOME/.claude/multi-agent-refs/tracker-contract.md` section "TaskCreate ordering (strict)".
-
-```text
-# Phase 0 startup  -  register one tile per phase (0..N), capture the taskId, persist it:
-for each phase in 0:Init, 3:Dev, 4:Review, 6:Commit, 7:Report:
-  TaskCreate({ subject: "Phase <N>: <Name>", activeForm: "<doing-form>" })
-    -> returns taskId
-  bash $HOME/.claude/scripts/phase-tracker.sh meta <N> tasklist_id "<taskId>"
-
-# Phase entry  -  flip the tile to in_progress alongside the state update:
-TaskUpdate({ taskId: <saved>, status: "in_progress" })
-bash $HOME/.claude/scripts/phase-tracker.sh update <N> in_progress
-
-# Active sub-step inside a phase  -  update activeForm so the spinner header reflects what's happening now:
-TaskUpdate({ taskId: <saved>, activeForm: "Editing TopBarView.swift" })
-
-# Phase exit  -  flip to completed/failed/skipped on both channels:
-TaskUpdate({ taskId: <saved>, status: "completed" })
-bash $HOME/.claude/scripts/phase-tracker.sh update <N> completed
 ```
-
-`--dev local` mode does NOT TaskCreate phases 1/2/5  -  those are not part of the `--dev local` phase set (`0:Init 3:Dev 4:Review 6:Commit 7:Report`). Only register tiles for the active set.
-
-#### TaskCreate ordering (strict)
-
-**All TaskCreate calls fire in strict phase-number order BEFORE any TaskUpdate is applied.** For `--dev local` that means: Phase 0 → Phase 3 → Phase 4 → Phase 6 → Phase 7. The native widget renders by creation order, not by phase number  -  out-of-order calls produce visually scrambled tile stacks. Full ordering contract in `$HOME/.claude/multi-agent-refs/tracker-contract.md` section "TaskCreate ordering (strict)".
-
-### Visual channel  -  Copilot CLI / plain shell
-
-These CLIs have no TaskList widget. After every state change the agent calls render, which prints a bordered ANSI card as the last tool result so the user sees an updated phase table:
-
-```bash
-bash $HOME/.claude/scripts/phase-tracker.sh render
+/multi-agent:dev-local has been removed. Run /multi-agent:local and choose
+Short at the depth question - same pipeline, one picker step earlier.
 ```
 
-Do NOT call TaskCreate on these CLIs  -  the tool does not exist and the call fails.
-## Delegation
-
-Routes to the orchestrator with `--dev --local` flags. Apply the `$HOME/.claude/commands/multi-agent/dev/SKILL.md` pipeline in local mode:
-- Phase 0: skip worktree creation, continue on the current branch
-- Phase 1 (Analysis), Phase 2 (Planning + Approval Gate), and Phase 5 (User Test) are skipped (`--dev` + local/autopilot drop the interactive test gate)
-- Phase 3: develop on Opus (instead of the Sonnet TDD cycle)
-- Phase 4: review as in the full pipeline, on the local branch diff; accepted blocking findings loop back to Phase 3, capped at 3 iterations
-- Phase 6: commit + push + PR (the local checkout prompt is natural in local mode  -  you're already there; no worktree removal needed, code is already in `$PROJECT_ROOT`)
-- Phase 7: report + channels (same as `--dev`)
-
-## 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:resume-local`, not a second Dev pass). Read that section rather than reasoning about it from scratch.
+Print the line above, then continue at the named entry with the same `$ARGUMENTS`. Do not run any phase from this file: it carries no tracker contract and no phase set.
 
-## Required: outward-facing payload contracts
-
-Skipping Analysis and Planning does not shorten the payload contracts. Before writing anything outward-facing, load `$HOME/.claude/multi-agent-refs/payload-contracts.md`  -  the canonical list of what to read for the PR body, the Jira comment, and the closing report, plus the markup dialect per surface. Improvising a payload shape from memory is the single most common failure of the fast modes.
-
-## Examples
-
-```bash
-/multi-agent:dev-local "PROJ-12345"                            # Jira
-/multi-agent:dev-local "Bug: LoginView dark mode"              # Free-text
-```
+This stub exists so the old name fails loudly and usefully for one minor release instead of silently doing nothing. It is deleted in the next one.

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

@@ -1,123 +1,21 @@
 ---
-description: "Fastest + local  -  Dev(Opus) + Review + autopilot, no worktree, zero interaction. Review runs and auto-fixes blocking findings. Use when a change should be developed on the current branch with no worktree and no prompts."
-description-tr: "En hızlı + lokal - Dev(Opus) + Review + autopilot, worktree yok, sıfır etkileşim. Review koşar, blocking bulguları otomatik düzeltir."
-allowed-tools: Agent, Bash, Read, Write, Edit, Glob, Grep, TaskCreate, TaskUpdate, TaskList, TaskGet, WebFetch, Skill
+description: "Retired alongside its worktree twin in v16.0.0, with nothing standing in for it. Invoke only to be pointed at /multi-agent:local-autopilot or the interactive picker."
+description-tr: "v16.0.0'da kaldırıldı, birebir karşılığı yok: gözetimsiz koşular artık her zaman tam pipeline. /multi-agent:local-autopilot veya /multi-agent:local'e yönlendirir."
 ---
 
-# multi-agent dev-local-autopilot  -  Fastest + Local
+# multi-agent dev-local-autopilot  -  Removed in v16.0.0
 
-> **Language (read FIRST)**: Before any status output, read `prefs.global.outputLanguage` and render every conversational line in it. `AskUserQuestion` `label`/`header` stay English, but its `question` and option `description`s render in `outputLanguage`; external payload bodies follow `outputLanguage` too (identifiers, commit messages, branch names stay English). Full contract: `$HOME/.claude/multi-agent-refs/rules.md` "Language Application".
+Same removal as `dev-autopilot`, on the no-worktree path. Depth is a question, autopilot may not ask one, and Full is the safer answer when nobody is watching.
 
-The triple `--dev` + `--local` + `autopilot`  -  the fastest form available. Zero confirmations, NO worktree.
-
-## Pipeline
-
-```
-Phase 0: Init       → project detection, branch check, state (NO worktree, NO confirmation)
-Phase 3: Dev        → direct development on Opus (automatic)
-Phase 4: Review     → gates + parallel review + triage, auto-fix
-Phase 6: Commit     → auto commit + push + PR (no local checkout prompt)
-Phase 7: Report     → Jira / Wiki + log + knowledge/memory
 ```
-
-Phase 1 (Analysis), Phase 2 (Planning + Approval Gate) and Phase 5 (User Test) are skipped. Review is not: accepted blocking findings are fixed automatically without a prompt, and the run halts rather than committing if they survive 3 rework cycles.
-
-## When to use it
-
-- Routine change you trust  -  you want it reviewed, not discussed
-- A CI / batch environment running the pipeline automatically  -  no user interaction
-- Prototype / spike  -  you care about speed, and the review that runs costs you no prompts
-
-## When NOT to use it
-
-- Production-bound change  -  at minimum use `--dev` (without autopilot), so you see the findings before the commit
-- Security-sensitive code  -  autopilot decides for you which accepted findings to fix, and commits when they are gone
-- A first big refactor  -  human review is required, and machine review does not substitute for it
-
-## Delegation
-
-Routes to the orchestrator with `--dev --local autopilot` flags. The pipeline contract matches [`dev-autopilot/SKILL.md`](../dev-autopilot/SKILL.md) exactly, with Phase 0 Step 8 (worktree creation) skipped.
-
-
-## Examples
-
-```bash
-/multi-agent:dev-local-autopilot "PROJ-12345"                  # Jira
-/multi-agent:dev-local-autopilot "Add retry to HomeNetworking" # Free-text
+/multi-agent:dev-local-autopilot has been removed. "Fast plus unattended" no
+longer exists as a combination.
+  1. /multi-agent:local-autopilot - unattended, full pipeline, no worktree
+  2. /multi-agent:local           - short pipeline, but asks the depth question
 ```
-## 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:resume-local`, not a second Dev pass). Read that section rather than reasoning about it from scratch.
-
-## Required: outward-facing payload contracts
-
-Before writing anything outward-facing  -  PR body, Jira comment, Confluence page, closing report  -  load `$HOME/.claude/multi-agent-refs/payload-contracts.md`. It names the canonical section set for each payload, the markup dialect per surface (PR body is Markdown, Jira is wiki markup  -  mixing them is a defect), and the token/duration numbers the closing report must carry. Improvising a payload shape from memory is the most common failure of the short modes.
-
-## Required: Phase Tracker Contract
-
-**The phase tracker is mandatory**  -  the agent cannot skip it. Full spec: [`$HOME/.claude/multi-agent-refs/tracker-contract.md`]($HOME/.claude/multi-agent-refs/tracker-contract.md).
-
-> **Autopilot mode:** user confirmations are skipped. The tracker is still mandatory  -  autopilot agent calls cannot skip it; skipping breaks `smoke-tracker-contract.sh`.
-
-> **Local mode:** no worktree is created, work happens on the current branch. Phase 0 Init still calls `init`  -  the `--local` flag is stored in tracker-state.json, and `:resume` restores the correct CWD.
 
-Two channels run in parallel at every phase boundary:
+If a cron job or script calls this name it needs editing, and the two options trade differently: option 1 stays unattended and will take longer and cost more per run, option 2 stays fast and needs a person.
 
-1. **State channel** (every CLI, identical): `phase-tracker.sh` writes to `tracker-state.json`. Drives `:resume`, `:log`, `:status`.
-2. **Visual channel** (CLI-specific): native widget on Claude Code, ANSI render on every other CLI. Without it the user sees no phase progress.
-
-```bash
-# Phase 0, very first shell call (every CLI):
-bash $HOME/.claude/scripts/phase-tracker.sh init "$TASK_ID"
-for p in "0:Init" "3:Dev" "4:Review" "6:Commit" "7:Report"; do
-  bash $HOME/.claude/scripts/phase-tracker.sh add "${p%%:*}" "${p#*:}"
-done
-bash $HOME/.claude/scripts/phase-tracker.sh update 0 in_progress
-
-# Every phase boundary (every CLI):
-bash $HOME/.claude/scripts/phase-tracker.sh update <N> in_progress|completed|failed|skipped
-
-# After every LLM call (every CLI):
-bash $HOME/.claude/scripts/phase-tracker.sh tokens <N> <in> <out> [cached]
-```
-
-### Visual channel  -  Claude Code (native TaskList widget, required)
-
-In Claude Code the agent MUST also drive the native TaskList widget so the user sees a sticky phase tile stack  -  this is the only progress signal Claude Code surfaces. Skipping these calls is the #1 source of "I don't see any phases" complaints.
-
-**TaskCreate ordering (strict)**: All TaskCreate calls fire in strict phase-number order BEFORE any TaskUpdate is applied. The native widget renders by creation order, not by phase number  -  out-of-order calls produce visually scrambled tile stacks (e.g. `1 ✓ · 2 ✓ · 4 ✓ · 0 ▶ · 3 ☐`) even when the underlying state is correct. Pre-marking phases as completed/skipped before Phase 0 starts is FORBIDDEN  -  register the tile in order, then flip status via TaskUpdate when the phase actually short-circuits. Full contract in `$HOME/.claude/multi-agent-refs/tracker-contract.md` section "TaskCreate ordering (strict)".
-
-```text
-# Phase 0 startup  -  register one tile per phase (0..N), capture the taskId, persist it:
-for each phase in 0:Init, 3:Dev, 4:Review, 6:Commit, 7:Report:
-  TaskCreate({ subject: "Phase <N>: <Name>", activeForm: "<doing-form>" })
-    -> returns taskId
-  bash $HOME/.claude/scripts/phase-tracker.sh meta <N> tasklist_id "<taskId>"
-
-# Phase entry  -  flip the tile to in_progress alongside the state update:
-TaskUpdate({ taskId: <saved>, status: "in_progress" })
-bash $HOME/.claude/scripts/phase-tracker.sh update <N> in_progress
-
-# Active sub-step inside a phase  -  update activeForm so the spinner header reflects what's happening now:
-TaskUpdate({ taskId: <saved>, activeForm: "Editing TopBarView.swift" })
-
-# Phase exit  -  flip to completed/failed/skipped on both channels:
-TaskUpdate({ taskId: <saved>, status: "completed" })
-bash $HOME/.claude/scripts/phase-tracker.sh update <N> completed
-```
-
-`--dev local autopilot` mode does NOT TaskCreate phases 1/2/5  -  those are not part of the `--dev local autopilot` phase set (`0:Init 3:Dev 4:Review 6:Commit 7:Report`). Only register tiles for the active set.
-
-#### TaskCreate ordering (strict)
-
-**All TaskCreate calls fire in strict phase-number order BEFORE any TaskUpdate is applied.** For `--dev local autopilot` that means: Phase 0 → Phase 3 → Phase 4 → Phase 6 → Phase 7. The native widget renders by creation order, not by phase number  -  out-of-order calls produce visually scrambled tile stacks. Full ordering contract in `$HOME/.claude/multi-agent-refs/tracker-contract.md` section "TaskCreate ordering (strict)".
-
-### Visual channel  -  Copilot CLI / plain shell
-
-These CLIs have no TaskList widget. After every state change the agent calls render, which prints a bordered ANSI card as the last tool result so the user sees an updated phase table:
-
-```bash
-bash $HOME/.claude/scripts/phase-tracker.sh render
-```
+Print the block above and stop. Do not pick an entry on the user's behalf: the two options differ in what gets skipped and who is watching, and that is their call. Autopilot passed to this stub still stops here - a zero-interaction contract does not authorise choosing a different pipeline than the one that was asked for.
 
-Do NOT call TaskCreate on these CLIs  -  the tool does not exist and the call fails.
+This stub exists so the old name fails loudly and usefully for one minor release instead of silently doing nothing. It is deleted in the next one.

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

@@ -55,22 +55,25 @@ 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  -  normal mode only;
-                           skipped for --dev, autopilot, --dev autopilot)
+                          (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
-                          (runs in dev + full; skipped in every autopilot and local variant)
+                          (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).
 
-  --dev pipeline (Phases 1-2 skipped; Review is NEVER skipped):
-  Init (same 8 steps), Dev with Opus, Review (same gates + triage),
-  Test (skipped in autopilot / --local), Commit + Report (menu still pauses).
+  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.
 
@@ -78,25 +81,25 @@ Pipeline (after Phase 0)  -  shown as visual cards in terminal:
 
 Modes:
 
-  (normal)             Full 8 phases, Sonnet dev, Plan Approval Gate active, parallel review + Fable triage
-  --dev                Fast: Init -> Dev(Opus) -> Review -> Test -> Commit -> Report
-  --local              No worktree  -  works directly on local branch
-  autopilot            Skip all confirmations INCLUDING plan gate, auto commit/PR
-                       (EXCEPT Phase 7 channels menu  -  always pauses)
-  --dev autopilot      Fastest path
-  --local --dev        Local + fast (no worktree, no analysis/plan gate  -  review still runs)
-
-Dedicated commands (same as flags above):
-
-  /multi-agent:dev "task"                       = multi-agent "task" --dev
-  /multi-agent:autopilot "task"                 = multi-agent "task" autopilot
-  /multi-agent:dev-autopilot "task"             = multi-agent "task" --dev autopilot
-  /multi-agent:local "task"                     = multi-agent "task" --local
-  /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
+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:
@@ -132,7 +135,7 @@ Post-Hoc & Side-Channel:
   /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 dev / dev-local. Read-only, never edits source.
+                              plan + one-page onboarding summary -> hand off to /multi-agent or :local. Read-only, never edits source.
 
 Setup & Maintenance:
 
@@ -166,7 +169,7 @@ Interactive Launchers:
 
   Both follow the same flow after selection:
     1. Branch selection (develop/release/main)
-    2. Mode: full pipeline or --dev
+    2. Depth: Full or Short
     3. Autopilot: yes/no
     4. Pipeline starts with the selected issue
 
@@ -267,17 +270,17 @@ Examples:
   /multi-agent "MOBILE-12345"
 
   # GitHub issue, fast mode, local
-  /multi-agent "#42" --dev --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 "LoginView dark mode fix" --dev autopilot         # iOS
+  /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" --dev        # Frontend
+  /multi-agent "Responsive layout broken on tablet"              # Frontend, choose Short
 
   # Review current diff only
   /multi-agent:review
@@ -328,22 +331,25 @@ 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 normal mode;
-                           --dev, autopilot, --dev autopilot'ta skip)
+                          (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
-                          (dev + full'de koşar; her autopilot ve local varyantında skip)
+                          (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).
 
-  --dev pipeline'ı (Faz 1-2 atlanır; Review ASLA atlanmaz):
-  Init (aynı 8 adım), Dev Opus ile, Review (aynı kapılar + triage),
-  Test (autopilot / --local'de atlanır), Commit + Report (menü yine durur).
+  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.
 
@@ -351,25 +357,24 @@ Pipeline (Phase 0'dan sonra)  -  terminalde görsel kart olarak görünür:
 
 Modlar:
 
-  (normal)             Tam 8 faz, Sonnet dev, Plan Onay Kapısı aktif, paralel review + Fable triage
-  --dev                Hızlı: Init -> Dev(Opus) -> Review -> Test -> Commit -> Report
-  --local              Worktree yok  -  doğrudan local branch'te çalışır
-  autopilot            Plan gate dahil tüm onayları atla, otomatik commit/PR
-                       (İSTİSNA: Phase 7 channels menüsü  -  her zaman durur)
-  --dev autopilot      En hızlı yol
-  --local --dev        Local + hızlı (worktree yok, analiz/plan gate yok  -  review yine koşar)
-
-Dedicated komutlar (yukarıdaki flag'lerin eşdeğeri):
-
-  /multi-agent:dev "task"                       = multi-agent "task" --dev
-  /multi-agent:autopilot "task"                 = multi-agent "task" autopilot
-  /multi-agent:dev-autopilot "task"             = multi-agent "task" --dev autopilot
-  /multi-agent:local "task"                     = multi-agent "task" --local
-  /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
+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:
@@ -405,7 +410,7 @@ Post-Hoc & Side-Channel:
   /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 -> dev / dev-local'e devreder. Read-only, kaynağı hiç düzenlemez.
+                              planı + tek sayfalık onboarding özeti -> /multi-agent veya :local'e devreder. Read-only, kaynağı hiç düzenlemez.
 
 Setup & Maintenance:
 
@@ -440,7 +445,7 @@ Rutinler (kendi tekrar eden işlerin):
 
   İkisi de seçim sonrası aynı akışı takip eder:
     1. Branch seçimi (develop/release/main)
-    2. Mode: tam pipeline ya da --dev
+    2. Derinlik: Tam ya da Kısa
     3. Autopilot: evet/hayır
     4. Pipeline seçilen issue ile başlar
 
@@ -541,17 +546,17 @@ Quality & Telemetry (advisory, default açık  -  prefs.global.* ile kapatılabi
   /multi-agent "MOBILE-12345"
 
   # GitHub issue, hızlı mode, local
-  /multi-agent "#42" --dev --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 "LoginView dark mode fix" --dev autopilot         # iOS
+  /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" --dev        # Frontend
+  /multi-agent "Responsive layout broken on tablet"              # Frontend, Kısa seç
 
   # Sadece mevcut diff'i review et
   /multi-agent:review

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

@@ -236,8 +236,10 @@ Show a concise version of the plan to the user too.
 
 | Option | What it does |
 |---|---|
-| `/multi-agent:dev-local` | No worktree; branches from the main development branch, fixes on the current checkout |
-| `/multi-agent:dev` | Opens a worktree; Opus fixes on a fresh branch + PR |
+| `/multi-agent:local` | No worktree; branches from the main development branch, fixes on the current checkout |
+| `/multi-agent` | Opens a worktree; fixes on a fresh branch + PR |
+
+Both ask Full or Short at Phase 0 Step 7.5; a standards sweep is usually already scoped, so Short is the common answer.
 
 Invoke the chosen command with the plan file as the task input, branching off the repo's main
 development branch (e.g. `chore/<module>-coding-standard`). The dev pipeline applies the fixes,

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

@@ -21,10 +21,8 @@ Run the full pipeline **without a worktree** and **with every confirmation skipp
 | `/multi-agent:autopilot "task"` | 7 phases (no User Test) | ✅ | ❌ (autopilot) |
 | `/multi-agent:local "task"` | 7 phases (no User Test) | ❌ | ✅ (interactive) |
 | **`/multi-agent:local-autopilot "task"`** | **7 phases (no User Test)** | **❌** | **❌ (autopilot)** |
-| `/multi-agent:dev "task"` | Init → Dev → Review → Test → Commit → Report | ✅ | ✅ |
-| `/multi-agent:dev-autopilot "task"` | Init → Dev → Review → Commit → Report | ✅ | ❌ |
-| `/multi-agent:dev-local "task"` | Init → Dev → Review → Commit → Report | ❌ | ✅ |
-| `/multi-agent:dev-local-autopilot "task"` | Init → Dev → Review → Commit → Report | ❌ | ❌ (fastest) |
+
+Depth is a separate axis, asked at Phase 0 Step 7.5 rather than encoded in the command name: Full runs every phase above, Short runs Dev → Review → Test → Commit → Report. The two autopilot rows never ask and always run Full.
 
 ## What changes
 

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

@@ -42,7 +42,7 @@ Plan bands (all five feed the single Step 4 table):
 Do not copy features blindly. The goal is the best *approaches*, reshaped so they are applicable to THIS project's stack, size, and constraints.
 
 1. **Identify the domain** of the current project (read README + package/build manifests): what kind of project is it (CLI, SDK, app, pipeline, library), what stack, who uses it.
-2. **Research the best-in-class** for that exact domain:
+2. **Research the best-in-class** for that exact domain. When `ai-analyst-toolkit` is enabled, run the first three bullets through its skills (`evidence-github`, `evidence-registry`, `signal-community`) rather than ad-hoc searching: they carry the query forms and the citation format, and they keep the evidence / signal line straight - a GitHub PR is a fact, a forum thread is one person's experience. Not enabled is a recorded no-op and the manual searches below still apply.
    - **GitHub**: search the domain terms + `stars:>50`; read the top repos' READMEs, architecture docs, CI configs, test layout.
    - **X / Twitter**: search the domain terms + "best practices" / "we switched to" / "lesson learned"; capture what practitioners and tool authors actually recommend right now (WebFetch/WebSearch on `x.com` / `twitter.com` threads).
    - **Reddit**: relevant subreddits for real-world pain points and adopted patterns.

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

@@ -8,7 +8,7 @@ allowed-tools: Agent, Bash, Read, Write, Edit, Glob, Grep, TaskCreate, TaskUpdat
 
 > **Language (read FIRST)**: Before any status output, read `prefs.global.outputLanguage` and render every conversational line in it. `AskUserQuestion` `label`/`header` stay English, but its `question` and option `description`s render in `outputLanguage`; external payload bodies follow `outputLanguage` too (identifiers, commit messages, branch names stay English). Full contract: `$HOME/.claude/multi-agent-refs/rules.md` "Language Application".
 
-You already did the work locally  -  wrote code on the current branch and maybe tested it by hand, or committed it outside the pipeline entirely. (As of v14.0.0 the `--dev` family reviews its own output, so this command is for work that had no pipeline run behind it, not a patch for a mode that skipped review.) `/multi-agent:resume-local` picks up from there and runs the **pipeline tail** over that existing local work in one command: parallel review, a build + test success gate, commit/push + PR, then the technical analysis and a **Jira comment with test scenarios**. It does NOT re-develop  -  Analysis / Planning / Dev (phases 1-3) are intentionally skipped; the diff already on the branch IS the input.
+You already did the work locally  -  wrote code on the current branch and maybe tested it by hand, or committed it outside the pipeline entirely. (As of v14.0.0 a Short run reviews its own output, so this command is for work that had no pipeline run behind it, not a patch for a mode that skipped review.) `/multi-agent:resume-local` picks up from there and runs the **pipeline tail** over that existing local work in one command: parallel review, a build + test success gate, commit/push + PR, then the technical analysis and a **Jira comment with test scenarios**. It does NOT re-develop  -  Analysis / Planning / Dev (phases 1-3) are intentionally skipped; the diff already on the branch IS the input.
 
 ## When to use it
 
@@ -18,7 +18,7 @@ You already did the work locally  -  wrote code on the current branch and maybe
 
 ## When NOT to use it
 
-- You haven't written the change yet  -  use `/multi-agent`, `/multi-agent:local`, or `/multi-agent:dev-local`.
+- You haven't written the change yet  -  use `/multi-agent` or `/multi-agent:local`.
 - You only want the review, nothing else  -  use `/multi-agent:review`. Only the report/channels  -  `/multi-agent:channels`. Only device UI testing  -  `/multi-agent:test` / `/multi-agent:manual-test`.
 
 ## Input
@@ -106,7 +106,7 @@ No TaskList widget. After every state change call `bash $HOME/.claude/scripts/ph
 ## Examples
 
 ```bash
-/multi-agent:dev-local "PROJ-12345"     # develop locally (Init→Dev→Commit→Report, no review/test)
+/multi-agent:local "PROJ-12345"         # develop locally, then answer Short at the depth question
 # ... you inspect / hand-test the change ...
 /multi-agent:resume-local                        # now: review + build/test + PR + Jira analysis & test scenarios
 ```

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

@@ -828,13 +828,13 @@ Stack skills ship as versioned plugins in the `{owner}/multi-agent-plugins` mark
    ```bash
    claude marketplace add {owner}/multi-agent-plugins 2>/dev/null || true
    ```
-2. Detect the project stack from markers and enable the matching plugin(s) plus the always-on common plugin in the project's `.claude/settings.json` `enabledPlugins`:
+2. Detect the project stack from markers and enable the matching plugin(s) plus the two always-on plugins in the project's `.claude/settings.json` `enabledPlugins`:
    - `.xcodeproj` / `Package.swift` / `*.xcworkspace` → `ai-ios-toolkit`
    - `build.gradle` / `settings.gradle` → `ai-android-toolkit`
    - `package.json` with `react`/`next` → `ai-frontend-toolkit`
    - `requirements.txt` / `pyproject.toml` / server `package.json` → `ai-backend-toolkit`
    - **no clear marker → default `ai-ios-toolkit`**
-   `ai-common-toolkit@multi-agent-plugins` is always set `true` alongside the stack plugin.
+   `ai-common-toolkit@multi-agent-plugins` and `ai-analyst-toolkit@multi-agent-plugins` are always set `true` alongside the stack plugin: neither is stack-specific.
 3. Report the enabled set. To change later, run `/multi-agent:stack <ios|android|frontend|backend|...>` in the repo. Pipeline Phase 1 auto-detects the stack for its own routing regardless of enablement.
 
 The marketplace repo name (`multi-agent-plugins`) is generic; a different org points `{owner}` at its own fork - nothing in the pipeline is coupled to a specific account.