@mmerterden/multi-agent-pipeline 8.6.2 → 10.2.0

package/pipeline/skills/figma-common/performance-iteration-commit-all/SKILL.md

@@ -1,4 +1,9 @@
-# /performance-iteration-commit-all — Batch Validate & Push All Tour Components
+---
+name: performance-iteration-commit-all
+description: Reads `_tour_tracker.json`, validates all reviewed components in a single build+test cycle, pushes all local commits in a single push per submodule, then handles issue.
+---
+
+# /performance-iteration-commit-all  -  Batch Validate & Push All Tour Components
 
 > Reads `_tour_tracker.json`, validates all reviewed components in a single build+test
 > cycle, pushes all local commits in a single push per submodule, then handles issue
@@ -16,7 +21,7 @@
 
 ## Parameters
 
-No arguments — reads `_tour_tracker.json`.
+No arguments  -  reads `_tour_tracker.json`.
 
 ```
 /performance-iteration-commit-all
@@ -37,12 +42,12 @@ TRACKER_FILE    = ${REPO_ROOT}/_tour_tracker.json
 
 ---
 
-## STEP 0 — Read Tracker & Verify State
+## STEP 0  -  Read Tracker & Verify State
 
 Read `_tour_tracker.json`.
 
 Verify:
-- `current_step` is `"STEP_3"` — if not, HALT: "Review not complete. Run /performance-review-next first."
+- `current_step` is `"STEP_3"`  -  if not, HALT: "Review not complete. Run /performance-review-next first."
 - `reviewed_components` has at least 1 entry
 - All reviewed components have local commits (check with `git log`)
 
@@ -57,15 +62,15 @@ Print:
 
 ```
 ╔══════════════════════════════════════════════════════════════╗
-║  BATCH COMMIT — PRE-FLIGHT                                   ║
+║  BATCH COMMIT  -  PRE-FLIGHT                                   ║
 ╠══════════════════════════════════════════════════════════════╣
 ║                                                              ║
 ║  Components to commit:                                       ║
