@mmerterden/multi-agent-pipeline 8.6.1 → 10.0.6

package/pipeline/skills/figma-common/figma-review/SKILL.md

@@ -1,4 +1,9 @@
-# /figma-review — Interactive Code Review for Figma Components
+---
+name: figma-review
+description: Guided review session for a Figma component implementation. Resolves the component, finds or creates the GitHub issue, shows relevant code, and walks the reviewer through approve/bug/inspect actions.
+---
+
+# /figma-review  -  Interactive Code Review for Figma Components
 
 ## Purpose
 
@@ -12,7 +17,7 @@ Guided review session for a Figma component implementation. Resolves the compone
 
 ```
 /figma-review ModalsTitle
-/figma-review CheckinBoardingPassFlightInfo
+/figma-review MyComponent
 /figma-review 175
 ```
 
@@ -29,7 +34,7 @@ PROJECT_ID      = {github.projectV2Id}
 
 ---
 
-## STEP 0 — Resolve Component
+## STEP 0  -  Resolve Component
 
 ### Determine input type
 
@@ -67,7 +72,7 @@ If no `.swift` file found → HALT: "Component `{ComponentName}` not found in co
 
 ### Find GitHub issue (if input was ComponentName)
 
-**Primary: node-id search (deterministic)** — if the registry has an entry for this component, look up its nodeId and search for issues whose body references that exact string:
+**Primary: node-id search (deterministic)**  -  if the registry has an entry for this component, look up its nodeId and search for issues whose body references that exact string:
 
 ```bash
 # Resolve ComponentName → nodeId via registry
@@ -88,7 +93,7 @@ if [ -n "$NODE_ID" ]; then
 fi
 ```
 
-**Fallback: fuzzy name search** — only if node-id lookup returned nothing (component not in registry, or registry not cloned):
+**Fallback: fuzzy name search**  -  only if node-id lookup returned nothing (component not in registry, or registry not cloned):
 
 ```bash
 gh issue list --repo ${GH_REPO} --state open --label component --search "{ComponentName}" --json number,title,body,labels,state
@@ -105,8 +110,8 @@ No open issue found for {ComponentName}.
 2. Continue without issue
 ```
 
-- If "1": run the same flow as `/figma-issue open` — registry lookup, create issue, add to board. Then continue.
-- If "2": continue review without issue tracking (no labels, no sub-issues — just code inspection).
+- If "1": run the same flow as `/figma-issue open`  -  registry lookup, create issue, add to board. Then continue.
+- If "2": continue review without issue tracking (no labels, no sub-issues  -  just code inspection).
 
 ### Extract issue metadata
 
@@ -118,9 +123,9 @@ From the issue body:
 
 ---
 
-## STEP 1 — Show Review Context
+## STEP 1  -  Show Review Context
 
-## STEP 2 — Review Menu
+## STEP 2  -  Review Menu
 
 Print the full review context AND the menu **together in a single output block**, then STOP. Wait for user's response.
 
@@ -128,7 +133,7 @@ Print the full review context AND the menu **together in a single output block**
 ═══════════════════════════════════════════════
   REVIEW: {ComponentName}
 ═══════════════════════════════════════════════
-  Issue:    #{N} — {title}
+  Issue:    #{N}  -  {title}
   Jira:     {JIRA_KEY or "none"}
   Phase:    {current phase from labels}
   Review:   {X/4 from label or "not started"}
@@ -155,7 +160,7 @@ What would you like to do?
 6. Done (exit review)
 ```
 
-### Action: `1` — Open in Xcode
+### Action: `1`  -  Open in Xcode
 
 Find the component's Swift file using Glob, then open it:
 
@@ -165,7 +170,7 @@ open -a Xcode "<resolved_path>"
 
 Return to menu.
 
-### Action: `2` — Open in Xcode + Figma
+### Action: `2`  -  Open in Xcode + Figma
 
 1. Open the Swift file in Xcode (same as Action 1):
 ```bash
@@ -187,7 +192,7 @@ fi
 
 Return to menu.
 
