@mmerterden/multi-agent-pipeline 10.12.0 → 11.1.0

package/pipeline/scripts/smoke-generate-issue.sh

@@ -1,26 +1,24 @@
 #!/usr/bin/env bash
-# smoke-generate-issue.sh  -  contract for /multi-agent:generate-task + generate-bug.
+# smoke-generate-issue.sh  -  contract for /multi-agent:generate.
 #
 # Verifies:
-#   1. All 5 files exist (2 commands, shared ref, 2 Copilot SKILL.md).
+#   1. All 3 files exist (1 command, shared ref, 1 Copilot/plugin SKILL.md).
 #   2. Frontmatter keys present on both surfaces.
-#   3. Commands delegate to refs/generate-issue.md and declare their ISSUE_TYPE.
+#   3. Command delegates to refs/generate-issue.md and asks the issue type.
 #   4. Approval gate documented and marked unskippable in the ref.
 #   5. Convention mining + createmeta + Agile sprint endpoints present.
 #   6. UTF-8 verbatim POST path (--rawfile + --data-binary) present.
-#   7. Profile section vocab: Task (Goal/Scope/Acceptance), Bug (Steps/Expected/Actual/Environment).
-#   8. Registration: dispatcher rows, inventory lists, count consistency (37).
+#   7. Standard template vocab: Task/Story (Scope/Acceptance/Test Scenarios), Bug (Steps/Expected/Actual/Environment), Swagger.
+#   8. Registration: dispatcher rows, inventory lists, count consistency (36).
 #   9. Forbidden strings absent (em-dash, section sign, the M-word, unicode_escape).
 
 set -euo pipefail
 
 HERE="$(cd "$(dirname "$0")" && pwd)"
 ROOT="$(cd "$HERE/../.." && pwd)"
-CMD_TASK="$ROOT/pipeline/commands/multi-agent/generate-task.md"
-CMD_BUG="$ROOT/pipeline/commands/multi-agent/generate-bug.md"
+CMD="$ROOT/pipeline/commands/multi-agent/generate.md"
 REF="$ROOT/pipeline/commands/multi-agent/refs/generate-issue.md"
-SKILL_TASK="$ROOT/pipeline/skills/shared/core/multi-agent-generate-task/SKILL.md"
-SKILL_BUG="$ROOT/pipeline/skills/shared/core/multi-agent-generate-bug/SKILL.md"
+SKILL="$ROOT/pipeline/skills/shared/core/multi-agent-generate/SKILL.md"
 DISPATCHER="$ROOT/pipeline/commands/multi-agent.md"
 CONTRACT="$ROOT/pipeline/commands/multi-agent/refs/cross-cli-contract.md"
 SYNC="$ROOT/pipeline/commands/multi-agent/sync.md"
@@ -32,30 +30,30 @@ pass() { PASS=$((PASS+1)); echo "  ✓ $1"; }
 fail() { FAIL=$((FAIL+1)); echo "  ✗ $1"; }
 
 echo "→ 1. files exist"
-for f in "$CMD_TASK" "$CMD_BUG" "$REF" "$SKILL_TASK" "$SKILL_BUG"; do
+for f in "$CMD" "$REF" "$SKILL"; do
   if [ -f "$f" ]; then pass "exists: ${f#$ROOT/}"; else fail "missing: ${f#$ROOT/}"; fi
 done
+# old split commands must be gone
+for f in "$ROOT/pipeline/commands/multi-agent/generate-task.md" "$ROOT/pipeline/commands/multi-agent/generate-bug.md"; do
+  if [ -f "$f" ]; then fail "stale file present: ${f#$ROOT/}"; else pass "removed: ${f##*/}"; fi
+done
 [ "$FAIL" -eq 0 ] || { echo "══ generate-issue smoke: $PASS passed, $FAIL failed ══"; exit 1; }
 
 echo ""
 echo "→ 2. frontmatter keys"
-for f in "$CMD_TASK" "$CMD_BUG"; do
-  head -5 "$f" | grep -q '^description:' && pass "description: ${f##*/}" || fail "description missing: ${f##*/}"
-  head -5 "$f" | grep -q '^argument-hint:' && pass "argument-hint: ${f##*/}" || fail "argument-hint missing: ${f##*/}"
-done
-for f in "$SKILL_TASK" "$SKILL_BUG"; do
-  head -8 "$f" | grep -q '^name: multi-agent-generate-' && pass "name: ${f%/*}" || fail "name missing: $f"
-  head -8 "$f" | grep -q '^language: en' && pass "language en" || fail "language missing: $f"
-  head -8 "$f" | grep -q '^user-invocable: true' && pass "user-invocable" || fail "user-invocable missing: $f"
-done
+head -5 "$CMD" | grep -q '^description:' && pass "description: ${CMD##*/}" || fail "description missing: ${CMD##*/}"
+head -5 "$CMD" | grep -q '^argument-hint:' && pass "argument-hint: ${CMD##*/}" || fail "argument-hint missing: ${CMD##*/}"
+head -8 "$SKILL" | grep -q '^name: multi-agent-generate$' && pass "name: multi-agent-generate" || fail "name wrong: $SKILL"
+head -8 "$SKILL" | grep -q '^language: en' && pass "language en" || fail "language missing: $SKILL"
+head -8 "$SKILL" | grep -q '^user-invocable: true' && pass "user-invocable" || fail "user-invocable missing: $SKILL"
 
 echo ""