-║  1. ComponentA (#1000) — reviewed ✅                         ║
-║  2. ComponentC (#1002) — reviewed ✅                         ║
+║  1. ComponentA (#1000)  -  reviewed ✅                         ║
+║  2. ComponentC (#1002)  -  reviewed ✅                         ║
 ║                                                              ║
 ║  Dropped (will NOT be committed):                            ║
-║  ❌ ComponentB (#1001) — halted, dropped                     ║
+║  ❌ ComponentB (#1001)  -  halted, dropped                     ║
 ║                                                              ║
 ╚══════════════════════════════════════════════════════════════╝
 
@@ -76,7 +81,7 @@ Wait for user confirmation.
 
 ---
 
-## STEP 1 — Validate (SINGLE PASS)
+## STEP 1  -  Validate (SINGLE PASS)
 
 ### 1a. Build
 
@@ -165,7 +170,7 @@ Validation Summary:
 
 ---
 
-## STEP 2 — Push (SINGLE PUSH per submodule)
+## STEP 2  -  Push (SINGLE PUSH per submodule)
 
 ### 2a. Push with Rebase-Retry Loop
 
@@ -179,12 +184,12 @@ MAX_RETRIES=3
 for i in $(seq 1 $MAX_RETRIES); do
   git push origin ${PUSH_BRANCH} && break
 
-  echo "Push rejected — remote updated. Rebasing (attempt $i)..."
+  echo "Push rejected  -  remote updated. Rebasing (attempt $i)..."
   git fetch origin ${PUSH_BRANCH}
   git rebase origin/${PUSH_BRANCH}
 
   if [ $? -ne 0 ]; then
-    # Rebase conflict — attempt auto-resolution for generated files
+    # Rebase conflict  -  attempt auto-resolution for generated files
     # See "Generated File Conflict Resolution" below
     # If auto-resolution fails → HALT
   fi
@@ -202,12 +207,12 @@ done
 ```
 
 **Push order matters:** common → uicomponents → wiki (dependencies flow this direction).
-In **lean mode**, wiki submodule has no commits — skip the wiki push entirely.
+In **lean mode**, wiki submodule has no commits  -  skip the wiki push entirely.
 
 #### Generated File Conflict Resolution (common submodule)
 
 During rebase, conflicts in generated files are **expected** when others have pushed to
-`iteration/develop` concurrently. **NEVER resolve these by picking a side — always
+`iteration/develop` concurrently. **NEVER resolve these by picking a side  -  always
 accept remote then regenerate.**
 
 **Conflict resolution table:**
@@ -265,7 +270,7 @@ Update tracker: record SHAs for each component.
 ```bash
 cd ${COMMON} && git fetch origin iteration/develop
 cd ${UICOMPONENTS} && git fetch origin iteration/develop
-# Wiki fetch — skip in lean mode
+# Wiki fetch  -  skip in lean mode
 if [ "$LEAN_MODE" != "true" ]; then
   cd ${WIKI} && git fetch origin master
 fi
@@ -308,7 +313,7 @@ conflict resolution (e.g., `LocalizationStringKeys.swift` missing component keys
 
 ---
 
-## STEP 3 — Issue Housekeeping (Per Component)
+## STEP 3  -  Issue Housekeeping (Per Component)
 
 > **(strict) NONE of these substeps may be skipped.** Each substep prints a
 > status line (`✅` or `❌`). The Completion Gate at the end (3g) verifies ALL
@@ -348,9 +353,9 @@ Print: `  #<N> 3a Comment: ✅` or `❌`
 
 Determine completed phases from committed files:
 - Has Swift view file → phase:implementation done
-- Has test files → phase:testing done (**skip check in lean mode — always false**)
+- Has test files → phase:testing done (**skip check in lean mode  -  always false**)
 - Has .figma.swift → phase:code-connect done
-- Has wiki markdown → phase:documentation done (**skip check in lean mode — always false**)
+- Has wiki markdown → phase:documentation done (**skip check in lean mode  -  always false**)
 
 **Add phase labels to issue (adjust for lean mode):**
 
@@ -385,7 +390,7 @@ ISSUE_NODE_ID=$(gh api graphql -f query='{ repository(owner: "{github.org}", nam
 
 ITEM_ID=$(gh api graphql -f query='mutation { addProjectV2ItemById(input: { projectId: "{github.projectV2Id}", contentId: "'"$ISSUE_NODE_ID"'" }) { item { id } } }' --jq '.data.addProjectV2ItemById.item.id')
 
-# Set Phase = Documentation (last completed) — or Code Connect in lean mode
+# Set Phase = Documentation (last completed)  -  or Code Connect in lean mode
 LAST_PHASE_ID="7307fb8f"  # Documentation
 if [ "$LEAN_MODE" = "true" ]; then
   LAST_PHASE_ID="5384b1e1"  # Code Connect
@@ -466,7 +471,7 @@ python3 ${REPO_ROOT}/.instructions/figma/figma-to-swiftui/scripts/update-status-
 
 If the script is not available, skip with a warning:
 ```
-⚠️  Status dashboard regeneration skipped — script not found.
+⚠️  Status dashboard regeneration skipped  -  script not found.
      Run /figma-to-swift-ui-status-update manually to update counts.
 ```
 
@@ -599,7 +604,7 @@ Print the housekeeping checklist for ALL components:
 ║  HOUSEKEEPING COMPLETION GATE                                ║
 ╠══════════════════════════════════════════════════════════════╣
 ║                                                              ║
-║  #308 MilesSmilesInviteInviteList                            ║
+║  #308 FeatureXInviteList                                     ║
 ║    3a Comment:    ✅                                         ║
 ║    3b Phase:      ✅ → Documentation                        ║
 ║    3c Wiki Link:  ✅                                         ║
@@ -607,7 +612,7 @@ Print the housekeeping checklist for ALL components:
 ║    3e Dashboard:  ✅ regenerated                             ║
 ║    3f Jira:       ✅ {jira.projectKey}-132507                          ║
 ║                                                              ║
-║  #309 MilesSmilesMenuVoucherRightsGroup                      ║
+║  #309 FeatureXVoucherGroup                                   ║
 ║    3a Comment:    ✅                                         ║
 ║    3b Phase:      ✅ → Documentation                        ║
 ║    3c Wiki Link:  ✅                                         ║
@@ -627,14 +632,14 @@ Print the housekeeping checklist for ALL components:
 ```
 
 **Critical substeps** (MUST pass or have valid skip reason):
-- **3a** — Comment on issue
-- **3b** — Phase + labels updated
-- **3c** — Wiki linked (if wiki committed)
-- **3f** — Jira assigned (if Jira key exists)
+- **3a**  -  Comment on issue
+- **3b**  -  Phase + labels updated
+- **3c**  -  Wiki linked (if wiki committed)
+- **3f**  -  Jira assigned (if Jira key exists)
 
 **Non-critical substeps** (warn but continue):
-- **3d** — Auto-unblock (best effort)
-- **3e** — Status dashboard (best effort)
+- **3d**  -  Auto-unblock (best effort)
+- **3e**  -  Status dashboard (best effort)
 
 If ANY critical substep shows `❌`:
 1. Print which substeps failed and for which components
@@ -645,11 +650,11 @@ If gate passes → proceed to STEP 4.
 
 ---
 
-## STEP 4 — Final Report
+## STEP 4  -  Final Report
 
 ```
 ╔══════════════════════════════════════════════════════════════╗
-║  TOUR COMPLETE — FINAL REPORT                                ║
+║  TOUR COMPLETE  -  FINAL REPORT                                ║
 ╠══════════════════════════════════════════════════════════════╣
 ║                                                              ║
 ║  ┌───┬────────┬──────────────┬──────────┬────────────────┐  ║
@@ -657,7 +662,7 @@ If gate passes → proceed to STEP 4.
 ║  ├───┼────────┼──────────────┼──────────┼────────────────┤  ║
 ║  │ 1 │ #1000  │ ComponentA   │ ✅ Pushed │ abc1234       │  ║
 ║  │ 2 │ #1002  │ ComponentC   │ ✅ Pushed │ def5678       │  ║
-║  │ 3 │ #1001  │ ComponentB   │ ❌ Dropped│ —             │  ║
+║  │ 3 │ #1001  │ ComponentB   │ ❌ Dropped│  -              │  ║
 ║  └───┴────────┴──────────────┴──────────┴────────────────┘  ║
 ║                                                              ║
 ║  Validation:                                                 ║
@@ -698,14 +703,14 @@ rm -f ${TRACKER_FILE}
 | Tracker not found | HALT: "No tour in progress" |
 | current_step not STEP_3 | HALT: "Review not complete" |
 | No reviewed components | HALT: "Nothing to commit" |
-| Build fails | HALT — fix, then re-run |
-| Tests fail | HALT — fix failing component, then re-run |
-| Push rejected (after 3 retries) | HALT — manual conflict resolution needed |
+| Build fails | HALT  -  fix, then re-run |
+| Tests fail | HALT  -  fix failing component, then re-run |
+| Push rejected (after 3 retries) | HALT  -  manual conflict resolution needed |
 | Rebase conflict (generated file) | Auto-resolve: accept remote + regenerate (see 2a table) |
-| Rebase conflict (non-generated) | HALT — print conflict file, ask user to resolve |
+| Rebase conflict (non-generated) | HALT  -  print conflict file, ask user to resolve |
 | Post-push build fails | Regenerate generated files in common, commit + push fix |
-| Status dashboard script missing | Warn + skip — not blocking |
+| Status dashboard script missing | Warn + skip  -  not blocking |
 | Issue housekeeping fails (critical: 3a/3b/3c/3f) | Retry once → if still fails, HALT |
 | Issue housekeeping fails (non-critical: 3d/3e) | Warn but continue |
-| Jira unreachable | ⚠️ warn — mark 3f as skipped with reason, pass gate |
+| Jira unreachable | ⚠️ warn  -  mark 3f as skipped with reason, pass gate |
 | Completion gate fails | HALT: print failed substeps, retry once, then abort |

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

@@ -1,4 +1,9 @@
-# /performance-review-next — Interactive Component Review Session
+---
+name: performance-review-next
+description: Reads `_tour_tracker.json`, presents a dashboard of produced components, and guides the user through reviewing each one. Fix commits are separate. Halted components can be retried or dropped.
+---
+
+# /performance-review-next  -  Interactive Component Review Session
 
 > Reads `_tour_tracker.json`, presents a dashboard of produced components,
 > and guides the user through reviewing each one. Fix commits are separate.
@@ -8,7 +13,7 @@
 
 | Parameter | Required | Default | Description |
 |-----------|----------|---------|-------------|
-| `--status` | No | — | Show dashboard only, don't start review loop |
+| `--status` | No |  -  | Show dashboard only, don't start review loop |
 
 ```
 /performance-review-next
@@ -27,7 +32,7 @@ UICOMPONENTS    = ${REPO_ROOT}/{repos.components.path}
 
 ---
 
-## STEP 0 — Read Tracker & Show Dashboard
+## STEP 0  -  Read Tracker & Show Dashboard
 
 Read `_tour_tracker.json`. If not found → HALT: "No tour in progress."
 
@@ -45,8 +50,8 @@ lean_mode = tracker.get("lean_mode", False)
 ║                                                              ║
 ║  # │ Issue  │ Component    │ Status                          ║
 ║  ──┼────────┼──────────────┼──────────────────────────────── ║
-║  1 │ #1000  │ ComponentA   │ ✅ Produced — ready for review  ║
-║  2 │ #1002  │ ComponentC   │ ✅ Produced — ready for review  ║
+║  1 │ #1000  │ ComponentA   │ ✅ Produced  -  ready for review  ║
+║  2 │ #1002  │ ComponentC   │ ✅ Produced  -  ready for review  ║
 ║  3 │ #1001  │ ComponentB   │ ❌ Halted (Phase 4)             ║
 ║                                                              ║
 ║  Reviewed: 0/2 produced                                      ║
@@ -57,7 +62,7 @@ lean_mode = tracker.get("lean_mode", False)
 If `lean_mode` is `true`, add a warning banner after the dashboard:
 
 ```
-⚠️  LEAN MODE — Tests & wiki were NOT generated.
+⚠️  LEAN MODE  -  Tests & wiki were NOT generated.
     Review covers: implementation (Phase 4) + Code Connect (Phase 6) only.
 ```
 
@@ -65,7 +70,7 @@ If `--status` → print dashboard and exit.
 
 ---
 
-## STEP 1 — Build All (One Time)
+## STEP 1  -  Build All (One Time)
 
 Before any review, run a single build to verify the current state:
 
@@ -89,19 +94,19 @@ Print:
 
 Do NOT proceed until build passes.
 
-**If build passes:** Print "Build ✅ — all components compile" and proceed to STEP 2.
+**If build passes:** Print "Build ✅  -  all components compile" and proceed to STEP 2.
 
 ---
 
-## STEP 2 — Review Loop
+## STEP 2  -  Review Loop
 
 Ask user which component to review:
 
 ```
 Which component would you like to review?
-  [1] ComponentA (#1000) — ready for review
-  [2] ComponentC (#1002) — ready for review
-  [3] ComponentB (#1001) — halted (retry/drop)
+  [1] ComponentA (#1000)  -  ready for review
+  [2] ComponentC (#1002)  -  ready for review
+  [3] ComponentB (#1001)  -  halted (retry/drop)
   [done] All reviews complete → proceed to commit
 ```
 
@@ -131,13 +136,13 @@ When user selects a produced component:
 
 3. **Present review options:**
    ```
-   ComponentA (#1000) — Review
+   ComponentA (#1000)  -  Review
      Files: 8 files (view, config, tests, snapshots, wiki, code-connect)    # lean: fewer files
      Tests: ✅ 12 passed    # lean: ⏭ skipped (lean mode)
    
    Actions:
      [approve] Mark as reviewed ✅
-     [fix]     I see an issue — let me fix it
+     [fix]     I see an issue  -  let me fix it
      [back]    Back to dashboard
    ```
 
@@ -166,8 +171,8 @@ When user selects a produced component:
 When user selects a halted component:
 
 ```
-ComponentB (#1001) — Halted at Phase 4
-  Reason: Build failure — missing dependency protocol
+ComponentB (#1001)  -  Halted at Phase 4
+  Reason: Build failure  -  missing dependency protocol
   
   Actions:
     [retry]  Re-produce this component from scratch
@@ -198,8 +203,8 @@ When user selects "done" or all produced components are reviewed:
 ║  Dropped:   1 component (ComponentB)                         ║
 ║                                                              ║
 ║  Ready to commit:                                            ║
-║  ✅ #1000 — ComponentA                                       ║
-║  ✅ #1002 — ComponentC                                       ║
+║  ✅ #1000  -  ComponentA                                       ║
+║  ✅ #1002  -  ComponentC                                       ║
 ║                                                              ║
 ║  Next: /performance-iteration-commit-all                     ║
 ╚══════════════════════════════════════════════════════════════╝

package/pipeline/skills/figma-common/performance-start/SKILL.md

@@ -1,6 +1,11 @@
-# /performance-start — Start + Auto-Launch Performance Pipeline
+---
+name: performance-start
+description: Identical to `/figma-to-swift-ui-start` for Steps 0-5. After printing the summary (Step 6), automatically invokes `/performance-swiftui <figma-url>` to begin the implementation pipeline.
+---
+
+# /performance-start  -  Start + Auto-Launch Performance Pipeline
 
-> Identical to `/figma-to-swift-ui-start` for Steps 0–5. After printing the summary (Step 6),
+> Identical to `/figma-to-swift-ui-start` for Steps 0-5. After printing the summary (Step 6),
 > automatically invokes `/performance-swiftui <figma-url>` to begin the implementation pipeline
 > without waiting for user input.
 
@@ -8,10 +13,10 @@
 
 | Parameter | Required | Default | Description |
 |-----------|----------|---------|-------------|
-| `<issue-number>` | Yes | — | GitHub issue number from uicomponents repo |
-| `jira id <KEY>` | No | — | Jira issue key (e.g., `{jira.projectKey}-129850`). If provided, updates GitHub issue body and populates Jira task. |
-| `--tour` | No | — | Tour mode: skips fetch/pull (STEP 1) and branch creation (STEP 2). Used by `/performance-tour` when producing multiple components on `iteration/develop`. |
-| `--lean` | No | — | Lean mode: forwarded to `/performance-swiftui` to skip Phase 5 (testing) and Phase 7 (wiki). Can be combined with `--tour`. |
+| `<issue-number>` | Yes |  -  | GitHub issue number from uicomponents repo |
+| `jira id <KEY>` | No |  -  | Jira issue key (e.g., `{jira.projectKey}-129850`). If provided, updates GitHub issue body and populates Jira task. |
+| `--tour` | No |  -  | Tour mode: skips fetch/pull (STEP 1) and branch creation (STEP 2). Used by `/performance-tour` when producing multiple components on `iteration/develop`. |
+| `--lean` | No |  -  | Lean mode: forwarded to `/performance-swiftui` to skip Phase 5 (testing) and Phase 7 (wiki). Can be combined with `--tour`. |
 
 ```
 /performance-start #107
@@ -28,15 +33,15 @@ When `--tour` is passed, the following steps are **SKIPPED**:
 
 | Step | Normal Mode | Tour Mode |
 |------|------------|:---------:|
-| STEP 0 — Parse Issue | ✅ | ✅ |
-| STEP 0.5 — Confirm Pipeline Mode | ✅ | **SKIP** |
-| STEP 1 — Fetch Latest | ✅ | **SKIP** |
-| STEP 2 — Create Feature Branches | ✅ | **SKIP** |
-| STEP 3 — Registry Lookup | ✅ | ✅ |
-| STEP 3.5 — Save Specs Artifact | ✅ | ✅ |
-| STEP 4 — Assign to Me | ✅ | ✅ |
-| STEP 5 — Update Issue Status | ✅ | ✅ |
-| STEP 6 — Summary + Auto-Launch | ✅ | ✅ |
+| STEP 0  -  Parse Issue | ✅ | ✅ |
+| STEP 0.5  -  Confirm Pipeline Mode | ✅ | **SKIP** |
+| STEP 1  -  Fetch Latest | ✅ | **SKIP** |
+| STEP 2  -  Create Feature Branches | ✅ | **SKIP** |
+| STEP 3  -  Registry Lookup | ✅ | ✅ |
+| STEP 3.5  -  Save Specs Artifact | ✅ | ✅ |
+| STEP 4  -  Assign to Me | ✅ | ✅ |
+| STEP 5  -  Update Issue Status | ✅ | ✅ |
+| STEP 6  -  Summary + Auto-Launch | ✅ | ✅ |
 
 **Rationale:** In tour mode, `/performance-tour` has already fetched latest and
 all submodules are on `iteration/develop`. Creating feature branches would conflict
@@ -64,24 +69,24 @@ WIKI            = ${REPO_ROOT}/{repos.wiki.path}
 
 ---
 
-## STEP 0 — Parse Issue
+## STEP 0  -  Parse Issue
 
 ```bash
 gh issue view <N> --repo ${GH_REPO} --json number,title,body,labels,assignees
 ```
 
 Extract from the issue body:
-- **Component Name** — from `### Component Name (PascalCase)` section
-- **Figma URL** — from `### Figma URL` section
-- **Node ID** — from `### Node ID` section
-- **Registry Name** — from `### Registry Name` section
-- **Figma Page** — from `### Figma Page` section
-- **Jira Key** — from `### Jira Issue` section (if not `_No response_`)
-- **Acceptance Criteria** — from `### Acceptance Criteria` section (if not `_No response_`)
+- **Component Name**  -  from `### Component Name (PascalCase)` section
+- **Figma URL**  -  from `### Figma URL` section
+- **Node ID**  -  from `### Node ID` section
+- **Registry Name**  -  from `### Registry Name` section
+- **Figma Page**  -  from `### Figma Page` section
+- **Jira Key**  -  from `### Jira Issue` section (if not `_No response_`)
+- **Acceptance Criteria**  -  from `### Acceptance Criteria` section (if not `_No response_`)
 
 If Jira key is `_No response_` or empty **and** user provided a `jira id` parameter:
 1. Use the user-provided key as `JIRA_ISSUE`.
-2. Update the GitHub issue body — replace `_No response_` under `### Jira Issue` with a Jira link:
+2. Update the GitHub issue body  -  replace `_No response_` under `### Jira Issue` with a Jira link:
    ```bash
    # Read current body, replace the Jira section, update via gh
    CURRENT_BODY=$(gh issue view <N> --repo ${GH_REPO} --json body --jq '.body')
@@ -114,17 +119,17 @@ Print:
 
 ---
 
-## STEP 0.5 — Confirm Pipeline Mode
+## STEP 0.5  -  Confirm Pipeline Mode
 
 > **If `--tour` is set → SKIP this step.** Tour mode delegates mode selection to `/performance-tour`.
 
-After parsing the issue, **always ask the user** to confirm which pipeline mode to use — regardless of whether `--lean` was passed as a parameter. This prevents accidental full-pipeline runs when lean was intended, or vice versa.
+After parsing the issue, **always ask the user** to confirm which pipeline mode to use  -  regardless of whether `--lean` was passed as a parameter. This prevents accidental full-pipeline runs when lean was intended, or vice versa.
 
 **Use the ask-questions tool** with these options:
 
 | Header | Question | Options |
 |--------|----------|---------|
-| Pipeline Mode | `<COMPONENT_PASCAL>` implementation — which pipeline mode? | **Lean** (skip testing & wiki — Phases 5, 7) · **Full** (all 8 phases) |
+| Pipeline Mode | `<COMPONENT_PASCAL>` implementation  -  which pipeline mode? | **Lean** (skip testing & wiki  -  Phases 5, 7) · **Full** (all 8 phases) |
 
 - If `--lean` was passed in the original command, pre-select **Lean** as the recommended option.
 - If no flag was passed, pre-select **Full** as the recommended option.
@@ -137,7 +142,7 @@ This confirmation overrides whatever was passed on the command line.
 
 ---
 
-## STEP 1 — Fetch Latest
+## STEP 1  -  Fetch Latest
 
 > **If `--tour` is set → SKIP this entire step.** Tour mode assumes
 > `/performance-tour` STEP 0e has already fetched and checked out the correct branches.
@@ -163,12 +168,12 @@ git pull origin iteration/develop
 
 ---
 
-## STEP 2 — Create Feature Branches
+## STEP 2  -  Create Feature Branches
 
 > **If `--tour` is set → SKIP this entire step.** Tour mode stays on
 > `iteration/develop` with local commits. No feature branches are created.
 
-Create feature branches on **submodules only**. Do NOT create branches on the main repo — it stays on `develop`. The main repo never receives commits from this workflow; submodule refs are updated separately.
+Create feature branches on **submodules only**. Do NOT create branches on the main repo  -  it stays on `develop`. The main repo never receives commits from this workflow; submodule refs are updated separately.
 
 ```bash
 # Common (tokens, localization, accessibility, testing identifiers)
@@ -180,11 +185,11 @@ cd ${UICOMPONENTS}
 git checkout -b ${BRANCH_NAME}
 ```
 
-Wiki submodule stays on `master` — wiki changes are committed directly.
+Wiki submodule stays on `master`  -  wiki changes are committed directly.
 
 ---
 
-## STEP 3 — Registry Lookup
+## STEP 3  -  Registry Lookup
 
 ```bash
 cd ${COMMON}
@@ -192,8 +197,8 @@ cd ${COMMON}
 ```
 
 Collect:
-- `suggestedComponentLocation` — where the Swift files will go
-- `suggestedArtifactPath` — where implementation artifacts go
+- `suggestedComponentLocation`  -  where the Swift files will go
+- `suggestedArtifactPath`  -  where implementation artifacts go
 
 Print:
 
@@ -204,7 +209,7 @@ Artifact Path:      <suggestedArtifactPath>
 
 ---
 
-## STEP 3.5 — Save Specs Artifact
+## STEP 3.5  -  Save Specs Artifact
 
 If the issue has acceptance criteria (not `_No response_`), save them as an artifact that the implementation pipeline can consume.
 
@@ -223,21 +228,21 @@ Write `${suggestedArtifactPath}/pass0/specs.md`:
 
 ## Acceptance Criteria
 
-{ACCEPTANCE_CRITERIA from issue body — verbatim}
+{ACCEPTANCE_CRITERIA from issue body  -  verbatim}
 
 ## Implementation Guidance
 
 {Convert the acceptance criteria into actionable implementation instructions for the AI agent:
 - Rephrase checkbox items as concrete requirements
 - Add technical context where the criteria imply Swift/SwiftUI patterns
-- Preserve the user's intent exactly — don't add or remove requirements}
+- Preserve the user's intent exactly  -  don't add or remove requirements}
 ```
 
 If no acceptance criteria → skip this step. No file created.
 
 ---
 
-## STEP 4 — Assign to Me
+## STEP 4  -  Assign to Me
 
 Assign the GitHub issue and linked Jira task (if any) to the current user. Same logic as `/figma-issue assign`:
 
@@ -245,7 +250,7 @@ Assign the GitHub issue and linked Jira task (if any) to the current user. Same
 gh issue edit <N> --repo ${GH_REPO} --add-assignee @me
 ```
 
-If Jira key exists (from issue body or user-provided `jira id` parameter — not `_No response_` and not `DEFAULT_JIRA`):
+If Jira key exists (from issue body or user-provided `jira id` parameter  -  not `_No response_` and not `DEFAULT_JIRA`):
 
 Use **Python urllib** for all Jira API calls (curl is blocked by terminal auto-approval policy):
 
@@ -288,7 +293,7 @@ try:
     resp2 = urllib.request.urlopen(req2, timeout=15)
     print(f"Assigned {JIRA_KEY} to {username} (HTTP {resp2.status})")
 except urllib.error.HTTPError as e:
-    print(f"Assign failed — HTTP {e.code}: {e.read().decode()[:200]}")
+    print(f"Assign failed  -  HTTP {e.code}: {e.read().decode()[:200]}")
 
 # 3. Update Jira summary, description, and labels
 description = (
@@ -328,7 +333,7 @@ try:
     resp3 = urllib.request.urlopen(req3, timeout=15)
     print(f"Updated {JIRA_KEY} content (HTTP {resp3.status})")
 except urllib.error.HTTPError as e:
-    print(f"Update failed — HTTP {e.code}: {e.read().decode()[:200]}")
+    print(f"Update failed  -  HTTP {e.code}: {e.read().decode()[:200]}")
 ```
 
 Run: `python3 /tmp/jira_start_<JIRA_KEY>.py`
@@ -341,7 +346,7 @@ If Jira token not found or VPN unreachable, skip with warning:
 
 ---
 
-## STEP 5 — Update Issue Status (required)
+## STEP 5  -  Update Issue Status (required)
 
 **This step is mandatory. Do not skip it and do not defer it.** The issue
 is on the board with Status=Todo after creation. Moving it to Status=In
@@ -355,7 +360,7 @@ Set the issue phase to "Implementation" and status to "In Develop" on the Projec
 # Get issue node ID
 ISSUE_NODE_ID=$(gh api graphql -f query='{ repository(owner: "{github.org}", name: "{project.slug}-components") { issue(number: <N>) { id } } }' --jq '.data.repository.issue.id')
 
-# Add to project (if not already). This mutation is idempotent — if the
+# Add to project (if not already). This mutation is idempotent  -  if the
 # item already exists it returns the existing item id.
 ITEM_ID=$(gh api graphql -f query='mutation { addProjectV2ItemById(input: { projectId: "{github.projectV2Id}", contentId: "'"$ISSUE_NODE_ID"'" }) { item { id } } }' --jq '.data.addProjectV2ItemById.item.id')
 
@@ -377,12 +382,12 @@ gh api graphql -f query='{ node(id: "'"$ITEM_ID"'") { ... on ProjectV2Item { fie
 ```
 
 Expected output: `In Develop`. If you see anything else (or empty),
-re-fetch the current option IDs and retry — do NOT proceed to implementation
+re-fetch the current option IDs and retry  -  do NOT proceed to implementation
 without the Status set correctly.
 
 ---
 
-## STEP 6 — Summary + Auto-Launch Pipeline
+## STEP 6  -  Summary + Auto-Launch Pipeline
 
 Print:
 
@@ -411,7 +416,7 @@ Ready to implement:
 
 Forward `--lean` based on the user's confirmed selection in **STEP 0.5** (not the raw command-line flag). This starts Phase 0 of the performance-optimized implementation pipeline.
 
-> If any STEP (0–5) failed or was aborted, do NOT auto-launch. Print the error and stop.
+> If any STEP (0-5) failed or was aborted, do NOT auto-launch. Print the error and stop.
 
 ---
 
@@ -420,6 +425,6 @@ Forward `--lean` based on the user's confirmed selection in **STEP 0.5** (not th
 - **Issue not found**: Print error and stop.
 - **Issue body missing required fields**: Print which fields are missing, stop.
 - **FigmaRegistryUtility not built**: Run `swift build --product FigmaRegistryUtility` in common.
-- **Branch already exists**: Print warning — checkout existing branch instead of creating.
+- **Branch already exists**: Print warning  -  checkout existing branch instead of creating.
 - **Main repo not on develop**: Fetch and checkout automatically.
 - **Submodule not on iteration/develop**: Fetch and checkout automatically.