-### Action: `3` — Approve
+### Action: `3`  -  Approve
 
 1. Get current reviewer's GitHub username:
 ```bash
@@ -223,7 +228,7 @@ Print: "Approved. Review status: {APPROVED}/4"
 
 Return to menu.
 
-### Action: `4` — Open bug
+### Action: `4`  -  Open bug
 
 Print and STOP:
 
@@ -233,13 +238,13 @@ Describe the bug:
 
 Wait for user's response. Capture as `BUG_DESCRIPTION`.
 
-Then ask via **AskUserQuestion** (discrete options only — no free text):
+Then ask via **AskUserQuestion** (discrete options only  -  no free text):
 
 ```
 Question: "Bug severity?"
 Options:
-  - label: "Minor"  description: "Cosmetic, non-blocking — label bug-minor"
-  - label: "Major"  description: "Functional issue, must fix — label bug-major"
+  - label: "Minor"  description: "Cosmetic, non-blocking  -  label bug-minor"
+  - label: "Major"  description: "Functional issue, must fix  -  label bug-major"
 ```
 
 The answer drives a label, not a free-text comparison. Map:
@@ -308,7 +313,7 @@ Print: "Bug #M created and linked to #N."
 
 Return to menu.
 
-### Action: `5` — Status
+### Action: `5`  -  Status
 
 Show detailed review progress:
 
@@ -316,17 +321,17 @@ Show detailed review progress:
 Review Status: {ComponentName} (#N)
 
 Approvals: {COUNT}/4
-  ✅ @reviewer1 — approved 2026-03-22
-  ✅ @reviewer2 — approved 2026-03-22
+  ✅ @reviewer1  -  approved 2026-03-22
+  ✅ @reviewer2  -  approved 2026-03-22
   ⬜ @reviewer3
   ⬜ @reviewer4
 
 Open Bugs: {COUNT}
-  🔴 #108 — dark mode text color wrong (Major)
-  🟡 #109 — RTL padding missing (Minor)
+  🔴 #108  -  dark mode text color wrong (Major)
+  🟡 #109  -  RTL padding missing (Minor)
 
 Closed Bugs: {COUNT}
-  ✅ #110 — wrong font token (fixed)
+  ✅ #110  -  wrong font token (fixed)
 ```
 
 Fetch sub-issues:
@@ -336,7 +341,7 @@ gh api graphql -f query='{ repository(owner: "{github.org}", name: "{project.slu
 
 Return to menu.
 
-### Action: `6` — Done
+### Action: `6`  -  Done
 
 Print: "Review session ended." Exit.
 
@@ -351,7 +356,7 @@ When STEP 1 detects no `### Review` section in the issue body:
 gh api user --jq '.login'
 ```
 
-2. Add them as the first reviewer, **unchecked** (pending — they must use Action 3 to formally approve):
+2. Add them as the first reviewer, **unchecked** (pending  -  they must use Action 3 to formally approve):
 
 ```markdown
 ### Review
@@ -372,7 +377,7 @@ You've been added as reviewer (@{current_username}). Review requires 4 approvals
 Other reviewers can be added via the GitHub issue or by running /figma-review.
 ```
 
-6. Continue to STEP 2 (review menu) — no need to stop again.
+6. Continue to STEP 2 (review menu)  -  no need to stop again.
 
 ---
 

package/pipeline/skills/figma-common/figma-setup/SKILL.md

@@ -8,7 +8,7 @@ status: wip-v5
 sourced-from: upstream/figma-setup
 ---
 
-# /figma-setup — Environment Setup
+# /figma-setup  -  Environment Setup
 
 One-time environment setup for the Figma-to-SwiftUI workflow. Run before your first `/figma` invocation, or when `/figma` reports missing prerequisites.
 
@@ -147,7 +147,7 @@ else:
 - If output starts with `figu_` → valid OAuth token
 - If `EXTRACT_FAILED` → Claude Code has no figma-remote credentials
 
-#### 3b-c. If extraction succeeded — save to keychain
+#### 3b-c. If extraction succeeded  -  save to keychain
 
 ```bash
 TOKEN="<extracted_token>" && "$HOME/.claude/lib/credential-store.sh" set \1 \"\2\" >/dev/null 2>&1 && echo "MCP_TOKEN_STORED" || echo "MCP_TOKEN_STORE_FAILED"
