@mmerterden/multi-agent-pipeline 10.12.0 → 11.0.0

package/CHANGELOG.md

@@ -14,6 +14,33 @@ Internal file-layout changes that don't affect the slash-command surface are sti
 
 ---
 
+## [11.0.0] - 2026-07-07
+
+Breaking: the two issue creators `generate-task` and `generate-bug` are merged
+into a single `generate` command. The command surface shrinks from 37 to 36
+commands, so this is a major bump per the versioning policy (a renamed/removed
+command is a breaking surface change).
+
+- **New `/multi-agent:generate`** asks the issue type (Task / Bug / Story) at the
+  start of every run, then mines the project's recent same-type issues for
+  conventions and drafts the issue.
+- **Standard template baseline with auto-sizing.** Each type has a fixed section
+  skeleton (Task/Story: Detailed Description, Scope, Acceptance Criteria, Test
+  Scenarios; Bug: Detailed Description, Steps to Reproduce, Expected/Actual
+  Result, Environment). Conditional sections (Design Reference, API Contract /
+  Swagger, Screenshots, Notes) render only when their trigger is present  -  no
+  empty placeholder headings, nothing invented.
+- **Test Scenarios pulled from Jira convention.** Detects linked Xray/Zephyr test
+  issues or a dominant test-scenario heading style and reuses it; falls back to an
+  AC-derived skeleton the user edits.
+- **Swagger / API Contract section.** When a Swagger/OpenAPI URL or contract is
+  given, fetches only the referenced endpoints (method + path + key fields) and
+  links the spec. No full-spec crawl; failures degrade to link-only.
+- **Removed** `generate-task` and `generate-bug` on both CLIs (Claude Code +
+  Copilot) and the plugin skill set. The shared `refs/generate-issue.md` flow is
+  now 12 steps with a dedicated type-selection step; the hard approval gate is
+  unchanged.
+
 ## [10.12.0] - 2026-07-06
 
 Two trust upgrades: every external channel post now shows a plan-mode-style

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mmerterden/multi-agent-pipeline",
-  "version": "10.12.0",
+  "version": "11.0.0",
   "description": "8-phase AI development pipeline with full orchestration on Claude Code and Copilot CLI. Analysis, planning, TDD, CLI-aware parallel review with consensus surfacing + Fable triage, default-FAIL evidence gates, secret + intent guards, per-phase cost ledger, persistent learnings memory, wiki generation, commit automation. Token-preserving uninstall.",
   "type": "module",
   "main": "index.js",

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

@@ -0,0 +1,34 @@
+---
+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."
+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, no pipeline chaining. The draft learns the target project's conventions from its recent same-type issues (summary format, labels, components, priority norms, test-scenario style) 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.
+
+## Issue types
+
+Type is chosen at step [3/11] via AskUserQuestion (never inferred silently). Each type has a standard template baseline; sections auto-size (see `refs/generate-issue.md` for the full A/C matrix and inclusion rules).
+
+| Type | Always-present sections | Conditional sections (included only when their trigger is present) |
+|---|---|---|
+| `Task` | Detailed Description, Scope, Acceptance Criteria, Test Scenarios | API Contract / Swagger, Design Reference, Screenshots, Notes |
+| `Bug` | Detailed Description, Steps to Reproduce, Expected Result, Actual Result, Environment | Screenshots / Logs, Regression / Test Scenario, API Contract, Design Reference, Notes |
+| `Story` | User Story, Detailed Description, Scope, Acceptance Criteria, Test Scenarios | API Contract / Swagger, Design Reference, Screenshots, Dependencies / Notes |
+
+## Flow
+
+Read `$HOME/.claude/commands/multi-agent/refs/generate-issue.md` and execute the 11-step shared flow. Non-negotiables restated:
+
+- Ask the user (AskUserQuestion) for the issue type first, then about every genuinely unknown field  -  component, epic, priority, labels, assignee, sprint vs backlog, required custom fields.
+- A conditional section renders only when its trigger is present (Figma URL, pasted screenshot/log, Swagger URL/contract, real Notes content). No empty placeholder headings; content the user did not supply and mining could not derive is never invented.
+- 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.

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

@@ -111,8 +111,7 @@ Post-Hoc & Side-Channel:
   /multi-agent:analysis ["analysis-name"]  Feature-spec analysis (Figma + Swagger + Confluence + repos) → per-platform v3 doc (23-section Full / 7-section Lite)
   /multi-agent:analysis-resolve [doc]      Resolve Section 20 open questions of an analysis doc, one at a time with source-labeled candidates
   /multi-agent:build-optimize iOS-only Xcode build perf wrapper → benchmark + analyze + recommend-first .build-benchmark/optimization-plan.md