-echo "→ 3. commands delegate to the shared ref with a profile"
-for f in "$CMD_TASK" "$CMD_BUG"; do
-  grep -Fq "refs/generate-issue.md" "$f" && pass "ref link: ${f##*/}" || fail "ref link missing: ${f##*/}"
+echo "→ 3. command delegates to the shared ref and asks the type"
+grep -Fq "refs/generate-issue.md" "$CMD" && pass "ref link present" || fail "ref link missing"
+for t in "Task" "Bug" "Story"; do
+  grep -Fq "$t" "$CMD" && pass "type offered: $t" || fail "type missing: $t"
 done
-grep -Fq '`ISSUE_TYPE` | `Task`' "$CMD_TASK" && pass "ISSUE_TYPE=Task declared" || fail "ISSUE_TYPE=Task missing"
-grep -Fq '`ISSUE_TYPE` | `Bug`' "$CMD_BUG" && pass "ISSUE_TYPE=Bug declared" || fail "ISSUE_TYPE=Bug missing"
+grep -Fqi "Pick issue type" "$REF" && pass "type-selection step present" || fail "type-selection step missing"
 
 echo ""
 echo "→ 4. approval gate documented and unskippable"
@@ -79,31 +77,38 @@ grep -Fq -- "--data-binary" "$REF" && pass "--data-binary present" || fail "--da
 grep -Fqi "humanizer" "$REF" && pass "humanizer pass referenced" || fail "humanizer missing"
 
 echo ""
-echo "→ 7. profile section vocabulary"
-for s in "Goal" "Scope" "Acceptance Criteria"; do
-  grep -Fq "$s" "$CMD_TASK" && pass "task section: $s" || fail "task section missing: $s"
+echo "→ 7. standard template vocabulary + auto-sizing + swagger"
+for s in "Scope" "Acceptance Criteria" "Test Scenarios"; do
+  grep -Fq "$s" "$REF" && pass "task/story section: $s" || fail "task/story section missing: $s"
 done
 for s in "Steps to Reproduce" "Expected Result" "Actual Result" "Environment"; do
-  grep -Fq "$s" "$CMD_BUG" && pass "bug section: $s" || fail "bug section missing: $s"
+  grep -Fq "$s" "$REF" && pass "bug section: $s" || fail "bug section missing: $s"
 done
+grep -Fqi "auto-sizing" "$REF" && pass "auto-sizing rule present" || fail "auto-sizing rule missing"
+grep -Fqi "swagger" "$REF" && pass "swagger context present" || fail "swagger context missing"
 
 echo ""
-echo "→ 8. registration + count consistency (37)"
-grep -Fq '| `generate-task' "$DISPATCHER" && pass "dispatcher routing: generate-task" || fail "dispatcher routing missing: generate-task"
-grep -Fq '| `generate-bug' "$DISPATCHER" && pass "dispatcher routing: generate-bug" || fail "dispatcher routing missing: generate-bug"
-grep -Fq "generate-task.md" "$DISPATCHER" && pass "dispatcher loading row" || fail "dispatcher loading row missing"
-grep -Fq "## 1. Command Inventory (37 commands)" "$CONTRACT" && pass "contract count = 37" || fail "contract count wrong"
-grep -Eq '(^|[ ,])generate-bug, generate-task([ ,]|$)' "$CONTRACT" && pass "contract list has both" || fail "contract list missing entries"
-grep -Fq "**37 commands are synced**" "$SYNC" && pass "sync count = 37" || fail "sync count wrong"
+echo "→ 8. registration + count consistency (36)"
+grep -Fq '| `generate ' "$DISPATCHER" && pass "dispatcher routing: generate" || fail "dispatcher routing missing: generate"
+grep -Fq "generate.md" "$DISPATCHER" && pass "dispatcher loading row" || fail "dispatcher loading row missing"
+grep -Fq "## 1. Command Inventory (36 commands)" "$CONTRACT" && pass "contract count = 36" || fail "contract count wrong"
+grep -Eq '(^|[ ,])generate, help([ ,]|$)' "$CONTRACT" && pass "contract list has generate" || fail "contract list missing generate"
+grep -Fq "**36 commands are synced**" "$SYNC" && pass "sync count = 36" || fail "sync count wrong"
 SYNC_SKILL="$ROOT/pipeline/skills/shared/core/multi-agent-sync/SKILL.md"
