@mmerterden/multi-agent-pipeline 10.12.0 → 11.1.0

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.