-  /multi-agent:generate-task ["desc"] [figma-url]  Create a Jira Task matching team conventions (mining + active sprint + preview & approval)
-  /multi-agent:generate-bug ["desc"] [figma-url]   Create a Jira Bug matching team conventions (mining + active sprint + preview & approval)
+  /multi-agent:generate ["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
@@ -223,8 +222,8 @@ Examples:
   /multi-agent:review
 
   # Create a Jira issue that matches team conventions (preview + approval before create)
-  /multi-agent:generate-task "Profile screen empty state" https://figma.com/design/abc?node-id=1-2
-  /multi-agent:generate-bug "Login crash on iOS 17, see attached log"
+  /multi-agent:generate "Profile screen empty state" https://figma.com/design/abc?node-id=1-2
+  /multi-agent:generate "Login crash on iOS 17, see attached log"
 
 ------------------------------------------------------------
 
@@ -324,8 +323,7 @@ Post-Hoc & Side-Channel:
   /multi-agent:analysis ["analysis-name"]  Feature-spec analizi (Figma + Swagger + Confluence + repolar) → platform başına v3 doküman (23 bölüm Full / 7 bölüm Lite)
   /multi-agent:analysis-resolve [doc]      Analiz dokümanının Bölüm 20 açık sorularını kaynak etiketli adaylarla teker teker çözer
   /multi-agent:build-optimize iOS-only Xcode build performance wrapper → benchmark + analiz + recommend-first .build-benchmark/optimization-plan.md
-  /multi-agent:generate-task ["açıklama"] [figma-url]  Takım standartlarına uygun Jira Task oluştur (convention mining + aktif sprint + önizleme & onay)
-  /multi-agent:generate-bug ["açıklama"] [figma-url]   Takım standartlarına uygun Jira Bug oluştur (convention mining + aktif sprint + önizleme & onay)
+  /multi-agent:generate ["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)
@@ -436,8 +434,8 @@ Quality & Telemetry (advisory, default açık  -  prefs.global.* ile kapatılabi
   /multi-agent:review
 
   # Takım standartlarına uygun Jira issue oluştur (oluşturmadan önce önizleme + onay)
-  /multi-agent:generate-task "Profil ekranı empty state" https://figma.com/design/abc?node-id=1-2
-  /multi-agent:generate-bug "iOS 17'de login crash, log ekte"
+  /multi-agent:generate "Profil ekranı empty state" https://figma.com/design/abc?node-id=1-2
+  /multi-agent:generate "iOS 17'de login crash, log ekte"
 
 ------------------------------------------------------------
 

package/pipeline/commands/multi-agent/refs/cross-cli-contract.md

@@ -6,12 +6,12 @@
 
 ---
 
-## 1. Command Inventory (37 commands)
+## 1. Command Inventory (36 commands)
 
 ```
 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
 ```
@@ -19,7 +19,7 @@ scan, search, setup, stack, status, sync, test, update
 Categories:
 
 - **Interactive pickers** (single-purpose, not modes): `jira`, `issue`
-- **Issue generators** (one-shot, no worktree, hard approval gate before create): `generate-task`, `generate-bug`
+- **Issue generator** (one-shot, no worktree, asks type Task/Bug/Story, hard approval gate before create): `generate`
 - **Full 8-phase modes**: `autopilot`, `local`, `local-autopilot`
 - **Fast modes** (Init -> Dev(Opus) -> Commit -> Report): `dev`, `dev-autopilot`, `dev-local`, `dev-local-autopilot`
 - **Tail modes** (run the pipeline tail over already-done local work): `finish`
@@ -30,7 +30,7 @@ Categories:
 
 ### 1.1 Figma component subphase skills
 
-In addition to the 37 top-level multi-agent commands, the figma-to-component pipeline ships platform-specific skills that multi-agent dispatches from Phase 3 (see `refs/component-dispatch.md`). The structure is **platform-parallel iOS + Android with a shared common pool**:
+In addition to the 36 top-level multi-agent commands, the figma-to-component pipeline ships platform-specific skills that multi-agent dispatches from Phase 3 (see `refs/component-dispatch.md`). The structure is **platform-parallel iOS + Android with a shared common pool**:
 
 | Location | Skill count | Purpose |
 |---|---|---|
@@ -312,7 +312,7 @@ For clipboard ops, callers still gate with `if command -v pbpaste >/dev/null; th
 
 This contract is validated by:
 
-- `smoke-cross-cli-behavior.sh`  -  asserts all 37 commands behave identically, pulls from Section 2 (placeholder vocab), Section 5 (argument parsing), Section 6 (output formats); also regression-locks the 6-persona agent deployment
+- `smoke-cross-cli-behavior.sh`  -  asserts all 36 commands behave identically, pulls from Section 2 (placeholder vocab), Section 5 (argument parsing), Section 6 (output formats); also regression-locks the 6-persona agent deployment
 - `smoke-commands-skills-parity.sh` (50 assertions)  -  enforces colon-form command ↔ dash-form skill directory parity
 - `smoke-compliance-skills.sh` (45 assertions)  -  enforces store-compliance skill catalog + 4 consumer wiring
 - `smoke-personal-data.sh`  -  extended in 0.5.5 to treat deprecated placeholders (`{github-username}`, `{your-website}`, `{website-repo}`) as leaks; adds `mmerterden` to public-handle blocklist for generic docs

package/pipeline/commands/multi-agent/refs/generate-issue.md

@@ -1,21 +1,59 @@
-# Generate Issue  -  Shared Flow (generate-task / generate-bug)
+# Generate Issue  -  Shared Flow (generate)
 
-> **TLDR**  -  Shared 11-step flow for `/multi-agent:generate-task` and `/multi-agent:generate-bug`. Mines the target project's existing issues to learn team conventions, detects the active sprint, drafts a standards-compliant issue, asks the user about every genuinely unknown field, renders a full preview, and creates the Jira issue only after explicit approval. Creates exactly one Jira issue per run  -  no branches, no commits, no worktrees.
+> **TLDR**  -  Shared 12-step flow for `/multi-agent:generate`. Asks the issue type (Task / Bug / Story), mines the target project's existing same-type issues to learn team conventions, detects the active sprint, drafts a standards-compliant issue from a fixed standard template with auto-sizing sections, asks the user about every genuinely unknown field, renders a full preview, and creates the Jira issue only after explicit approval. Creates exactly one Jira issue per run  -  no branches, no commits, no worktrees.
 
-Consumed by `generate-task.md` and `generate-bug.md` via their profile blocks (`ISSUE_TYPE`, default description sections, JQL sample filter). This ref is never invoked directly.
+Consumed by `generate.md`. This ref is never invoked directly.
 
 ## Hard rules (must not regress)
 
-- **Approval gate is absolute.** Step [8/11] (full preview + explicit approval) runs on every invocation. There is no autopilot variant of these commands and no preference that skips the gate. `Cancel` means nothing was created.
-- **Never invent content.** Anything the user did not supply and mining could not derive stays an open question (step [7/11]) or an explicitly empty section  -  never fabricated repro steps, environments, or acceptance criteria.
+- **Approval gate is absolute.** Step [9/12] (full preview + explicit approval) runs on every invocation. There is no autopilot variant of this command and no preference that skips the gate. `Cancel` means nothing was created.
+- **Never invent content.** Anything the user did not supply and mining could not derive stays an open question (step [8/12]) or is omitted entirely  -  never fabricated repro steps, environments, acceptance criteria, or test pass/fail results.
+- **Standard template is the baseline.** The description structure comes from the type's standard template (see [7/12]), not from a mined heading set. Mining informs summary prefix, labels, components, priority norm, sprint placement, and test-scenario style  -  never replaces the standard section skeleton.
+- **Auto-sizing.** A conditional section renders only when its trigger is present. No empty placeholder headings  -  if there is nothing to put in a conditional section, it does not appear.
 - **Issue content language follows `prefs.global.outputLanguage`.** Summary and description are written in the user's output language (intentional exception to the "external payloads stay English" default  -  the issue is authored FOR the user's team). Code identifiers, file paths, and URLs stay verbatim. AskUserQuestion `question`/`description` also follow `outputLanguage`; `label`/`header` stay English.
 - **UTF-8 verbatim POST path** (same as `refs/channels/jira.md`): description body goes to a file, `jq -n --rawfile` builds the payload, `curl --data-binary @file` ships it. Never round-trip through `unicode_escape`/`latin-1`, never hand-roll a re-encoding helper. Jira wiki markup (`h3.` headings, `[text|url]` links), real newlines, no HTML entities.
 - **Humanizer pass** on the description body after composition, before the preview render.
-- **Read-only until approval.** Steps 1-8 perform only GET requests. The first write of any kind is the `POST /rest/api/2/issue` in step [9/11].
+- **Read-only until approval.** Steps 1-9 perform only GET requests. The first write of any kind is the `POST /rest/api/2/issue` in step [10/12].
+
+## Standard templates
+
+Each type has a standard section skeleton. `A` = always present. `C` = conditional (renders only when its trigger fires).
+
+| Type | Section | Presence | Trigger (for `C`) |
+|---|---|---|---|
+| **Task** | Detailed Description | A | |
+| | Scope | A | |
+| | Acceptance Criteria | A | |
+| | Test Scenarios | A | populated from mined test-scenario style; skeleton derived from AC when the project has no prior style |
+| | API Contract / Swagger | C | Swagger URL, OpenAPI/contract snippet, or explicit endpoint mention in input |
+| | Design Reference | C | Figma URL given |
+| | Screenshots | C | user pasted image(s) or a Figma screenshot was fetched |
+| | Notes | C | real content only |
+| **Bug** | Detailed Description | A | |
+| | Steps to Reproduce | A | |
+| | Expected Result | A | |
+| | Actual Result | A | |
+| | Environment | A | |
+| | Screenshots / Logs | C | user pasted image(s) or log/stack-trace text |
+| | Regression / Test Scenario | C | derivable from the repro; else omitted |
+| | API Contract | C | API-related bug + Swagger/contract/endpoint given |
+| | Design Reference | C | Figma URL given |
+| | Notes | C | real content only |
+| **Story** | User Story (`As a ... I want ... so that ...`) | A | |
+| | Detailed Description | A | |
+| | Scope | A | |
+| | Acceptance Criteria | A | |
+| | Test Scenarios | A | same as Task |
+| | API Contract / Swagger | C | Swagger URL / contract / endpoint mention |
+| | Design Reference | C | Figma URL given |
+| | Screenshots | C | user pasted image(s) or Figma screenshot fetched |
+| | Dependencies / Notes | C | real content only |
+
+Section headings render in `outputLanguage` (e.g. tr: "Detaylı Açıklama", "Kapsam", "Kabul Kriterleri", "Test Senaryoları", "Adımlar", "Beklenen Sonuç", "Gerçekleşen Sonuç", "Ortam", "Ekran Görüntüleri", "API Contract", "Design Reference", "Notlar").
 
 ## Flow
 
-### [1/11] Pick account (`_account-picker`)
+### [1/12] Pick account (`_account-picker`)
 
 ```bash
 ACCOUNTS=$(~/.claude/lib/account-resolver.sh --providers jira)
@@ -25,7 +63,7 @@ TOKEN=$(~/.claude/lib/credential-store.sh get "$ACCOUNT_JIRA_TOKEN_KEY")
 - Output: `ACCOUNT_JIRA_TOKEN_KEY`, `ACCOUNT_JIRA_HOST`.
 - Token missing/expired → Token Save Flow from `setup.md` inline; user skips → abort, nothing created.
 
-### [2/11] Resolve project key
+### [2/12] Resolve project key
 
 Fallback chain (same as `refs/issue-jira-triad.md` Create path):
 1. `figmaConfig.jira.projectKey` (per-project config, when running inside a configured repo)
@@ -39,44 +77,55 @@ curl -s -H "Authorization: Bearer $TOKEN" \
    AskUserQuestion (single-select) → cache the choice to `prefs.global.defaultJiraKey`.
 - Output: `PROJECT_KEY`.
 
-### [3/11] Parse input
+### [3/12] Pick issue type
+
+AskUserQuestion (single-select, `question` in `outputLanguage`, e.g. tr: "Ne oluşturmak istiyorsun?"): `Task` / `Bug` / `Story`. Never inferred silently.
+- Output: `ISSUE_TYPE`. Selects the standard template from the table above.
+- The chosen type drives the mining JQL in [5/12], the required-field discovery in [5/12], and the section skeleton in [7/12].
+
+### [4/12] Parse input
 
 - Any `figma.com` URL in `$ARGUMENTS` → `FIGMA_URL`. Node-id normalization: `-` → `:`. Branch URLs use `branchKey` as effective `fileKey` (see `rules/figma-pipeline.md` URL parsing).
+- Any OpenAPI/Swagger URL (path or query contains `swagger`, `openapi`, `/v2/api-docs`, `/v3/api-docs`, or a `.json`/`.yaml` spec) → `SWAGGER_URL`.
+- Pasted images (chat attachments) → `USER_SCREENSHOTS[]`. Pasted log/stack-trace text → kept with `FREE_TEXT` and later mapped to the Screenshots / Logs section (Bug) or Notes.
 - Everything else → `FREE_TEXT`.
-- Both empty → AskUserQuestion (free-text, in `outputLanguage`): "Describe the {task|bug} you want to open."
-- `FIGMA_URL` is always optional. Never ask for one; only use it when given.
+- All of `FREE_TEXT`/`FIGMA_URL`/`SWAGGER_URL`/`USER_SCREENSHOTS` empty → AskUserQuestion (free-text, in `outputLanguage`): "Describe the {type} you want to open."
+- `FIGMA_URL`, `SWAGGER_URL`, and screenshots are always optional. Never ask for them; only use them when given.
 
-### [4/11] Convention mining + field discovery + sprint detection (read-only)
+### [5/12] Convention mining + field discovery + sprint detection (read-only)
 
 Three GET groups. Run them before drafting anything.
 
-**4a. Sample recent same-type issues:**
+**5a. Sample recent same-type issues:**
 ```bash
 JQL="project = ${PROJECT_KEY} AND issuetype = ${ISSUE_TYPE} ORDER BY created DESC"
 curl -s -H "Authorization: Bearer $TOKEN" \
-  "https://$ACCOUNT_JIRA_HOST/rest/api/2/search?jql=$(printf '%s' "$JQL" | python3 -c 'import sys,urllib.parse; print(urllib.parse.quote(sys.stdin.read()))')&fields=summary,description,labels,components,priority,fixVersions&maxResults=30"
+  "https://$ACCOUNT_JIRA_HOST/rest/api/2/search?jql=$(printf '%s' "$JQL" | python3 -c 'import sys,urllib.parse; print(urllib.parse.quote(sys.stdin.read()))')&fields=summary,description,labels,components,priority,fixVersions,issuelinks&maxResults=30"
 ```
 Extract from the sample (thresholds are guidance, not hard gates):
-- **Summary prefix pattern**: leading `[...]` or `AREA:` token frequency. Appears in >= 40% of samples → adopt as suggested prefix; top 2-3 prefixes become AskUserQuestion options in step 7 when ambiguous.
-- **Description heading set**: lines matching `h[1-4]\.` or `*bold*` header style, frequency-ranked. A heading set shared by >= 50% of samples overrides the profile's default sections  -  the team template wins.
-- **Top labels / components**: top 5 each by frequency → option lists for step 7.
-- **Priority norm**: modal priority for this issuetype → pre-filled default, editable in preview.
-- **Epic usage rate**: share of sampled issues carrying an epic link → decides whether step 7 asks for an epic.
-
-**4b. Field discovery (createmeta):**
+- **Summary prefix pattern**: leading `[...]` or `AREA:` token frequency. Appears in >= 40% of samples → adopt as suggested prefix; top 2-3 prefixes become AskUserQuestion options in step 8 when ambiguous.
+- **Top labels / components**: top 5 each by frequency → option lists for step 8.
+- **Priority norm**: modal priority for this issuetype → pre-filled default, editable in preview. (Bug priorities often skew higher  -  respect the project's own norm.)
+- **Epic usage rate**: share of sampled issues carrying an epic link → decides whether step 8 asks for an epic.
+- **Test-scenario style** (Task / Story, and Bug regression): detect how the project expresses test scenarios in the sampled descriptions and links, in priority order:
+  1. Linked test issues  -  `issuelinks` pointing at a `Test`-family issuetype (Xray / Zephyr). If present, the standard Test Scenarios section references those linked tests rather than inlining steps.
+  2. A dedicated description heading (`Test Scenarios`, `Test Cases`, `QA`, `Senaryolar`, checklist blocks). If a style is shared by >= 40% of samples, reuse that exact format (heading name + bullet/checklist/table shape).
+  3. No prior style → inline a Test Scenarios skeleton derived from the Acceptance Criteria (one scenario per criterion, Given/When/Then or the project's dominant shape). Skeleton only  -  the user edits it in preview; pass/fail data is never fabricated.
+
+**5b. Field discovery (createmeta):**
 ```bash
 curl -s -H "Authorization: Bearer $TOKEN" \
   "https://$ACCOUNT_JIRA_HOST/rest/api/2/issue/createmeta?projectKeys=${PROJECT_KEY}&issuetypeNames=${ISSUE_TYPE}&expand=projects.issuetypes.fields"
 ```
 - 404 or empty `projects[]` (newer Jira DC deprecates the classic form) → fall back to the paged endpoint: `GET /rest/api/2/issue/createmeta/{PROJECT_KEY}/issuetypes` then `GET /rest/api/2/issue/createmeta/{PROJECT_KEY}/issuetypes/{issuetypeId}`.
-- Every field with `required: true` beyond project/issuetype/summary/description/reporter → step 7 question (options from `allowedValues` when present, free-text fallback).
+- Every field with `required: true` beyond project/issuetype/summary/description/reporter → step 8 question (options from `allowedValues` when present, free-text fallback).
 - Generic custom-field detection by `schema.custom` id  -  never assume field ids:
   - Sprint: `com.pyxis.greenhopper.jira:gh-sprint`
   - Epic Link: `com.pyxis.greenhopper.jira:gh-epic-link`
   - Team-like fields: case-insensitive name match on `Team`
-- 403 → warn "cannot read project field metadata", continue with profile defaults; required fields surface reactively via the 400 path in step 9.
+- 403 → warn "cannot read project field metadata", continue with template defaults; required fields surface reactively via the 400 path in step 10.
 
-**4c. Board + active sprint (Agile REST):**
+**5c. Board + active sprint (Agile REST):**
 ```bash
 curl -s -H "Authorization: Bearer $TOKEN" \
   "https://$ACCOUNT_JIRA_HOST/rest/agile/1.0/board?projectKeyOrId=${PROJECT_KEY}"
@@ -84,58 +133,72 @@ curl -s -H "Authorization: Bearer $TOKEN" \
   "https://$ACCOUNT_JIRA_HOST/rest/agile/1.0/board/${BOARD_ID}/sprint?state=active"
 ```
 - Multiple boards → AskUserQuestion (board name + type). One board → silent. Zero boards or Agile API 404 → the sprint option is silently omitted; the preview notes "backlog only (no board found)".
-- Active sprint found → remember `SPRINT_ID` + name for the step 7 placement choice. None → backlog only; if a `state=future` sprint exists, mention it in the preview as information.
+- Active sprint found → remember `SPRINT_ID` + name for the step 8 placement choice. None → backlog only; if a `state=future` sprint exists, mention it in the preview as information.
 
-### [5/11] Figma context (only when `FIGMA_URL` is set)
+### [6/12] External context (only for the sources actually provided)
 
+Each source is failure-isolated and never blocks issue creation.
+
+**6a. Figma** (only when `FIGMA_URL` is set):
 Follow the 3-tier chain from `rules/figma-pipeline.md`: Tier 1 MCP (`get_design_context` / `get_screenshot`, one re-auth retry) → Tier 2 REST (`keychainMapping.figma_pat`) → Tier 3 ask the user for a screenshot or proceed link-only.
 
 > This command is standalone (same class as `/multi-agent:analysis`), so Figma MCP use here is allowed  -  it is not a dev-phase violation under the "No MCP outside analysis phase" rule.
 
-- Output: frame name, node id, optional screenshot PNG in `/tmp/generate-issue-$$-figma.png` for the step 10 attachment opt-in.
-- Any tier failure degrades gracefully; Figma never blocks issue creation. Link-only is always acceptable.
+- Output: frame name, node id, optional screenshot PNG in `/tmp/generate-issue-$$-figma.png` for the step 11 attachment opt-in.
+- Any tier failure degrades gracefully; link-only is always acceptable.
+
+**6b. Swagger / API contract** (only when `SWAGGER_URL` is set or a contract snippet was pasted):
+- `SWAGGER_URL` set → fetch the spec, then extract **only the referenced endpoints**: if `FREE_TEXT` names specific paths / operationIds / tags, extract those; otherwise summarize the single tag or path group the user pointed at. Never crawl or dump the whole spec.
+```bash
+curl -s "$SWAGGER_URL" -o /tmp/generate-issue-$$-swagger.json  # add auth header only if the user supplied one
+```
+  Parse with `python3`/`jq` to pull, per referenced endpoint: HTTP method + path, a one-line summary, and the key request/response fields (names + types, not the full schema).
+- Only a pasted contract snippet → summarize that snippet (endpoints + key fields).
+- Output: an `API Contract` section body: `{METHOD} {path}` + summary + key request/response fields, plus `[Swagger|{SWAGGER_URL}]` when a URL was given.
+- Fetch failure / unreachable / no matching endpoint → degrade to link-only (or omit the section if nothing usable) and note it in the preview. Never block issue creation.
+
+**6c. Screenshots**: `USER_SCREENSHOTS[]` from step 4 are staged for the step 11 attachment opt-in; each attached image is referenced inline in the relevant section with Jira wiki `!filename|thumbnail!` markup.
 
-### [6/11] Compose draft
+### [7/12] Compose draft
 
-Write summary + description in `outputLanguage`:
+Write summary + description in `outputLanguage` from the type's **standard template** (baseline, not mined headings):
 - **Summary**: `{minedPrefix} {concise title}`, truncated to 255 chars.
-- **Description**: mined heading set from 4a (or the profile's default sections when mining found no dominant template), in Jira wiki markup (`h3.` headings).
-  - Task profile fills: Goal, Scope, Acceptance Criteria, Notes from `FREE_TEXT`.
-  - Bug profile fills: Steps to Reproduce, Expected Result, Actual Result, Environment, Notes from `FREE_TEXT`.
-  - Missing information stays an open question for step 7  -  never invented.
-  - `FIGMA_URL` set → add `h3. Design Reference` with `[Figma|{FIGMA_URL}]` + frame name + node id.
+- **Description**: render the type's standard section skeleton in Jira wiki markup (`h3.` headings), applying auto-sizing:
+  - **Always-present** sections are filled from `FREE_TEXT` (+ mining for Test Scenarios style). If an always-present section has no user content and cannot be derived, it stays an explicit open question for step 8  -  it is not fabricated.
+  - **Conditional** sections render only when their trigger fired (see the Standard templates table): Design Reference when `FIGMA_URL` set (`[Figma|{FIGMA_URL}]` + frame name + node id); API Contract when 6b produced a body; Screenshots when images were staged; Notes/Dependencies only with real content. Otherwise the heading is omitted entirely.
+  - Bug: logs / stack traces / device+OS mentions from `FREE_TEXT` map into Environment and Screenshots / Logs; anything underivable becomes a step-8 question.
 - Run the humanizer skill on the description body.
 - Write the final body to `/tmp/generate-issue-$$.txt` (UTF-8, real newlines) for the `--rawfile` POST.
 
-### [7/11] Clarifying questions (only genuinely unknown fields)
+### [8/12] Clarifying questions (only genuinely unknown fields)
 
 Batched AskUserQuestion(s), each with a "Skip / leave unset" option where Jira allows it:
 - **Component**: mined top components + "none"  -  only when the project uses components.
-- **Epic link**: only when 4a epic usage rate is high. Options from `project = {KEY} AND issuetype = Epic AND statusCategory != Done`.
+- **Epic link**: only when 5a epic usage rate is high. Options from `project = {KEY} AND issuetype = Epic AND statusCategory != Done`.
 - **Priority**: only when the mined norm is ambiguous; otherwise pre-fill the norm and let the preview edit change it.
 - **Labels**: mined top labels, multiSelect.
 - **Assignee**: "me / unassigned / someone else".
 - **Sprint placement**: "Active sprint: {name}" vs "Backlog"  -  only when an active sprint exists.
-- **Required custom fields** from 4b not yet resolved (allowedValues as options).
-- **Bug profile**: Steps to Reproduce or Environment underivable from `FREE_TEXT` → ask here.
+- **Required custom fields** from 5b not yet resolved (allowedValues as options).
+- **Always-present sections still empty**: Bug Steps to Reproduce / Environment, or a Task/Story with no derivable Scope / Acceptance Criteria → ask here.
 
-Rule: never ask about anything already answerable from mining or the input. Regardless of how complete the draft looks, step 8 always runs.
+Rule: never ask about anything already answerable from mining or the input. Regardless of how complete the draft looks, step 9 always runs.
 
-### [8/11] Full preview + approval gate (never skipped)
+### [9/12] Full preview + approval gate (never skipped)
 
-Render the complete issue in chat: project, issuetype, summary, the full description body, priority, labels, components, epic, assignee, sprint/backlog placement, attachment plan (Figma screenshot upload  -  default off, opt-in).
+Render the complete issue in chat: project, issuetype, summary, the full description body, priority, labels, components, epic, assignee, sprint/backlog placement, attachment plan (Figma + user screenshots upload  -  default off, opt-in).
 
 Then AskUserQuestion (`question` in `outputLanguage`, e.g. tr: "Bu sekilde olusturuyorum, onayliyor musun?"):
 
 | Option | Behavior |
 |---|---|
-| `Approve` | Proceed to step 9 |
+| `Approve` | Proceed to step 10 |
 | `Edit` | Free-text "what should change?" → apply → re-render the FULL preview → re-ask. Loop, no iteration cap |
 | `Cancel` | Stop. Nothing was created; say so explicitly |
 
 This gate has no bypass. No flag, mode, or preference suppresses it.
 
-### [9/11] Create
+### [10/12] Create
 
 ```bash
 jq -n --rawfile desc /tmp/generate-issue-$$.txt \
@@ -148,13 +211,13 @@ curl -sS -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application
   "https://$ACCOUNT_JIRA_HOST/rest/api/2/issue"
 ```
 - Parse `key` from the response → `NEW_KEY`.
-- 400 with field errors → show Jira's per-field error verbatim, return to step 7 for exactly those fields, then re-run step 8 (full preview again).
+- 400 with field errors → show Jira's per-field error verbatim, return to step 8 for exactly those fields, then re-run step 9 (full preview again).
 
-### [10/11] Post-create steps
+### [11/12] Post-create steps
 
 Each step is failure-isolated: on error, warn + continue  -  the issue already exists.
 
-1. **Sprint** (when chosen in step 7/8):
+1. **Sprint** (when chosen in step 8/9):
 ```bash
 jq -n --arg key "$NEW_KEY" '{issues: [$key]}' > /tmp/generate-issue-$$-sprint.json
 curl -sS -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
@@ -168,30 +231,37 @@ curl -sS -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application
   -d '{"object":{"url":"'"$FIGMA_URL"'","title":"Figma design"}}' \
   "https://$ACCOUNT_JIRA_HOST/rest/api/2/issue/${NEW_KEY}/remotelink"
 ```
-3. **Screenshot attachment** (only when opted in during preview):
+3. **Swagger remote link** (when `SWAGGER_URL` set):
+```bash
+curl -sS -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
+  -d '{"object":{"url":"'"$SWAGGER_URL"'","title":"API contract"}}' \
+  "https://$ACCOUNT_JIRA_HOST/rest/api/2/issue/${NEW_KEY}/remotelink"
+```
+4. **Screenshot / image attachments** (only when opted in during preview  -  Figma render and/or user-pasted images):
 ```bash
 curl -sS -X POST -H "Authorization: Bearer $TOKEN" -H "X-Atlassian-Token: no-check" \
   -F "file=@/tmp/generate-issue-$$-figma.png" \
   "https://$ACCOUNT_JIRA_HOST/rest/api/2/issue/${NEW_KEY}/attachments"
 ```
 
-### [11/11] Report
+### [12/12] Report
 
 ```
 Created {NEW_KEY}: https://{ACCOUNT_JIRA_HOST}/browse/{NEW_KEY}
 ```
-Plus one line per post-create step that ran (sprint placement, remote link, attachment) and any that were skipped with reason.
+Plus one line per post-create step that ran (sprint placement, remote links, attachments) and any that were skipped with reason.
 
 ## Error paths
 
 | Condition | Behavior |
 |---|---|
 | Token missing/expired (401) | Token Save Flow from `setup.md` inline; user skips → abort with message, nothing created |
-| Search 403 / createmeta denied | Warn "cannot read project conventions/fields"; continue with profile-default template; required fields asked reactively on 400 |
-| Zero sampled issues (new project) | Skip mining, use profile defaults, note in preview "no prior issues to learn from" |
+| Search 403 / createmeta denied | Warn "cannot read project conventions/fields"; continue with standard-template defaults; required fields asked reactively on 400 |
+| Zero sampled issues (new project) | Skip mining, use standard template + AC-derived test-scenario skeleton, note in preview "no prior issues to learn from" |
 | Agile API 404 / no boards | Omit sprint choice, backlog implied, say so in preview |
 | No active sprint | Offer backlog only; mention the next `state=future` sprint when one exists |
 | Figma Tier 1 fails | Tier 2; Tier 2 fails → Tier 3 (ask screenshot or link-only). Never block issue creation on Figma |
-| Create 400 (field errors) | Show per-field errors, loop back to step 7 for those fields, re-preview |
+| Swagger fetch fails / unreachable | Degrade to link-only, or omit the API Contract section if nothing usable; note in preview. Never block issue creation |
+| Create 400 (field errors) | Show per-field errors, loop back to step 8 for those fields, re-preview |
 | Create 5xx / network | Show the error, offer one retry, then abort  -  keep `/tmp/generate-issue-$$.txt` and print its path so the draft survives |
 | Post-create step failure | Warn + continue (issue exists); print a manual-fix hint |

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

@@ -58,7 +58,7 @@ Run every step automatically:
 Step 0: FIGMA_SYNC  SKIP (deprecated  -  feedback_figma_source_deprecated)
 Step 1: PLATFORM    Detect macOS / Linux / Windows (Git Bash / WSL); export PLATFORM env
 Step 1.5: DETECT    Compare timestamps, find stale targets
-Step 2: COPILOT     Claude Code -> Copilot CLI (instructions + 37 sub-command skills)
+Step 2: COPILOT     Claude Code -> Copilot CLI (instructions + 36 sub-command skills)
 Step 3: REPO        Claude Code -> pipeline repo (genericized, personal data scrub, bash -n on all sh)
 Step 3c: PLUGINS    pipeline shared/external -> multi-agent-plugins marketplace (rebuild knowledge/,
                      bump changed plugins' patch version, commit + push the plugins repo)
@@ -169,7 +169,7 @@ If nothing is stale → report "All targets up to date" and stop.
 
 ## Stack-Plugin Sync (Step 3c)
 
-Stack skills are distributed as versioned plugins in the `{owner}/multi-agent-plugins` marketplace. The pipeline's `pipeline/skills/shared/external/` is the **single authoring source**; the marketplace is a derived, versioned publish artifact. This step rebuilds it and publishes only when something changed.
+Stack skills are distributed as versioned plugins in the `mmerterden/multi-agent-plugins` marketplace. The pipeline's `pipeline/skills/shared/external/` is the **single authoring source**; the marketplace is a derived, versioned publish artifact. This step rebuilds it and publishes only when something changed.
 
 **Source of truth:** author/vendor knowledge skills in `pipeline/skills/shared/external/` (the pipeline's own phases also consume them). The plugins' authored lifecycle skills (`index` / `reference` / `workflow` / `tools`) live in the plugins repo and are never touched by sync.
 
@@ -177,7 +177,7 @@ Stack skills are distributed as versioned plugins in the `{owner}/multi-agent-pl
 
 ```bash
 PLUGINS_REPO="$HOME/multi-agent-plugins"
-[ ! -d "$PLUGINS_REPO/.git" ] && gh repo clone {owner}/multi-agent-plugins "$PLUGINS_REPO"
+[ ! -d "$PLUGINS_REPO/.git" ] && gh repo clone mmerterden/multi-agent-plugins "$PLUGINS_REPO"
 cd "$PLUGINS_REPO" && git pull origin main
 
 # 1. Preview what would change (routing + version bumps), no writes:
@@ -197,10 +197,10 @@ node "$HOME/multi-agent-pipeline/pipeline/scripts/build-stack-plugins.mjs"
 ```bash
 cd "$PLUGINS_REPO"
 if ! git diff --quiet; then
-  git config user.name "$(git config user.name)"; git config user.email "$(git config user.email)"
+  git config user.name "Mert Erden"; git config user.email "mmerterden@gmail.com"
   git add -A
   git commit -m "chore: rebuild stack plugins from pipeline shared/external"
-  gh auth switch --user {owner} 2>/dev/null || true
+  gh auth switch --user mmerterden 2>/dev/null || true
   git push origin main
 fi
 ```
@@ -277,12 +277,12 @@ This runs on the Claude <-> Copilot axis — the two CLIs the pipeline supports
 |-------------|-------------|
 | `~/.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/commands/multi-agent.md

@@ -77,8 +77,7 @@ Lib scripts (`~/.claude/lib/`):
 | `analysis ["<feature>"]` | Standalone feature-spec analizi: Figma / Swagger / Confluence / Jira / repo girdileri sabit 7-bölümlük şablona dökülür, humanizer'dan geçer, Local/Confluence/Jira hedef(ler)ine post edilir. Worktree veya commit yok. Dev'e zincirleme yok. |
 | `build-optimize` | iOS-only Xcode build performance wrapper. Vendored `xcode-build-orchestrator`'a dispatch eder; benchmark + compilation / project / SPM analyzer'lar + recommend-first plan `.build-benchmark/optimization-plan.md`. Non-iOS stack'lerde fail-fast. |
 | `channels [PR-url\|#N\|Jira-url\|Jira-id] [--channels pr,jira,confluence,wiki] [--content normal,test,auto-diff,note] [--message "..."]` | Post task report to multi-select channels (PR description, Jira comment, Confluence page, Wiki pages) with multi-select content sources. Humanizer pass per-channel. Bitbucket PR updates use reviewer-preserving PUT. Phase 7 delegates to this command; also invocable post-hoc for fixes made outside the pipeline. No worktree. |
-| `generate-task ["desc"] [figma-url]` | Create a standards-compliant Jira **Task**: mines the project's recent Tasks for conventions (summary format, template, labels, priority), detects the active sprint, asks about unknown fields, then full draft preview + explicit approval before create. No worktree, no commits. |
-| `generate-bug ["desc"] [figma-url]` | Create a standards-compliant Jira **Bug**: same convention mining + active-sprint detection; free-text logs/devices map to Steps to Reproduce / Environment; full draft preview + explicit approval before create. No worktree, no commits. |
+| `generate ["desc"] [figma-url] [swagger-url]` | Create a standards-compliant Jira issue: asks the type (**Task** / **Bug** / **Story**), mines the project's recent same-type issues for conventions (summary format, labels, priority, test-scenario style), detects the active sprint, drafts from a standard template with auto-sizing sections (Design Reference / API Contract / Screenshots appear only when their source is given), asks about unknown fields, then full draft preview + explicit approval before create. No worktree, no commits. |
 | `test` or `test [args]` | UI Bug Hunter  -  screenshot + tap + analyze on booted simulator via MCP (read `$HOME/.claude/commands/sim-test.md`). `/multi-agent:test` also resolves here via the `commands/multi-agent/test.md` delegate. |
 | `manual-test [#id]` | Phase 5 standalone Manual Test  -  checks out the task branch, prints Xcode / SourceTree hints, waits for user verdict (`ok` / `fix: ...`). |
 | `stack [ios\|android\|backend\|mobile\|all]` | Swap skills for next conversation. No arg = show current stack. |
@@ -118,8 +117,7 @@ This command uses lazy loading for token efficiency. Read the relevant sub-file
 | `local-autopilot` | `$HOME/.claude/commands/multi-agent/local-autopilot.md` |
 | `dev-local` | `$HOME/.claude/commands/multi-agent/dev-local.md` |
 | `dev-local-autopilot` | `$HOME/.claude/commands/multi-agent/dev-local-autopilot.md` |
-| `generate-task` | `$HOME/.claude/commands/multi-agent/generate-task.md` (loads `refs/generate-issue.md`) |
-| `generate-bug` | `$HOME/.claude/commands/multi-agent/generate-bug.md` (loads `refs/generate-issue.md`) |
+| `generate` | `$HOME/.claude/commands/multi-agent/generate.md` (loads `refs/generate-issue.md`) |
 | `stack` | `$HOME/.claude/commands/multi-agent/stack.md` |
 | `language` | Handled inline  -  set/show prompt language in preferences |
 | SwiftUI component task (iOS) | `$HOME/.claude/commands/multi-agent/refs/swiftui-guide.md` |

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-07T13:28:32.523Z",
+  "skillCount": 223,
   "entries": [
     {
       "name": "accessibility-compliance-accessibility-audit",
@@ -1156,22 +1156,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",

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/skills-index.md

@@ -3,7 +3,7 @@
 > 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.
+**223 skills** across 5 groups.
 
 | Group | Name | Platform | Description |
 |-------|------|----------|-------------|
@@ -135,8 +135,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. |

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.

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

@@ -1,33 +0,0 @@
----
-description: "Create a standards-compliant Jira Task: mines project conventions, drafts in outputLanguage, full preview + explicit approval before create."
-argument-hint: "[\"<free-text description>\"] [figma-url]  -  both optional, asked interactively when missing"
----
-
-# multi-agent generate-task  -  Standards-Compliant Jira Task Creator
-
-**Input**: $ARGUMENTS
-
-Creates exactly one Jira **Task**, 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 Tasks (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` | `Task` |
-| Default description sections | Goal, Scope, Acceptance Criteria, Design Reference (only when a Figma URL is given), Notes |
-| JQL sample filter | `issuetype = Task` |
-| Priority default | mined norm from sampled Tasks |
-
-## 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:
-
-- Ask the user (AskUserQuestion) about every genuinely unknown field  -  component, epic, priority, labels, assignee, sprint vs backlog, required custom fields.
-- Step [8/11] full preview + approval gate always runs. `Approve` / `Edit` (loop) / `Cancel`. No bypass exists.
-- Never invent Goal, Scope, or Acceptance Criteria content the user did not supply.
-
-## Error paths
-
-See `refs/generate-issue.md` Error paths. No command-specific additions.

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

@@ -1,39 +0,0 @@
----
-name: multi-agent-generate-bug
-language: en
-description: "Create a standards-compliant Jira Bug: mines project conventions, drafts in outputLanguage, full preview + explicit approval before create."
-user-invocable: true
-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. Profile: `ISSUE_TYPE=Bug`; default description sections: Steps to Reproduce, Expected Result, Actual Result, Environment, Design Reference (only when a Figma URL is given), Notes.
-
-> **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.
-
-## 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. **Parse input**  -  `figma.com` URL in `$ARGUMENTS` → `FIGMA_URL` (node-id `-` → `:`); the rest is `FREE_TEXT`. Logs, stack traces, and device/OS mentions map into Steps to Reproduce / Environment. Both empty → ask for a description. Figma URL is always optional.
-4. **Convention mining + field discovery + sprint** (read-only GETs):
-   - Sample: `GET /rest/api/2/search?jql=project={KEY} AND issuetype=Bug ORDER BY created DESC&fields=summary,description,labels,components,priority,fixVersions&maxResults=30`. Extract summary prefix pattern (>= 40% threshold), dominant description heading set (>= 50% overrides the profile sections), top-5 labels/components, modal priority, epic usage rate.
-   - `GET /rest/api/2/issue/createmeta?projectKeys={KEY}&issuetypeNames=Bug&expand=projects.issuetypes.fields` (404/empty → paged DC endpoint fallback). Required custom fields → step 6 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.
-5. **Figma context** (only when `FIGMA_URL` set)  -  3-tier chain (MCP → REST figma_pat → user screenshot); standalone command, MCP allowed here. Figma failures never block issue creation.
-6. **Draft + clarifying questions**  -  compose summary (`{minedPrefix} {title}`, 255 trunc) + description (mined heading set or profile sections, Jira wiki markup `h3.`, 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, missing Steps to Reproduce / Environment. Never invent repro steps or environments the user did not supply.
-7. **Full preview + approval gate (never skipped)**  -  render the complete issue (all fields + full description + attachment plan, screenshot default off). Ask: `Approve` / `Edit` (apply → re-render → re-ask, loop) / `Cancel` (nothing created). No flag or mode bypasses this gate.
-8. **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.
-9. **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`; screenshot opt-in → `POST /rest/api/2/issue/{KEY}/attachments` with `X-Atlassian-Token: no-check`.
-10. **Report**  -  `Created {KEY}: https://{host}/browse/{KEY}` + which post-steps ran.
-
-## Error paths
-
-401 token → Save Flow or abort (nothing created); mining/createmeta 403 → profile defaults + reactive 400 handling; zero sampled issues → skip mining, note in preview; no board/active sprint → backlog implied, say so; create 5xx → one retry then abort keeping the draft file; post-create failure → warn + continue.

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

@@ -1,39 +0,0 @@
----
-name: multi-agent-generate-task
-language: en
-description: "Create a standards-compliant Jira Task: mines project conventions, drafts in outputLanguage, full preview + explicit approval before create."
-user-invocable: true
-argument-hint: "[\"<free-text description>\"] [figma-url]  -  both optional, asked interactively when missing"
----
-
-# multi-agent generate-task  -  Standards-Compliant Jira Task Creator
-
-**Input**: $ARGUMENTS
-
-Creates exactly one Jira **Task**, and only after explicit approval. No branches, no commits, no worktrees. Profile: `ISSUE_TYPE=Task`; default description sections: Goal, Scope, Acceptance Criteria, Design Reference (only when a Figma URL is given), Notes.
-
-> **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.
-
-## 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. **Parse input**  -  `figma.com` URL in `$ARGUMENTS` → `FIGMA_URL` (node-id `-` → `:`); the rest is `FREE_TEXT`. Both empty → ask for a description. Figma URL is always optional.
-4. **Convention mining + field discovery + sprint** (read-only GETs):
-   - Sample: `GET /rest/api/2/search?jql=project={KEY} AND issuetype=Task ORDER BY created DESC&fields=summary,description,labels,components,priority,fixVersions&maxResults=30`. Extract summary prefix pattern (>= 40% threshold), dominant description heading set (>= 50% overrides the profile sections), top-5 labels/components, modal priority, epic usage rate.
-   - `GET /rest/api/2/issue/createmeta?projectKeys={KEY}&issuetypeNames=Task&expand=projects.issuetypes.fields` (404/empty → paged DC endpoint fallback). Required custom fields → step 6 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.
-5. **Figma context** (only when `FIGMA_URL` set)  -  3-tier chain (MCP → REST figma_pat → user screenshot); standalone command, MCP allowed here. Figma failures never block issue creation.
-6. **Draft + clarifying questions**  -  compose summary (`{minedPrefix} {title}`, 255 trunc) + description (mined heading set or profile sections, Jira wiki markup `h3.`, 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. Never invent content the user did not supply.
-7. **Full preview + approval gate (never skipped)**  -  render the complete issue (all fields + full description + attachment plan, screenshot default off). Ask: `Approve` / `Edit` (apply → re-render → re-ask, loop) / `Cancel` (nothing created). No flag or mode bypasses this gate.
-8. **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.
-9. **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`; screenshot opt-in → `POST /rest/api/2/issue/{KEY}/attachments` with `X-Atlassian-Token: no-check`.
-10. **Report**  -  `Created {KEY}: https://{host}/browse/{KEY}` + which post-steps ran.
-
-## Error paths
-
-401 token → Save Flow or abort (nothing created); mining/createmeta 403 → profile defaults + reactive 400 handling; zero sampled issues → skip mining, note in preview; no board/active sprint → backlog implied, say so; create 5xx → one retry then abort keeping the draft file; post-create failure → warn + continue.