-grep -Fq "**37 commands are synced**" "$SYNC_SKILL" && pass "sync SKILL count = 37" || fail "sync SKILL count wrong (Copilot parity)"
-grep -Fq "generate-task" "$ROOT/pipeline/skills/shared/core/multi-agent-help/SKILL.md" && pass "help SKILL lists generators" || fail "help SKILL missing generators (Copilot parity)"
-grep -c "generate-task" "$HELP" | awk '{exit !($1>=2)}' && pass "help.md has EN + TR entries" || fail "help.md entries incomplete"
+grep -Fq "**36 commands are synced**" "$SYNC_SKILL" && pass "sync SKILL count = 36" || fail "sync SKILL count wrong (Copilot parity)"
+grep -Fq "generate" "$ROOT/pipeline/skills/shared/core/multi-agent-help/SKILL.md" && pass "help SKILL lists generate" || fail "help SKILL missing generate (Copilot parity)"
+grep -c "multi-agent:generate" "$HELP" | awk '{exit !($1>=2)}' && pass "help.md has EN + TR entries" || fail "help.md entries incomplete"
+# no stale split-command references anywhere in the synced surfaces
+if grep -rqE "generate-task|generate-bug" "$DISPATCHER" "$CONTRACT" "$SYNC" "$HELP" "$CMD" "$REF" "$SKILL"; then
+  fail "stale generate-task/generate-bug reference found"
+else
+  pass "no stale split-command references"
+fi
 
 echo ""
 echo "→ 9. forbidden strings absent"
 MWORD="MAN""DATORY"
-for f in "$CMD_TASK" "$CMD_BUG" "$REF" "$SKILL_TASK" "$SKILL_BUG"; do
+for f in "$CMD" "$REF" "$SKILL"; do
   if grep -q $'—\|§\|…' "$f"; then fail "forbidden unicode punctuation in ${f##*/}"; else pass "punctuation clean: ${f##*/}"; fi
   if grep -q "$MWORD" "$f"; then fail "forbidden word in ${f##*/}"; else pass "vocabulary clean: ${f##*/}"; fi
   if grep -q "unicode_escape" "$f" && ! grep -q "Never round-trip" "$f"; then fail "unicode_escape misuse in ${f##*/}"; else pass "encoding rule clean: ${f##*/}"; fi

package/pipeline/skills/.skills-index.json