@@ -189,7 +189,7 @@ Record as `skipped`. Scripts will fall back to extracting at runtime (slower but
 "$HOME/.claude/lib/credential-store.sh" get \1 >/dev/null 2>&1 && echo "TOKEN_EXISTS" || echo "TOKEN_MISSING"
 ```
 
-#### 4b. If TOKEN_EXISTS — verify it works
+#### 4b. If TOKEN_EXISTS  -  verify it works
 
 ```bash
 curl -s -o /dev/null -w "%{http_code}" -H "X-Figma-Token: $("$HOME/.claude/lib/credential-store.sh" get \1 2>/dev/null)" "https://api.figma.com/v1/me"
@@ -199,7 +199,7 @@ curl -s -o /dev/null -w "%{http_code}" -H "X-Figma-Token: $("$HOME/.claude/lib/c
 - `403` → token expired or revoked, proceed to 4c
 - Other → network issue, retry
 
-#### 4c. If TOKEN_MISSING or expired — secure setup
+#### 4c. If TOKEN_MISSING or expired  -  secure setup
 
 Tell the user:
 
@@ -260,7 +260,7 @@ npx @figma/code-connect@latest --version 2>/dev/null
 > - Download from https://nodejs.org/ (LTS recommended)
 > - Or: `brew install node`
 >
-> Code Connect uses `npx` — no global install needed.
+> Code Connect uses `npx`  -  no global install needed.
 
 Ask: "Confirm when Node.js is installed, or say 'skip'."
 
@@ -333,7 +333,7 @@ If `INSUFFICIENT_SCOPES` error mentioning `project`:
 "$HOME/.claude/lib/credential-store.sh" get \1 >/dev/null 2>&1 && echo "TOKEN_EXISTS" || echo "TOKEN_MISSING"
 ```
 
-#### 9a. If TOKEN_EXISTS — verify
+#### 9a. If TOKEN_EXISTS  -  verify
 
 ```bash
 curl -s -o /dev/null -w "%{http_code}" "{jira.baseUrl}/rest/api/2/myself" \
@@ -379,7 +379,7 @@ Same flow as CHECK 9 but for Confluence:
 - Verify: `curl -s -o /dev/null -w "%{http_code}" "{confluence.baseUrl}/rest/api/content?limit=1" -H "Authorization: Bearer ..."`
 - If missing: guide user to create PAT at `{confluence.baseUrl}`
 - Clipboard flow, same as Jira
-- VPN required — if not connected, record as `skipped (no VPN)`
+- VPN required  -  if not connected, record as `skipped (no VPN)`
 
 ---
 
@@ -410,19 +410,19 @@ After all checks complete, create `{repos.packagesContainer}/{repos.artifactsRep
 
 ## Token Management
 
-### `retrieve-token` — Retrieve Remote MCP OAuth Token
+### `retrieve-token`  -  Retrieve Remote MCP OAuth Token
 
 Looks up the Figma remote MCP OAuth token (`figu_` prefix) and prints it for the user.
 
 **Resolution order:**
 
-1. **Keychain `FIGMA_MCP_TOKEN`** — the dedicated keychain entry saved by `save-token` or CHECK 3b.
+1. **Keychain `FIGMA_MCP_TOKEN`**  -  the dedicated keychain entry saved by `save-token` or CHECK 3b.
 
 ```bash
 "$HOME/.claude/lib/credential-store.sh" get \1 2>/dev/null
 ```
 
-2. **Claude Code credentials** — if not in dedicated keychain, extract from Claude Code's credential store.
+2. **Claude Code credentials**  -  if not in dedicated keychain, extract from Claude Code's credential store.
 
 ```bash
 python3 -c "
@@ -444,7 +444,7 @@ print(match.group(1) if match else 'NOT_FOUND')
 
 ---
 
-### `save-token` — Save Remote MCP OAuth Token to Keychain
+### `save-token`  -  Save Remote MCP OAuth Token to Keychain
 
 Saves a provided token (or extracts from Claude Code credentials) to the dedicated `FIGMA_MCP_TOKEN` keychain entry so scripts can use it.
 

package/pipeline/skills/figma-common/figma-setup/scripts/fetch-mcp-token.py

@@ -4,11 +4,11 @@ Figma Remote MCP Token Fetcher
 
 Retrieves or refreshes a Figma MCP OAuth token. Three modes:
 
-MODE 1 — Extract (default):
+MODE 1  -  Extract (default):
     Reads existing token from Keychain or Claude Code credentials.
     python3 fetch-mcp-token.py
 
-MODE 2 — OAuth (--oauth):
+MODE 2  -  OAuth (--oauth):
     Runs full OAuth flow. Opens browser for Figma consent, runs local
     callback server, exchanges code for token. Works from ANY terminal.
     python3 fetch-mcp-token.py --oauth --client-id X --client-secret Y --save-keychain
@@ -354,7 +354,7 @@ def run_oauth_flow(client_id, client_secret, port):
         return None
 
     if OAuthCallbackHandler.auth_state != state:
-        log("State mismatch — possible CSRF.")
+        log("State mismatch  -  possible CSRF.")
         return None
 
     auth_code = OAuthCallbackHandler.auth_code
@@ -530,7 +530,7 @@ def main():
             if not args.quiet:
                 log("Token is VALID.")
         else:
-            # Token invalid — try auto-refresh before giving up
+            # Token invalid  -  try auto-refresh before giving up
             if not args.quiet:
                 log("Token is INVALID or EXPIRED. Attempting auto-refresh...")
             refresh_tok = get_refresh_token_from_keychain()
@@ -564,7 +564,7 @@ def main():
                                 log(f"Updated Keychain '{KEYCHAIN_SERVICE}'.")
                     else:
                         if not args.quiet:
-                            log("Refresh failed — token or credentials expired.")
+                            log("Refresh failed  -  token or credentials expired.")
                 else:
                     if not args.quiet:
                         log("No client credentials available for refresh.")

package/pipeline/skills/figma-common/figma-skip/SKILL.md

@@ -8,7 +8,7 @@ status: wip-v5
 sourced-from: upstream/figma-skip
 ---
 
-# /figma-skip — Mark Component as Skipped
+# /figma-skip  -  Mark Component as Skipped
 
 ## Parse Arguments
 
@@ -32,7 +32,7 @@ Derive filename: `{nodeId with : replaced by -}.json` (e.g., `3-9045.json`).
 
 ## Workflow
 
-### STEP 1 — Resolve Component Name
+### STEP 1  -  Resolve Component Name
 
 ```bash
 COMMON_PATH="${REPO_ROOT}/{repos.common.path}"
@@ -45,7 +45,7 @@ If the registry file already exists at `Shared/Figma/Components/{nodeId}.json`:
 - Read it. If `"skip": true` already set → inform user "Already skipped" and exit.
 - If not skipped → ask user if they want to mark it as skipped (it may have implementation data).
 
-### STEP 2 — Create/Update Registry Entry
+### STEP 2  -  Create/Update Registry Entry
 
 Write `Shared/Figma/Components/{nodeId}.json`:
 
@@ -76,14 +76,14 @@ Write `Shared/Figma/Components/{nodeId}.json`:
 }
 ```
 
-### STEP 3 — Regenerate Catalog
+### STEP 3  -  Regenerate Catalog
 
 ```bash
 cd "${COMMON_PATH}"
 .build/debug/FigmaRegistryUtility catalog
 ```
 
-### STEP 4 — Update Confluence Status Dashboard
+### STEP 4  -  Update Confluence Status Dashboard
 
 ```bash
 python3 "${REPO_ROOT}/.instructions/figma/figma-to-swiftui/scripts/confluence-component-status.py"
@@ -92,7 +92,7 @@ python3 "${REPO_ROOT}/.instructions/figma/figma-to-swiftui/scripts/confluence-co
 This updates the global Component Implementation Status dashboard on Confluence.
 Requires VPN. If VPN unavailable, inform user and skip.
 
-### STEP 5 — Summary
+### STEP 5  -  Summary
 
 ```
 ## Skip Summary

package/pipeline/skills/figma-common/figma-ui-patterns/SKILL.md

@@ -7,11 +7,11 @@ status: wip-v5
 sourced-from: upstream/figma-ui-patterns
 ---
 
-# /figma-ui-patterns — UI Pattern Index
+# /figma-ui-patterns  -  UI Pattern Index
 
 ## Purpose
 
-Reusable SwiftUI UI-pattern guides, indexed in one place. Each pattern lives in its own sub-markdown under `patterns/` with a self-contained recipe — API shape, SwiftUI techniques, gotchas, and a minimal reference snippet.
+Reusable SwiftUI UI-pattern guides, indexed in one place. Each pattern lives in its own sub-markdown under `patterns/` with a self-contained recipe  -  API shape, SwiftUI techniques, gotchas, and a minimal reference snippet.
 
 This skill is **complementary**, not gating:
 - During **spec-driven** work (figma-to-swiftui pipeline): phases reference patterns by slug when the architecture calls for one.
@@ -31,7 +31,7 @@ This skill is **complementary**, not gating:
     └── <new-pattern>.md
 ```
 
-Each sub-guide is a single markdown file. No deeper nesting — flat under `patterns/`.
+Each sub-guide is a single markdown file. No deeper nesting  -  flat under `patterns/`.
 
 ## How to Use
 
@@ -39,14 +39,14 @@ Each sub-guide is a single markdown file. No deeper nesting — flat under `patt
 
 1. Run `/figma-ui-patterns` to see the index below.
 2. Open `patterns/<slug>.md` for the pattern you need.
-3. Follow the recipe. Sub-guides are self-contained — you should not need to hop between them.
+3. Follow the recipe. Sub-guides are self-contained  -  you should not need to hop between them.
 
 ### As an author (adding a new pattern)
 
 1. Pick a slug: `kebab-case`, descriptive, noun-phrase (`carousel-pager`, `scallop-view`, not `how-to-carousel`).
 2. Create `patterns/<slug>.md` using the template below.
 3. Add a row to the **Index** section of this file.
-4. Keep the guide under ~200 lines. If it grows beyond that, the pattern is probably two patterns — split it.
+4. Keep the guide under ~200 lines. If it grows beyond that, the pattern is probably two patterns  -  split it.
 
 ## Sub-guide Template
 
@@ -68,7 +68,7 @@ Step-by-step SwiftUI recipe. Which primitives (ScrollView, GeometryReader, Timel
 Numbered list. Common mistakes, platform quirks (iOS version gates, accessibility regressions, performance cliffs).
 
 ## Reference Snippet
-One complete, compilable SwiftUI snippet — under 60 lines. Should run as-is in an Xcode preview.
+One complete, compilable SwiftUI snippet  -  under 60 lines. Should run as-is in an Xcode preview.
 
 ## Related Patterns
 Bullet list of other slugs in this skill (or in `figma-price-integration`, `coreui-forms`, etc.) that commonly co-occur or contrast with this one.
@@ -77,10 +77,10 @@ Bullet list of other slugs in this skill (or in `figma-price-integration`, `core
 ## Authoring Rules
 
 1. **Self-contained.** A reader opening one sub-guide should implement the pattern without hopping.
-2. **SwiftUI-first.** Prefer pure SwiftUI techniques. Drop to UIViewRepresentable only when SwiftUI cannot express the behavior — and say so in Gotchas.
+2. **SwiftUI-first.** Prefer pure SwiftUI techniques. Drop to UIViewRepresentable only when SwiftUI cannot express the behavior  -  and say so in Gotchas.
 3. **Design-token aware.** Use project tokens (`.Text.textPrimary`, `.bodyRegular`, etc.) in snippets, not raw colors/fonts. Keeps examples on-brand.
-4. **No component specifics.** A pattern is generic. If your recipe references `FlightCard` or `TripSummary`, you're writing a component guide, not a pattern guide — move it to the component's wiki instead.
-5. **Validate names before committing.** For the pattern's human-readable title, run `/intent-idempotency-check` if the name isn't already obvious — UI pattern names are easy to get wrong.
+4. **No component specifics.** A pattern is generic. If your recipe references `FlightCard` or `TripSummary`, you're writing a component guide, not a pattern guide  -  move it to the component's wiki instead.
+5. **Validate names before committing.** For the pattern's human-readable title, run `/intent-idempotency-check` if the name isn't already obvious  -  UI pattern names are easy to get wrong.
 
 ## Integration with figma-to-swiftui
 
@@ -94,11 +94,11 @@ Bullet list of other slugs in this skill (or in `figma-price-integration`, `core
 
 | Slug | Pattern | Status |
 |------|---------|--------|
-| `carousel-banner` | Auto-advancing paged banner — single item visible, swipe/tap paging, `CarouselGroup` indicator, configurable interval + loop + pause-on-interaction. | Ready |
-| `scalloped-vstack` | Scalloped VStack (boarding-pass silhouette) — vertical card with semicircular edge cuts + dashed perforation line between segments. `CoreUI.ScallopedVStack`. | Ready |
+| `carousel-banner` | Auto-advancing paged banner  -  single item visible, swipe/tap paging, `CarouselGroup` indicator, configurable interval + loop + pause-on-interaction. | Ready |
+| `scalloped-vstack` | Scalloped VStack (boarding-pass silhouette)  -  vertical card with semicircular edge cuts + dashed perforation line between segments. `CoreUI.ScallopedVStack`. | Ready |
 
 ## Anti-patterns
 
 - **Dumping ground.** This is not a place for "here's a snippet I wrote once." A pattern appears here only if it is **reusable across ≥2 real components**.
 - **Pattern-by-component.** If every component gets its own pattern file, the index stops being useful. Generalize first.
-- **Stale snippets.** If a sub-guide's snippet no longer compiles on the project's current Swift/SwiftUI version, fix or remove it — don't leave a broken recipe.
+- **Stale snippets.** If a sub-guide's snippet no longer compiles on the project's current Swift/SwiftUI version, fix or remove it  -  don't leave a broken recipe.

package/pipeline/skills/figma-common/figma-utility/SKILL.md

@@ -8,13 +8,13 @@ status: wip-v5
 sourced-from: upstream/figma-utility
 ---
 
-# /figma-utility — On-Demand Figma Data Utility
+# /figma-utility  -  On-Demand Figma Data Utility
 
 ## Purpose
 
 Standalone utility for querying Figma data on demand. Exposes Figma REST API and MCP capabilities as simple sub-commands. Does **not** modify any project files or affect other skills.
 
-This is a **read-only data tool** — it fetches and displays Figma data. It does NOT implement, commit, or modify code.
+This is a **read-only data tool**  -  it fetches and displays Figma data. It does NOT implement, commit, or modify code.
 
 ## Parameters
 
@@ -140,7 +140,7 @@ Reset all repo branches (main + submodules) to their remote defaults. Discards l
 - **Requires:** Nothing
 - **Options:** None
 
-**IMPORTANT — run as a single Bash call.** `REPO_ROOT` must be resolved once before any `cd` into submodules; if split into separate Bash calls, `git rev-parse --show-toplevel` inside a submodule returns the submodule root, not the main repo.
+**IMPORTANT  -  run as a single Bash call.** `REPO_ROOT` must be resolved once before any `cd` into submodules; if split into separate Bash calls, `git rev-parse --show-toplevel` inside a submodule returns the submodule root, not the main repo.
 
 ```bash
 REPO_ROOT="$(git rev-parse --show-toplevel)" && \
@@ -267,7 +267,7 @@ If no tokens are found, the script reports what's missing and suggests running `
 ## Independence
 
 This skill is **completely independent** from other Figma skills. It:
-- Has its own script (`figma-utility.py`) — no shared imports
+- Has its own script (`figma-utility.py`)  -  no shared imports
 - Does not read or write implementation artifacts
 - Does not modify the component registry
 - Does not create branches or commits (except `reset-branches` which resets to remote)

package/pipeline/skills/figma-common/figma-utility/scripts/figma-utility.py

@@ -720,7 +720,7 @@ def cmd_whoami():
 
 def main():
     parser = argparse.ArgumentParser(
-        description="Figma Utility — query Figma data via REST API and MCP",
+        description="Figma Utility  -  query Figma data via REST API and MCP",
         formatter_class=argparse.RawDescriptionHelpFormatter,
     )
     parser.add_argument("command", choices=[