@@ -1,7 +1,7 @@
 {
   "schemaVersion": "1.0.0",
-  "generatedAt": "2026-07-06T11:38:47.307Z",
-  "skillCount": 224,
+  "generatedAt": "2026-07-07T15:10:40.029Z",
+  "skillCount": 226,
   "entries": [
     {
       "name": "accessibility-compliance-accessibility-audit",
@@ -12,6 +12,15 @@
       "triggerPaths": [],
       "relativePath": "shared/external/accessibility-compliance-accessibility-audit/SKILL.md"
     },
+    {
+      "name": "agent-introspection-debugging",
+      "description": "|",
+      "platform": null,
+      "group": "external",
+      "triggerKeywords": [],
+      "triggerPaths": [],
+      "relativePath": "shared/external/agent-introspection-debugging/SKILL.md"
+    },
     {
       "name": "agentflow",
       "description": "Orchestrate autonomous AI development pipelines through your Kanban board (Asana, GitHub Projects, Linear). Manages multi-worker Claude Code dispatch, deterministic quality gates, adversarial review, per-task cost tracking, and crash-proof pipeline execution.",
@@ -327,6 +336,15 @@
       "triggerPaths": [],
       "relativePath": "shared/external/coreml/SKILL.md"
     },
+    {
+      "name": "council",
+      "description": "|",
+      "platform": null,
+      "group": "external",
+      "triggerKeywords": [],
+      "triggerPaths": [],
+      "relativePath": "shared/external/council/SKILL.md"
+    },
     {
       "name": "cryptokit",
       "description": "Use Apple CryptoKit for Swift cryptographic primitives. Use when hashing with SHA-2 or SHA-3, generating HMACs, encrypting with AES-GCM or ChaChaPoly, signing with P256/P384/P521/Curve25519 or ML-DSA keys, performing ECDH, HPKE, ML-KEM, or X-Wing key exchange, using Secure Enclave CryptoKit keys, or",
@@ -1156,22 +1174,13 @@
       "relativePath": "shared/core/multi-agent-garbage-collect/SKILL.md"
     },
     {
-      "name": "multi-agent-generate-bug",
-      "description": "Create a standards-compliant Jira Bug: mines project conventions, drafts in outputLanguage, full preview + explicit approval before create.",
+      "name": "multi-agent-generate",
+      "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.",
       "platform": null,
       "group": "core",
       "triggerKeywords": [],
       "triggerPaths": [],
-      "relativePath": "shared/core/multi-agent-generate-bug/SKILL.md"
-    },
-    {
-      "name": "multi-agent-generate-task",
-      "description": "Create a standards-compliant Jira Task: mines project conventions, drafts in outputLanguage, full preview + explicit approval before create.",
-      "platform": null,
-      "group": "core",
-      "triggerKeywords": [],
-      "triggerPaths": [],
-      "relativePath": "shared/core/multi-agent-generate-task/SKILL.md"
+      "relativePath": "shared/core/multi-agent-generate/SKILL.md"
     },
     {
       "name": "multi-agent-help",
@@ -1578,6 +1587,15 @@
       "triggerPaths": [],
       "relativePath": "shared/external/room-database/SKILL.md"
     },
+    {
+      "name": "search-first",
+      "description": "|",
+      "platform": null,
+      "group": "external",
+      "triggerKeywords": [],
+      "triggerPaths": [],
+      "relativePath": "shared/external/search-first/SKILL.md"
+    },
     {
       "name": "shareplay-activities",
       "description": "Build shared real-time experiences using GroupActivities and SharePlay. Use when implementing shared media playback, collaborative app features, synchronized game state, or any FaceTime, Messages, AirDrop, or nearby visionOS group activity on iOS, macOS, tvOS, or visionOS.",

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

@@ -0,0 +1,51 @@
+---
+name: multi-agent-generate
+language: en
+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."
+user-invocable: true
+argument-hint: "[\"<free-text description>\"] [figma-url] [swagger-url]  -  all optional, asked interactively when missing"
+---
+
+# multi-agent generate  -  Standards-Compliant Jira Issue Creator
+
+**Input**: $ARGUMENTS
+
+Creates exactly one Jira issue, and only after explicit approval. The issue type (Task / Bug / Story) is asked at the start of every run. No branches, no commits, no worktrees. The description comes from the type's standard template (baseline, not a mined heading set); sections auto-size  -  a conditional section renders only when its trigger is present, otherwise the heading is omitted.
+
+> **Language**: issue content (summary + description) and user-facing questions follow `prefs.global.outputLanguage`  -  intentional exception to the "external payloads stay English" default (the issue is authored for the user's team). Code identifiers and URLs stay verbatim.
+
+## Standard templates (A = always, C = conditional)
+
+- **Task**: Detailed Description (A), Scope (A), Acceptance Criteria (A), Test Scenarios (A); API Contract/Swagger (C), Design Reference (C), Screenshots (C), Notes (C).
+- **Bug**: Detailed Description (A), Steps to Reproduce (A), Expected Result (A), Actual Result (A), Environment (A); Screenshots/Logs (C), Regression/Test Scenario (C), API Contract (C), Design Reference (C), Notes (C).
+- **Story**: User Story (A), Detailed Description (A), Scope (A), Acceptance Criteria (A), Test Scenarios (A); API Contract/Swagger (C), Design Reference (C), Screenshots (C), Dependencies/Notes (C).
+
+A `C` section fires on: Design Reference → Figma URL; Screenshots → pasted image or fetched Figma render; API Contract → Swagger URL / contract / endpoint mention; Notes → real content. No empty placeholder headings; never invent content.
+
+## Steps
+
+1. **Account + token**  -  pick the Jira account (auto-select when single), then:
+   ```bash
+   TOKEN=$(~/.copilot/lib/credential-store.sh get "$ACCOUNT_JIRA_TOKEN_KEY")
+   ```
+   Missing/expired (401) → Token Save Flow; user skips → abort, nothing created.
+2. **Project key**  -  `figmaConfig.jira.projectKey` → `prefs.global.defaultJiraKey` → fetch `GET /rest/api/2/project`, ask, cache the choice.
+3. **Pick issue type**  -  ask (Task / Bug / Story), never inferred silently → `ISSUE_TYPE`. Drives the mining JQL, field discovery, and section skeleton.
+4. **Parse input**  -  `figma.com` URL → `FIGMA_URL` (node-id `-` → `:`); OpenAPI/Swagger URL (`swagger`/`openapi`/`api-docs`/`.json`/`.yaml`) → `SWAGGER_URL`; pasted images → screenshots; log/stack-trace text stays with `FREE_TEXT`; the rest is `FREE_TEXT`. All empty → ask for a description. Figma/Swagger/screenshots are always optional.
+5. **Convention mining + field discovery + sprint** (read-only GETs):
+   - Sample: `GET /rest/api/2/search?jql=project={KEY} AND issuetype={TYPE} ORDER BY created DESC&fields=summary,description,labels,components,priority,fixVersions,issuelinks&maxResults=30`. Extract summary prefix pattern (>= 40% threshold), top-5 labels/components, modal priority, epic usage rate, and **test-scenario style**: linked Test-family issues (Xray/Zephyr) → reference them; else a dominant test-scenario heading/checklist style (>= 40%) → reuse it; else inline a skeleton derived from Acceptance Criteria (user edits, never fabricated).
+   - `GET /rest/api/2/issue/createmeta?projectKeys={KEY}&issuetypeNames={TYPE}&expand=projects.issuetypes.fields` (404/empty → paged DC endpoint fallback). Required custom fields → step 7 questions with allowedValues options. Detect Sprint/Epic/Team fields generically via `schema.custom` ids.
+   - `GET /rest/agile/1.0/board?projectKeyOrId={KEY}` → (ask when multiple) → `GET /rest/agile/1.0/board/{id}/sprint?state=active`. No board/Agile 404 → sprint option silently omitted.
+6. **External context** (only for provided sources, each failure-isolated, never blocks create):
+   - **Figma** (`FIGMA_URL` set)  -  3-tier chain (MCP → REST figma_pat → user screenshot); standalone command, MCP allowed here.
+   - **Swagger** (`SWAGGER_URL` set or contract pasted)  -  fetch the spec, extract ONLY the referenced endpoints (paths/operationIds/tags named in `FREE_TEXT`, else the pointed-at group): method + path + one-line summary + key request/response fields. Never crawl the whole spec. Fetch failure → link-only or omit.
+   - **Screenshots**  -  staged for the step 8 attachment opt-in, referenced inline with `!file|thumbnail!`.
+7. **Draft + clarifying questions**  -  compose summary (`{minedPrefix} {title}`, 255 trunc) + description from the type's **standard template** in Jira wiki markup (`h3.`), auto-sizing conditional sections, humanizer pass, in `outputLanguage`; body to a file for `jq -n --rawfile` (UTF-8 verbatim, `--data-binary @file`, no re-encode). Ask ONLY genuinely unknown fields: component, epic (when usage rate is high), priority (when norm ambiguous), labels, assignee, sprint vs backlog, required customs, and any always-present section still empty (Bug Steps/Environment, or a Task/Story with no derivable Scope/AC). Never invent content the user did not supply.
+8. **Full preview + approval gate (never skipped)**  -  render the complete issue (all fields + full description + attachment plan, uploads default off). Ask: `Approve` / `Edit` (apply → re-render → re-ask, loop) / `Cancel` (nothing created). No flag or mode bypasses this gate.
+9. **Create**  -  `POST /rest/api/2/issue` with `jq -n --rawfile` payload + `curl --data-binary @file`. 400 field errors → show verbatim, re-ask those fields, re-preview.
+10. **Post-create** (each failure-isolated: warn + continue): sprint chosen → `POST /rest/agile/1.0/sprint/{id}/issue` `{"issues":["KEY"]}`; Figma → `POST /rest/api/2/issue/{KEY}/remotelink`; Swagger → `remotelink` with title "API contract"; screenshots opt-in → `POST /rest/api/2/issue/{KEY}/attachments` with `X-Atlassian-Token: no-check`.
+11. **Report**  -  `Created {KEY}: https://{host}/browse/{KEY}` + which post-steps ran.
+
+## Error paths
+
+401 token → Save Flow or abort (nothing created); mining/createmeta 403 → standard-template defaults + reactive 400 handling; zero sampled issues → skip mining, AC-derived test-scenario skeleton, note in preview; no board/active sprint → backlog implied, say so; Figma/Swagger failure → degrade (link-only or omit), never block; create 5xx → one retry then abort keeping the draft file; post-create failure → warn + continue.

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

@@ -98,8 +98,7 @@ Utility Commands (dash form on Copilot, colon form on Claude Code):
   /multi-agent:purge          Worktree + logs  -  full reset (double confirm)
   /multi-agent:channels       Post multi-channel report (Jira/Confluence/Wiki/PR)
   /multi-agent:review         Review current diff only
-  /multi-agent:generate-task ["desc"] [figma-url]  Create a Jira Task matching team conventions (preview + approval)
-  /multi-agent:generate-bug ["desc"] [figma-url]   Create a Jira Bug matching team conventions (preview + approval)
+  /multi-agent:generate ["desc"] [figma-url] [swagger-url]  Create a Jira Task/Bug/Story matching team conventions (asks type + preview + approval)
   /multi-agent:sync           Sync ecosystem (Claude + Copilot + website + remote-control)
   /multi-agent:setup          Keychain tokens + Git identity + language onboarding
   /multi-agent:language [en|tr]  Show or set prompt language
@@ -235,8 +234,7 @@ Utility Komutları:
   /multi-agent:purge          Worktree + log'lar  -  tam reset (çift onay)
   /multi-agent:channels       Multi-channel rapor gönder (Jira/Confluence/Wiki/PR)
   /multi-agent:review         Sadece mevcut diff'i review et
-  /multi-agent:generate-task ["açıklama"] [figma-url]  Takım standartlarına uygun Jira Task oluştur (önizleme + onay)
-  /multi-agent:generate-bug ["açıklama"] [figma-url]   Takım standartlarına uygun Jira Bug oluştur (önizleme + onay)
+  /multi-agent:generate ["açıklama"] [figma-url] [swagger-url]  Takım standartlarına uygun Jira Task/Bug/Story oluştur (tip sorar + önizleme + onay)
   /multi-agent:sync           Ekosistemi senkronize et
   /multi-agent:setup          Keychain token + Git kimliği + dil onboarding
   /multi-agent:language [en|tr]  Prompt dilini göster veya ayarla

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

@@ -158,12 +158,12 @@ When invoked with the `release` argument:
 |-------------|-------------|
 | `~/.claude/commands/multi-agent/{cmd}.md` | `~/.copilot/skills/multi-agent-{cmd}/SKILL.md` |
 
-**37 commands are synced** (canonical inventory  -  must match `cross-cli-contract.md` section 1; drift = contract violation):
+**36 commands are synced** (canonical inventory  -  must match `cross-cli-contract.md` section 1; drift = contract violation):
 
 ```
 analysis, analysis-resolve, autopilot, build-optimize, channels, delete, dev,
 dev-autopilot, dev-local, dev-local-autopilot, diff-explain, finish, garbage-collect,
-generate-bug, generate-task, help, issue, jira, kill, language, local,
+generate, help, issue, jira, kill, language, local,
 local-autopilot, log, manual-test, prune-logs, purge, refactor, resume, review,
 scan, search, setup, stack, status, sync, test, update
 ```

package/pipeline/skills/shared/external/agent-introspection-debugging/SKILL.md

@@ -0,0 +1,69 @@
+---
+name: agent-introspection-debugging
+version: 1.0.0
+description: |
+  Structured self-debugging for an agent that is stuck, looping, or failing
+  repeatedly. Replaces blind re-prompting with capture -> diagnose -> contained
+  recovery -> report. Use when the same step fails twice, a loop is not making
+  progress, tool calls keep erroring, or you are about to retry without a new
+  hypothesis.
+---
+
+# Agent Introspection Debugging
+
+When an agent is stuck, the instinct is to try again harder. That burns tokens
+and usually reproduces the failure. This is a workflow, not a hidden runtime:
+it forces you to name the failure, classify it, take the smallest action that
+changes the diagnosis, and report honestly  -  before retrying.
+
+## When to use
+
+- The same step failed twice, or a fix loop is not converging.
+- Tool calls keep erroring (connection refused, rate limit, stale state).
+- You are about to retry with no new hypothesis  -  the signal to stop and think.
+
+## Phase 1 — Capture
+
+Write the failure state down before acting:
+
+- Goal (what were you actually trying to do).
+- The exact error or wrong output.
+- Last successful step, and the first failing step.
+- What is repeating (same error? different each time?).
+- Environment assumptions (cwd, branch, service up, auth present).
+
+## Phase 2 — Diagnose
+
+Match the symptom to a cause before choosing an action:
+
+| Symptom | Likely cause | First check |
+| --- | --- | --- |
+| Hit max tool calls / no end | unbounded loop | is there a stop condition? |
+| Context overflow | unbounded notes/output | what is being accumulated? |
+| Connection refused | service/port down | is it running, right port? |
+| Rate limited (429) | retry storm | back off, not retry faster |
+| Diff/state looks stale | cwd or branch drift | pwd, current branch |
+| Tests still failing after "fix" | wrong hypothesis | re-read the actual assertion |
+
+## Phase 3 — Contained recovery
+
+Take the single smallest action that changes the diagnosis surface  -  not a
+broad rewrite. Change one variable, re-observe. The goal is new information,
+not a gamble on a fix.
+
+**Honesty guard:** do not claim recovery actions you are not actually
+performing. "Reset agent state," "cleared the cache," "restarted the service"
+are real only if you did them through a real tool. Narrating an imaginary
+auto-heal is worse than reporting that you are blocked.
+
+## Phase 4 — Introspection report
+
+Emit a short structured record:
+
+- Root cause (the confirmed one, not the first guess).
+- Result: `success` | `partial` | `blocked`.
+- Cost: rough tokens/time burned on the failure.
+- Preventive change: the rule, check, or guard that would stop this class of
+  failure next time  -  feed it back into the ledger or the plan.
+
+Then, and only then, retry  -  with the new hypothesis, not the old one.

package/pipeline/skills/shared/external/council/SKILL.md

@@ -0,0 +1,69 @@
+---
+name: council
+version: 1.0.0
+description: |
+  Convene a multi-voice council for ambiguous decisions, tradeoffs, and
+  go/no-go calls. Use when several valid paths exist and you need structured
+  disagreement before choosing, not code review or implementation planning.
+  Triggers on: "should we X or Y", "second opinion", "is this worth it",
+  "ship now or wait", requests for dissent or multiple perspectives.
+---
+
+# Council
+
+Convene a short panel of distinct advisory voices for a decision that has more
+than one credible answer. The point is structured disagreement: surface the
+tradeoffs and the strongest case against your leading option before you commit,
+so the choice survives contact with its own weaknesses.
+
+## When to use
+
+- A decision has multiple credible paths and no obvious winner.
+- You need the tradeoffs made explicit, not smoothed over.
+- Anchoring is a risk: the conversation has drifted toward one option and you
+  want it challenged on purpose.
+- A go / no-go would benefit from an adversarial pass.
+
+Examples: monorepo vs polyrepo, ship now vs hold for polish, feature-flag vs
+full rollout, build vs adopt, narrow scope vs keep strategic breadth.
+
+## When NOT to use
+
+| Instead of council | Use |
+| --- | --- |
+| Checking whether output is correct | a verification pass / tests |
+| Breaking a feature into steps | a planner |
+| Designing system architecture | an architect |
+| Finding bugs or security issues | a code reviewer |
+
+If there is a single correct answer discoverable from the code or the spec, do
+that work directly. Council is for genuine judgment calls.
+
+## The voices
+
+Run each as a distinct perspective (in-context, or as parallel sub-agents when
+the decision is high-stakes). Give each the same framing and ask for its
+strongest honest position, not a hedge.
+
+- **Skeptic** — attacks the leading option. What breaks it, what is being
+  assumed, what is the failure mode nobody is naming?
+- **Pragmatist** — optimizes for shipping and reversibility. What is the
+  cheapest path that keeps options open? What is good-enough now?
+- **Critic** — optimizes for long-term cost and coherence. What does this choice
+  lock in? What is the second-order effect in six months?
+
+Add a fourth domain voice (security, cost, UX) only when the decision hinges on
+that axis.
+
+## Protocol
+
+1. State the decision in one sentence and list the candidate options.
+2. Give each voice the same context; collect one crisp position + its single
+   strongest argument from each. No consensus-seeking at this stage.
+3. Surface the real disagreements as a tradeoff table (option x axis).
+4. Decide, and write down the losing option's best argument and the condition
+   under which you would revisit. A decision you cannot argue against is a
+   decision you have not understood.
+
+Keep it bounded: three voices, one round, one page. Council informs a choice; it
+does not replace making one.

package/pipeline/skills/shared/external/search-first/SKILL.md

@@ -0,0 +1,76 @@
+---
+name: search-first
+version: 1.0.0
+description: |
+  Research-before-coding workflow. Before writing a custom implementation,
+  check what already exists (repo utilities, installed libraries, packages,
+  internal components) and decide adopt / extend / compose / build on evidence.
+  Use at the start of any non-trivial feature or utility, especially when you
+  are about to reach for a new dependency or hand-roll something common.
+---
+
+# Search-First
+
+Reinventing an existing utility, or pulling a new dependency for something the
+codebase already solves, is one of the most common and most expensive agent
+mistakes. Search-first makes "does this already exist?" a required step before
+"how do I write it," and records the answer so the decision is auditable.
+
+## When to use
+
+- Starting a feature or utility that is plausibly a solved problem.
+- About to add a dependency (verify it is warranted and not already present).
+- About to hand-roll parsing, retry, caching, date math, validation, auth,
+  pagination, or any other well-trodden pattern.
+
+Skip it for genuinely novel, project-specific logic where no prior art exists.
+
+## The workflow
+
+### 0. Preflight (honesty gate)
+
+List the search channels actually available: the repo itself, installed
+dependencies, the package registry, internal component/skill catalogs, docs.
+If a channel is unreachable, say so explicitly. Never claim "nothing found"
+when a channel was simply not checked  -  silent skipping is the failure mode
+this step exists to prevent.
+
+### 1. Need analysis
+
+State in one line what capability is needed and the hard constraints
+(performance, license, platform, API shape). This is the query.
+
+### 2. Parallel search
+
+Search the channels concurrently, not one at a time:
+- the repo (existing utilities, similar call sites, patterns already in use);
+- installed dependencies (is it already a transitive capability?);
+- the package registry (mature options);
+- internal catalogs (components, skills, shared modules).
+
+### 3. Evaluate
+
+Score each candidate on functionality fit, maintenance/health, docs, license,
+and integration cost. Keep it to a short comparison, not a survey.
+
+### 4. Decide (matrix)
+
+| Situation | Decision |
+| --- | --- |
+| Existing thing fits as-is | **Adopt** |
+| Existing thing fits with a small addition | **Extend** it in place |
+| Two existing pieces combine to fit | **Compose** them |
+| Nothing fits and the need is real | **Build** minimal custom code |
+
+### 5. Implement
+
+Only now write code, and only the minimum the decision calls for. Record the
+decision and the rejected alternatives in the change description so the next
+person does not redo the search.
+
+## Anti-patterns
+
+- **Jumping to code** before step 0-4.
+- **Silent skipping** — reporting no prior art when a channel was down or
+  unchecked.
+- **Dependency reflex** — adding a package for a one-liner the repo already has.

package/pipeline/skills/skills-index.md

@@ -3,11 +3,12 @@
 > Auto-generated by `pipeline/scripts/build-skills-index.mjs`  -  do not hand-edit.
 > Regenerate with `node pipeline/scripts/build-skills-index.mjs`.
 
-**224 skills** across 5 groups.
+**226 skills** across 5 groups.
 
 | Group | Name | Platform | Description |
 |-------|------|----------|-------------|
 | external | `accessibility-compliance-accessibility-audit` |  -  | You are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. Conduct audits, i |
+| external | `agent-introspection-debugging` |  -  | \| |
 | external | `agentflow` |  -  | Orchestrate autonomous AI development pipelines through your Kanban board (Asana, GitHub Projects, Linear). Manages multi-worker Claude Code |
 | external | `alarmkit` |  -  | Implement AlarmKit alarms and countdown timers for iOS and iPadOS with Lock Screen, Dynamic Island, StandBy, and paired Apple Watch system U |
 | external | `android_ui_verification` |  -  | Automated end-to-end UI testing and verification on an Android Emulator using ADB. |
@@ -43,6 +44,7 @@
 | external | `core-motion` |  -  | Access Core Motion accelerometer, gyroscope, magnetometer, device-motion, pedometer, activity-recognition, altitude, headphone motion, batch |
 | external | `core-nfc` |  -  | Read and write NFC tags using CoreNFC. Use when scanning NDEF tags, reading ISO7816/ISO15693/FeliCa/MIFARE tags, writing NDEF messages, hand |
 | external | `coreml` |  -  | Integrate Core ML models in iOS apps for on-device machine learning inference. Covers model loading (.mlmodel, .mlpackage, .mlmodelc), predi |
+| external | `council` |  -  | \| |
 | external | `cryptokit` |  -  | Use Apple CryptoKit for Swift cryptographic primitives. Use when hashing with SHA-2 or SHA-3, generating HMACs, encrypting with AES-GCM or C |
 | external | `css-modern` |  -  | Modern CSS: container queries, nesting, @layer, Grid/Flexbox patterns, custom properties, animations, and transitions |
 | external | `database-patterns` |  -  | Database patterns: SQL best practices (PostgreSQL), indexing, query optimization, migrations, schema design, ORMs (SQLAlchemy, Prisma, Drizz |
@@ -135,8 +137,7 @@
 | core | `multi-agent-diff-explain` |  -  | Map Phase 4 triage findings to branch diff lines. Read-only post-hoc command, used after review to answer 'which finding lines up with which |
 | core | `multi-agent-finish` |  -  | Continue already-done LOCAL work through the pipeline tail: Review → Build+Test → Commit/PR → Report (technical analysis + Jira test-scenari |
 | core | `multi-agent-garbage-collect` |  -  | Sweep leftover /tmp scratch (picker state, review diffs, channel payloads, analysis drafts) from past runs. Dry-run first; confirms before d |
-| core | `multi-agent-generate-bug` |  -  | Create a standards-compliant Jira Bug: mines project conventions, drafts in outputLanguage, full preview + explicit approval before create. |
-| core | `multi-agent-generate-task` |  -  | Create a standards-compliant Jira Task: mines project conventions, drafts in outputLanguage, full preview + explicit approval before create. |
+| core | `multi-agent-generate` |  -  | Create a standards-compliant Jira issue (Task / Bug / Story): asks the type, mines project conventions, drafts from a standard template with |
 | core | `multi-agent-help` |  -  | Multi-agent pipeline usage guide  -  renders in EN or TR per prefs.global.outputLanguage (falls back to promptLanguage for backward compatib |
 | core | `multi-agent-issue` |  -  | List unassigned GitHub issues, pick one, auto-assign, and launch the multi-agent pipeline. |
 | core | `multi-agent-jira` |  -  | List open Jira issues, pick one, and launch the multi-agent pipeline. |
@@ -182,6 +183,7 @@
 | external | `rest-api-design` |  -  | REST API design: HTTP methods, status codes, pagination, versioning, rate limiting, caching headers, OpenAPI documentation |
 | external | `retrofit-networking` |  -  | Build networking layers on Android with Retrofit, OkHttp, and Kotlin Coroutines. Covers suspend functions in API interfaces, OkHttp intercep |
 | external | `room-database` |  -  | Implement Room database persistence on Android with @Entity, @Dao, @Database, Flow-based reactive queries, TypeConverters for complex types, |
+| external | `search-first` |  -  | \| |
 | external | `shareplay-activities` |  -  | Build shared real-time experiences using GroupActivities and SharePlay. Use when implementing shared media playback, collaborative app featu |
 | external | `speech-recognition` |  -  | Transcribe speech to text using Apple's Speech framework. Use when implementing live microphone transcription with AVAudioEngine, recognizin |
 | external | `spm-build-analysis` |  -  | Analyze Swift Package Manager dependencies, package plugins, module variants, and CI-oriented build overhead that slow Xcode builds. Use whe |

package/pipeline/commands/multi-agent/generate-bug.md

@@ -1,33 +0,0 @@
----
-description: "Create a standards-compliant Jira Bug: mines project conventions, drafts in outputLanguage, full preview + explicit approval before create."
-argument-hint: "[\"<free-text description>\"] [figma-url]  -  both optional; pasted logs/screens in the text land in Steps to Reproduce / Environment"
----
-
-# multi-agent generate-bug  -  Standards-Compliant Jira Bug Creator
-
-**Input**: $ARGUMENTS
-
-Creates exactly one Jira **Bug**, and only after explicit approval. No branches, no commits, no worktrees, no pipeline chaining. The draft learns the target project's conventions from its recent Bugs (summary format, description template, labels, components, priority norms) and offers active-sprint placement when a sprint is running.
-
-> **Language**: instruction prose here is English. AskUserQuestion `question`/`description` and the issue content (summary + description) follow `prefs.global.outputLanguage`  -  an intentional exception to the "external payloads stay English" default, because the issue is authored for the user's team. `label`/`header` stay English.
-
-## Profile
-
-| Key | Value |
-|---|---|
-| `ISSUE_TYPE` | `Bug` |
-| Default description sections | Steps to Reproduce, Expected Result, Actual Result, Environment, Design Reference (only when a Figma URL is given), Notes |
-| JQL sample filter | `issuetype = Bug` |
-| Priority default | mined norm from sampled Bugs (bug priorities often skew higher  -  respect the project's own norm) |
-
-## Flow
-
-Read `$HOME/.claude/commands/multi-agent/refs/generate-issue.md` and execute the 11-step shared flow with the profile above. Non-negotiables restated:
-
-- Free-text parsing maps logs, stack traces, and device/OS mentions into Steps to Reproduce and Environment; anything underivable is asked in step [7/11], never invented.
-- Ask the user (AskUserQuestion) about every genuinely unknown field  -  component, epic, priority, labels, assignee, sprint vs backlog, required custom fields, missing Steps to Reproduce / Environment.
-- Step [8/11] full preview + approval gate always runs. `Approve` / `Edit` (loop) / `Cancel`. No bypass exists.
-
-## Error paths
-
-See `refs/generate-issue.md` Error paths. No command-specific additions.