@mmerterden/multi-agent-pipeline 8.6.1 → 10.0.6

package/pipeline/skills/figma-common/figma-cli-iterate-mend/SKILL.md

@@ -1,12 +1,17 @@
-# /figma-cli-iterate-mend — Full Mend Pipeline Orchestrator for CLI
+---
+name: figma-cli-iterate-mend
+description: Runs the complete Figma-to-SwiftUI mend pipeline for a single issue whose component already exists under `Discarded/` and must be re-implemented from scratch: pick → start → pre-flight (locate + catalog old files) →.
+---
+
+# /figma-cli-iterate-mend  -  Full Mend Pipeline Orchestrator for CLI
 
 ## Purpose
 
 Runs the complete Figma-to-SwiftUI **mend** pipeline for a single issue whose component already exists under `Discarded/` and must be re-implemented from scratch: pick → start → pre-flight (locate + catalog old files) → implement (phases 0-7 with selective old-file reference injection) → cleanup old files → commit. Returns a structured `ORCHESTRATOR_RESULT` block that the CLI orchestrator can parse.
 
 This skill IS the mend orchestrator. It is the union of:
-- `/figma-cli-iterate` — leaf-phase-only subagent dispatch, structured result output
-- `/figma-mend` — discarded-component location, old-file cataloging, per-phase reference injection, post-implementation cleanup
+- `/figma-cli-iterate`  -  leaf-phase-only subagent dispatch, structured result output
+- `/figma-mend`  -  discarded-component location, old-file cataloging, per-phase reference injection, post-implementation cleanup
 
 **All leaf phase instructions, scripts, and references come from `.instructions/figma/figma-to-swiftui/`**. Nothing is duplicated. The only phases that differ from `/figma-cli-iterate` are:
 
@@ -16,7 +21,7 @@ This skill IS the mend orchestrator. It is the union of:
 
 ## Forbidden Dispatches
 
-**NEVER dispatch these as subagents — they are orchestrators that would try to dispatch further:**
+**NEVER dispatch these as subagents  -  they are orchestrators that would try to dispatch further:**
 
 - `/figma-mend` (entire mend pipeline)
 - `/figma-to-swiftui` (entire regular pipeline)
@@ -58,17 +63,17 @@ SCRIPT_DIR      = .instructions/figma/figma-to-swiftui/scripts
 
 ---
 
-## STEP 0 — Pick Issue
+## STEP 0  -  Pick Issue
 
 Same logic as `/figma-iterate` STEP 0. Read `.instructions/figma/figma-iterate/SKILL.md` STEP 0 for details.
 
 Extract from issue body: `componentName`, `figmaUrl`, `nodeId`, `nodeIdDash` (dash form, e.g. `517-834`), `jiraKey`, `registryName`, `figmaPage`, `acceptanceCriteria`.
 
-If the issue does NOT have a `mend` label or the body does not reference `Discarded/`, you may still proceed — the PRE-FLIGHT step below is the authoritative check for whether this is a mend candidate.
+If the issue does NOT have a `mend` label or the body does not reference `Discarded/`, you may still proceed  -  the PRE-FLIGHT step below is the authoritative check for whether this is a mend candidate.
 
 ---
 
-## STEP 1 — Start
+## STEP 1  -  Start
 
 Run inline (not as a skill). Read `.instructions/figma/figma-to-swift-ui-start/SKILL.md` for the full procedure:
 
@@ -82,9 +87,9 @@ Run inline (not as a skill). Read `.instructions/figma/figma-to-swift-ui-start/S
 
 ---
 
-## STEP 2 — Pre-Flight: Locate and Catalog Old Component
+## STEP 2  -  Pre-Flight: Locate and Catalog Old Component
 
-**Run entirely in the orchestrator — no subagents.** Uses `Grep`, `Glob`, and `Bash` directly.
+**Run entirely in the orchestrator  -  no subagents.** Uses `Grep`, `Glob`, and `Bash` directly.
 
 ### PRE-1: LOCATE_OLD_COMPONENT
 
@@ -152,9 +157,9 @@ Build `oldFilesCatalog` as an in-memory structure:
 
 ### PRE-3: RESOLVE_NAMES
 
-- `oldComponentName` — from PRE-1 (directory basename under `Discarded/`)
-- `newComponentName` — from the issue's `Component Name (PascalCase)` field, or from Phase 0 registry lookup if the issue does not specify
-- `nameChanged` — `true` if `oldComponentName != newComponentName`, else `false`
+- `oldComponentName`  -  from PRE-1 (directory basename under `Discarded/`)
+- `newComponentName`  -  from the issue's `Component Name (PascalCase)` field, or from Phase 0 registry lookup if the issue does not specify
+- `nameChanged`  -  `true` if `oldComponentName != newComponentName`, else `false`
 
 ### PRE-4: DEFERRED_CONTEXT_PERSIST
 
@@ -162,9 +167,9 @@ Hold `oldFilesCatalog` in memory. Write `{artifactPath}/mend-context.json` immed
 
 ---
 
-## STEP 3 — Implement (Phases 0-7)
+## STEP 3  -  Implement (Phases 0-7)
 
-This is the core orchestration. Run each phase by dispatching leaf subagents and scripts — **same phase dispatch table as `/figma-cli-iterate`**.
+This is the core orchestration. Run each phase by dispatching leaf subagents and scripts  -  **same phase dispatch table as `/figma-cli-iterate`**.
 
 ### Spec Injection + Mend Injection
 
@@ -188,7 +193,7 @@ You are executing {Phase Name} of the Figma-to-SwiftUI workflow.
 - Mode: MEND (re-implementing a discarded component)
 
 ## CRITICAL SPEC GATES (only if specs exist)
-{Concrete requirements extracted from specs — phrased as mandatory instructions.}
+{Concrete requirements extracted from specs  -  phrased as mandatory instructions.}
 
 ## Tool Restrictions
 {from dispatch table}
@@ -204,12 +209,12 @@ Read the return protocol from:
 {relevant reference files from the read-order table in figma-to-swiftui/SKILL.md}
 
 ## Previous Phase Artifacts
-{artifact paths in read order — compact first}
+{artifact paths in read order  -  compact first}
 
 ## Complementary Reference (Old Implementation)
 
 This component is being RE-IMPLEMENTED from Discarded/.
-Old source files (read as reference — do NOT copy verbatim):
+Old source files (read as reference  -  do NOT copy verbatim):
 {list of relevant old file paths for this phase, from oldFilesCatalog via the Selective File Injection Table}
 
 Preserve domain-specific patterns from the old implementation if architecturally sound:
@@ -220,7 +225,7 @@ Preserve domain-specific patterns from the old implementation if architecturally
 
 IMPORTANT: The new implementation MUST follow current workflow standards
 (macros, Configuration pattern, design tokens, naming rules). Use old code
-ONLY as reference for domain logic — not as a template for architecture.
+ONLY as reference for domain logic  -  not as a template for architecture.
 If the old file violates a current rule (e.g. a concrete {Name}Item struct),
 do NOT copy the violation forward.
 ```
@@ -259,7 +264,7 @@ Each phase receives ONLY the relevant old files to keep context tight. Reference
 | Phase | Old files injected |
 |-------|--------------------|
 | 0 | None (standard init, but mend-context.json is written here) |
-| 1 | None (automated script — no subagent prompt) |
+| 1 | None (automated script  -  no subagent prompt) |
 | 2A | `oldFilesCatalog.documentation`, `oldFilesCatalog.sources` |
 | 2B | `oldFilesCatalog.documentation` |
 | 2C | `oldFilesCatalog.documentation`, `oldFilesCatalog.sources` |
@@ -322,11 +327,11 @@ Append to `{artifactPath}/IMPLEMENTATION_HISTORY.md`:
 
 **Phase 2**: Exact same structure as `/figma-cli-iterate`. Wave 1 dispatches 2A + 2B + 2C in parallel; Wave 2 dispatches 2D; then `phase2-finalize.py`. Apply the injection table above for each AI subagent.
 
-**Phase 3**: Same as `/figma-cli-iterate` — Wave 1 script + 3A/3C/3H, token resolution if needed, Wave 2 (3D), Wave 3 script, spec compile, write `pass3/_index.md`. Apply the injection table.
+**Phase 3**: Same as `/figma-cli-iterate`  -  Wave 1 script + 3A/3C/3H, token resolution if needed, Wave 2 (3D), Wave 3 script, spec compile, write `pass3/_index.md`. Apply the injection table.
 
-**Phase 4**: Same as `/figma-cli-iterate` — read SIMPLE/COMPLEX, Wave 1 (4B + 4C + 4A if COMPLEX), Wave 2 (4D + 4E if COMPLEX), validate, build. Apply the injection table. Phase 4B is the primary reference phase and receives ALL old source files.
+**Phase 4**: Same as `/figma-cli-iterate`  -  read SIMPLE/COMPLEX, Wave 1 (4B + 4C + 4A if COMPLEX), Wave 2 (4D + 4E if COMPLEX), validate, build. Apply the injection table. Phase 4B is the primary reference phase and receives ALL old source files.
 
-**Phase 5**: Same as `/figma-cli-iterate` — switch to local common, Wave 1 (5A + 5B), Wave 2 (5C if applicable), run tests sequentially, revert Package.swift. Apply the injection table — if the old tests exist they are very valuable reference for the new ones.
+**Phase 5**: Same as `/figma-cli-iterate`  -  switch to local common, Wave 1 (5A + 5B), Wave 2 (5C if applicable), run tests sequentially, revert Package.swift. Apply the injection table  -  if the old tests exist they are very valuable reference for the new ones.
 
 **Phase 6**: Dispatch subagent with `oldFilesCatalog.codeConnect` injected → run `phase6-finalize.py` as safety net.
 
@@ -334,7 +339,7 @@ Append to `{artifactPath}/IMPLEMENTATION_HISTORY.md`:
 
 ---
 
-## STEP 4 — Cleanup Old Files
+## STEP 4  -  Cleanup Old Files
 
 Runs automatically after Phase 7 SUCCESS, **before** STEP 5 commit. This ensures the deletions are part of the same commit as the new implementation.
 
@@ -386,7 +391,7 @@ cd "${UICOMPONENTS}"
 xcodebuild -scheme UIComponents -destination 'generic/platform=iOS Simulator' build 2>&1 | grep -E "(error:|BUILD (SUCCEEDED|FAILED))" | tail
 ```
 
-Since the old files lived in `Discarded/` (not in the compiled target), the delete should never break the build. If it does, HALT and report the broken references — do not attempt automatic recovery.
+Since the old files lived in `Discarded/` (not in the compiled target), the delete should never break the build. If it does, HALT and report the broken references  -  do not attempt automatic recovery.
 
 ### CLEANUP-6: UPDATE_HISTORY
 
@@ -404,7 +409,7 @@ Append to `{artifactPath}/IMPLEMENTATION_HISTORY.md`:
 
 ---
 
-## STEP 5 — Commit
+## STEP 5  -  Commit
 
 Run inline. Read `.instructions/figma/figma-iteration-commit/SKILL.md` for the full procedure. Same as `/figma-cli-iterate`:
 
@@ -416,19 +421,19 @@ Run inline. Read `.instructions/figma/figma-iteration-commit/SKILL.md` for the f
 6. Issue housekeeping (comment, phase update, wiki link)
 7. Auto-unblock dependents
 
-The commit on the uicomponents submodule will naturally include both the new component files AND the deletions from STEP 4 — one atomic mend commit.
+The commit on the uicomponents submodule will naturally include both the new component files AND the deletions from STEP 4  -  one atomic mend commit.
 
 **Commit message hint**: use `feat(uicomponents): [JIRA-KEY] mend {newComponentName} component` instead of `feat(uicomponents): [JIRA-KEY] add {newComponentName} component` so reviewers see at a glance that this replaces a Discarded/ component.
 
 ---
 
-## STEP 6 — Loop
+## STEP 6  -  Loop
 
 Same logic as `/figma-iterate` STEP 4. If specific issue → exit after one. Otherwise → pick next mend issue.
 
 ---
 
-## STEP 7 — Output Result
+## STEP 7  -  Output Result
 
 Output EXACTLY this block as your FINAL message. Nothing else after it.
 
@@ -493,6 +498,6 @@ ORCHESTRATOR_RESULT:
 - **Pre-flight LOCATE_OLD_COMPONENT fails**: Output FAILED with phase `pre-flight` and suggest running `/figma-cli-iterate` (no mend needed).
 - **Phase HALT**: Show reason, ask user. If resolved → retry phase. If skipped → FAILED for this component, move to next.
 - **Build failure during Phase 4**: Attempt auto-fix. If unfixable → FAILED.
-- **Cleanup VERIFY_NEW_IMPLEMENTATION fails**: FAILED with phase `cleanup`. Old files are NOT deleted. New implementation must be fixed before re-running the skill with the same issue (which will resume from pre-flight — `mend-context.json` persists).
+- **Cleanup VERIFY_NEW_IMPLEMENTATION fails**: FAILED with phase `cleanup`. Old files are NOT deleted. New implementation must be fixed before re-running the skill with the same issue (which will resume from pre-flight  -  `mend-context.json` persists).
 - **3 consecutive failures**: Stop iteration.
-- **Subagents can't dispatch subagents**: This is why we dispatch only leaf phases. If a phase instruction file references dispatching subagents, ignore that — run its gates directly in the subagent.
+- **Subagents can't dispatch subagents**: This is why we dispatch only leaf phases. If a phase instruction file references dispatching subagents, ignore that  -  run its gates directly in the subagent.

package/pipeline/skills/figma-common/figma-cli-lean-iterate/SKILL.md

@@ -1,16 +1,21 @@
-# /figma-cli-lean-iterate — Lean Pipeline Orchestrator for CLI
+---
+name: figma-cli-lean-iterate
+description: Runs a lean Figma-to-SwiftUI pipeline for one or more issues: pick → start → implement (phases 0-4) → code connect (phase 6) → commit. Skips testing (phase 5) and wiki (phase 7).
+---
+
+# /figma-cli-lean-iterate  -  Lean Pipeline Orchestrator for CLI
 
 ## Purpose
 
 Runs a **lean** Figma-to-SwiftUI pipeline for one or more issues: pick → start → implement (phases 0-4) → code connect (phase 6) → commit. **Skips testing (phase 5) and wiki (phase 7).** Returns a structured `ORCHESTRATOR_RESULT` block that the CLI orchestrator can parse.
 
-This skill is identical in structure to `/figma-cli-iterate` — the only difference is that phases 5 and 7 are omitted. Use this when you want a faster turnaround and will run tests/wiki separately (or not at all).
+This skill is identical in structure to `/figma-cli-iterate`  -  the only difference is that phases 5 and 7 are omitted. Use this when you want a faster turnaround and will run tests/wiki separately (or not at all).
 
-This skill IS the orchestrator. It dispatches **only leaf-phase subagents** — individual phase instruction files that read one doc, execute gates, and return. It never delegates to multi-phase meta-skills.
+This skill IS the orchestrator. It dispatches **only leaf-phase subagents**  -  individual phase instruction files that read one doc, execute gates, and return. It never delegates to multi-phase meta-skills.
 
 ## Forbidden Dispatches
 
-**NEVER dispatch these as subagents — they are orchestrators that would try to dispatch further:**
+**NEVER dispatch these as subagents  -  they are orchestrators that would try to dispatch further:**
 
 - `/figma-to-swift-ui-implement` (Phases 0-4)
 - `/figma-to-swift-ui-test` (Phase 5)
@@ -42,11 +47,11 @@ REF_DIR         = .instructions/figma/figma-to-swiftui/reference
 SCRIPT_DIR      = .instructions/figma/figma-to-swiftui/scripts
 ```
 
-Note: the `WIKI` submodule is intentionally omitted from the constants — the lean flow never touches it.
+Note: the `WIKI` submodule is intentionally omitted from the constants  -  the lean flow never touches it.
 
 ---
 
-## STEP 0 — Pick Issue
+## STEP 0  -  Pick Issue
 
 Same logic as `/figma-iterate` STEP 0. Read `.instructions/figma/figma-iterate/SKILL.md` STEP 0 for details.
 
@@ -54,17 +59,17 @@ Extract from issue body: `componentName`, `figmaUrl`, `nodeId`, `jiraKey`, `regi
 
 ---
 
-## STEP 1 — Start
+## STEP 1  -  Start
 
 Run inline (not as a skill). Read `.instructions/figma/figma-to-swift-ui-start/SKILL.md` for the full procedure:
 
 1. Parse issue → extract metadata
 2. Fetch latest → checkout `develop` (main stays on develop, NO feature branch), `iteration/develop` (submodules)
-3. Create feature branches on **submodules only** (common, uicomponents) — wiki submodule is NOT checked out
+3. Create feature branches on **submodules only** (common, uicomponents)  -  wiki submodule is NOT checked out
 4. Registry lookup → `componentLocation`, `artifactPath`
 5. Save specs artifact if acceptance criteria exist
 6. Assign (GitHub + Jira)
-7. **Move GitHub issue to "In Develop" on the Projects V2 board** — required. Read STEP 5 of the start skill. Run both GraphQL mutations: set Status option `bc6c45f7` (In Develop) and Phase option `0577dcda` (Implementation). Do NOT skip this — new issues are created with Status=Todo, so this transition is how the board reflects "someone is working on it".
+7. **Move GitHub issue to "In Develop" on the Projects V2 board**  -  required. Read STEP 5 of the start skill. Run both GraphQL mutations: set Status option `bc6c45f7` (In Develop) and Phase option `0577dcda` (Implementation). Do NOT skip this  -  new issues are created with Status=Todo, so this transition is how the board reflects "someone is working on it".
 
 ---
 
@@ -77,7 +82,7 @@ These 6 rules govern orchestrator behavior. Violations have caused repeated fail
 
 ---
 
-## STEP 2 — Implement (Phases 0-4, 6)
+## STEP 2  -  Implement (Phases 0-4, 6)
 
 This is the core orchestration. Run each phase by dispatching leaf subagents and scripts.
 
@@ -88,7 +93,7 @@ This is the core orchestration. Run each phase by dispatching leaf subagents and
 Before dispatching any Phase 4+ subagent, check if `{artifactPath}/pass0/specs.md` exists. If it does:
 1. Read the specs
 2. Extract concrete requirements
-3. Inject them as **CRITICAL SPEC GATES** in the subagent dispatch prompt — NOT as a sidecar "also read this file" instruction
+3. Inject them as **CRITICAL SPEC GATES** in the subagent dispatch prompt  -  NOT as a sidecar "also read this file" instruction
 
 This ensures spec requirements become indistinguishable from standard gates.
 
@@ -113,18 +118,18 @@ All instruction files relative to `${PHASE_DIR}/`.
 | 4C | `phase-4c-documentation.md` | sonnet | Yes (leaf) |
 | 4D | `phase-4d-preview.md` | sonnet | Yes (leaf) |
 | 4E | `phase-4e-modifiers.md` | sonnet | Yes (leaf, COMPLEX only) |
-| ~~5A~~ | *(skipped — lean)* | — | — |
-| ~~5B~~ | *(skipped — lean)* | — | — |
-| ~~5C~~ | *(skipped — lean)* | — | — |
+| ~~5A~~ | *(skipped  -  lean)* |  -  |  -  |
+| ~~5B~~ | *(skipped  -  lean)* |  -  |  -  |
+| ~~5C~~ | *(skipped  -  lean)* |  -  |  -  |
 | 6 | `phase-6-code-connect.md` | opus | Yes (leaf) |
-| ~~7~~ | *(skipped — lean)* | — | — |
+| ~~7~~ | *(skipped  -  lean)* |  -  |  -  |
 
 ### Dispatch Prompt Template
 
 For each leaf subagent:
 
 ```
-You are executing {Phase Name} of the Figma-to-SwiftUI workflow (lean run — no testing, no wiki).
+You are executing {Phase Name} of the Figma-to-SwiftUI workflow (lean run  -  no testing, no wiki).
 
 ## Context
 - Component: {componentName}
@@ -134,7 +139,7 @@ You are executing {Phase Name} of the Figma-to-SwiftUI workflow (lean run — no
 - Component Location: {componentLocation}
 
 ## CRITICAL SPEC GATES (only if specs exist)
-{Concrete requirements extracted from specs — phrased as mandatory instructions, not a file reference}
+{Concrete requirements extracted from specs  -  phrased as mandatory instructions, not a file reference}
 
 ## Tool Restrictions
 {from dispatch table}
@@ -150,7 +155,7 @@ Read the return protocol from:
 {relevant reference files from the read-order table in figma-to-swiftui/SKILL.md}
 
 ## Previous Phase Artifacts
-{artifact paths in read order — compact first}
+{artifact paths in read order  -  compact first}
 ```
 
 ### Phase Execution Flow
@@ -187,40 +192,40 @@ If `COMPLETE_WITH_DEFERRED` → dispatch Phase 1 deferred resolution subagent.
 3. Wave 1 (parallel): dispatch 4B + 4C (+ 4A if COMPLEX)
 4. Wave 2 (parallel): dispatch 4D (+ 4E if COMPLEX)
 5. Validate: `bash ${SCRIPT_DIR}/validate-phase4.sh ...`
-6. Build: `xcodebuild build ...` — fix errors if any
+6. Build: `xcodebuild build ...`  -  fix errors if any
 7. Registry finalize: `python3 ${SCRIPT_DIR}/phase4-finalize.py ...`
 
-**Phase 5 (TESTING)**: **SKIPPED — lean flow.** Do NOT switch Package.swift to local common. Do NOT dispatch 5A/5B/5C. Do NOT run tests. The `status.ios.tested` flag will stay at its previous value.
+**Phase 5 (TESTING)**: **SKIPPED  -  lean flow.** Do NOT switch Package.swift to local common. Do NOT dispatch 5A/5B/5C. Do NOT run tests. The `status.ios.tested` flag will stay at its previous value.
 
 **Phase 6**: Dispatch subagent → run `${SCRIPT_DIR}/phase6-finalize.py` as safety net.
 
-**Phase 7 (WIKI)**: **SKIPPED — lean flow.** Do NOT dispatch 7A. Do NOT touch the wiki submodule. The `status.ios.wiki` flag will stay at its previous value.
+**Phase 7 (WIKI)**: **SKIPPED  -  lean flow.** Do NOT dispatch 7A. Do NOT touch the wiki submodule. The `status.ios.wiki` flag will stay at its previous value.
 
 ---
 
-## STEP 3 — Commit
+## STEP 3  -  Commit
 
 Run inline. Read `.instructions/figma/figma-iteration-commit/SKILL.md` for the full procedure, with these lean-mode adjustments:
 
 1. Rebase submodules to `iteration/develop` if on feature branch
 2. Build validation
-3. Commit to `iteration/develop` (**common → uicomponents only** — wiki submodule is intentionally untouched)
+3. Commit to `iteration/develop` (**common → uicomponents only**  -  wiki submodule is intentionally untouched)
 4. Push with rebase-retry loop
 5. Clean up feature branches (common + uicomponents only)
-6. Issue housekeeping (comment, progress table — but the Tests and Wiki rows stay at their previous state)
+6. Issue housekeeping (comment, progress table  -  but the Tests and Wiki rows stay at their previous state)
 7. Auto-unblock dependents
 
 **Skip any step in `/figma-iteration-commit` that writes to or pushes the wiki submodule.**
 
 ---
 
-## STEP 4 — Loop
+## STEP 4  -  Loop
 
 Same logic as `/figma-iterate` STEP 4. If specific issue → exit after one. If `--count` → decrement. Otherwise → pick next.
 
 ---
 
-## STEP 5 — Output Result
+## STEP 5  -  Output Result
 
 Output EXACTLY this block as your FINAL message. Nothing else after it.
 
@@ -238,9 +243,9 @@ ORCHESTRATOR_RESULT:
   commits:
     common: <SHA>
     uicomponents: <SHA>
-    wiki: null   # lean run — wiki not touched
+    wiki: null   # lean run  -  wiki not touched
   phases: [0, 1, 2, 3, 4, 6]   # 5 and 7 intentionally omitted
-  testsRun: 0   # lean run — no tests executed
+  testsRun: 0   # lean run  -  no tests executed
   summary: <one-line>
 ```
 
@@ -279,5 +284,5 @@ ORCHESTRATOR_RESULT:
 - **Phase HALT**: Show reason, ask user. If resolved → retry phase. If skipped → FAILED for this component, move to next.
 - **Build failure**: Attempt auto-fix. If unfixable → FAILED.
 - **3 consecutive failures**: Stop iteration.
-- **Subagents can't dispatch subagents**: This is why we dispatch only leaf phases. If a phase instruction file references dispatching subagents, ignore that — run its gates directly in the subagent.
-- **Accidental phase-5 / phase-7 dispatch**: If you catch yourself dispatching a 5A/5B/5C/7A subagent, STOP immediately. This is the lean flow — those phases must not run.
+- **Subagents can't dispatch subagents**: This is why we dispatch only leaf phases. If a phase instruction file references dispatching subagents, ignore that  -  run its gates directly in the subagent.
+- **Accidental phase-5 / phase-7 dispatch**: If you catch yourself dispatching a 5A/5B/5C/7A subagent, STOP immediately. This is the lean flow  -  those phases must not run.

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

@@ -1,6 +1,6 @@
 ---
 name: figma-cli-skip
-description: CLI variant of /figma-skip — fetches origin iteration/develop on mobile-common, marks a Figma component as skipped in the registry, commits, pushes, and returns a structured ORCHESTRATOR_RESULT block for the CLI.
+description: CLI variant of /figma-skip  -  fetches origin iteration/develop on mobile-common, marks a Figma component as skipped in the registry, commits, pushes, and returns a structured ORCHESTRATOR_RESULT block for the CLI.
 user-invocable: true
 argument-hint: <figma-url> [<figma-url> ...] [--reason <reason>]
 allowed-tools: Bash, Read, Write, Edit
@@ -8,7 +8,7 @@ status: wip-v5
 sourced-from: upstream/figma-cli-skip
 ---
 
-# /figma-cli-skip — CLI Skip Orchestrator
+# /figma-cli-skip  -  CLI Skip Orchestrator
 
 ## Purpose
 
@@ -32,11 +32,11 @@ Use `/figma-skip` directly when you need the Confluence dashboard refreshed.
 
 > **NEVER create branches on the main repo (REPO_ROOT).** This skill only
 > touches the `mobile-common` submodule. Main repo submodule pointer updates
-> are out of scope — handle them separately.
+> are out of scope  -  handle them separately.
 
 > **NEVER commit unrelated working-tree changes.** Stage only the registry
 > JSON(s) you wrote and the catalog output files the `FigmaRegistryUtility
-> catalog` command produced. Use explicit file paths with `git add` — never
+> catalog` command produced. Use explicit file paths with `git add`  -  never
 > `git add -A` / `git add .`.
 
 > **NEVER skip hooks (`--no-verify`) or force-push.** If push is rejected
@@ -75,11 +75,11 @@ UTILITY         = ${COMMON}/.build/debug/FigmaRegistryUtility
 
 ---
 
-## STEP 0 — Parse Arguments
+## STEP 0  -  Parse Arguments
 
 Split `$ARGUMENTS` into URLs and flags. Extract:
-- `urls[]` — every non-flag argument that looks like a Figma URL
-- `reason` — value after `--reason` (may be empty)
+- `urls[]`  -  every non-flag argument that looks like a Figma URL
+- `reason`  -  value after `--reason` (may be empty)
 
 If `urls` is empty → output `FAILED` with `reason: "No Figma URL provided"`.
 
@@ -87,7 +87,7 @@ For each URL, extract `fileKey` and `nodeId` (colon form).
 
 ---
 
-## STEP 1 — Sync `mobile-common` to `origin/iteration/develop`
+## STEP 1  -  Sync `mobile-common` to `origin/iteration/develop`
 
 ```bash
 cd "${COMMON}"
@@ -104,14 +104,14 @@ CURRENT_BRANCH=$(git branch --show-current)
 git pull --ff-only origin iteration/develop
 ```
 If fast-forward fails (local has diverged work) → HALT with
-`FAILED / reason: "mobile-common iteration/develop has diverged from origin — resolve manually before running figma-cli-skip"`.
+`FAILED / reason: "mobile-common iteration/develop has diverged from origin  -  resolve manually before running figma-cli-skip"`.
 
 **If on a different branch**:
 Check whether the working tree is clean:
 ```bash
 git status --porcelain
 ```
-- If dirty → HALT with `FAILED / reason: "mobile-common working tree is dirty on {branch} — commit or stash before running figma-cli-skip"`.
+- If dirty → HALT with `FAILED / reason: "mobile-common working tree is dirty on {branch}  -  commit or stash before running figma-cli-skip"`.
 - If clean → checkout and fast-forward:
   ```bash
   git checkout iteration/develop
@@ -123,7 +123,7 @@ After this step, `mobile-common` must be on `iteration/develop` and even with
 
 ---
 
-## STEP 2 — Ensure `FigmaRegistryUtility` Is Built
+## STEP 2  -  Ensure `FigmaRegistryUtility` Is Built
 
 ```bash
 cd "${COMMON}"
@@ -136,7 +136,7 @@ If the build fails → HALT with `FAILED / reason: "FigmaRegistryUtility build f
 
 ---
 
-## STEP 3 — Process Each URL
+## STEP 3  -  Process Each URL
 
 For each `(fileKey, nodeId)` pair:
 
@@ -148,7 +148,7 @@ cd "${COMMON}"
 ```
 
 Parse `suggestedComponentName` from the JSON output. If the lookup fails
-(node not in registry), still proceed — the lookup may return a suggested
+(node not in registry), still proceed  -  the lookup may return a suggested
 name even for unknown nodes. If no name is returned at all, use the raw
 `{nodeId}` as a placeholder and note it in the summary.
 
@@ -200,7 +200,7 @@ Collect the relative path (`Shared/Figma/Components/{filename}.json`) into a
 
 ---
 
-## STEP 4 — Regenerate Catalog
+## STEP 4  -  Regenerate Catalog
 
 Run once **after all URLs have been processed**, not per-URL:
 
@@ -218,7 +218,7 @@ If catalog regeneration fails → HALT with `FAILED / reason: "Catalog regenerat
 
 ---
 
-## STEP 5 — Commit & Push
+## STEP 5  -  Commit & Push
 
 ### 5a. Stage only the intended files
 
@@ -227,7 +227,7 @@ cd "${COMMON}"
 # Registry JSONs we wrote
 git add Shared/Figma/Components/{file1}.json Shared/Figma/Components/{file2}.json ...
 # Catalog files the utility regenerated (discover via `git status --porcelain`
-# — stage every modified/untracked path that lives under Shared/Figma/ AND was
+#  -  stage every modified/untracked path that lives under Shared/Figma/ AND was
 # not already present before STEP 4)
 git add <catalog paths discovered from git status>
 ```
@@ -299,7 +299,7 @@ After a successful rebase, re-read the new HEAD SHA for the output.
 
 ---
 
-## STEP 6 — Output `ORCHESTRATOR_RESULT`
+## STEP 6  -  Output `ORCHESTRATOR_RESULT`
 
 Output EXACTLY this block as your FINAL message. Nothing else after it.
 
@@ -315,7 +315,7 @@ ORCHESTRATOR_RESULT:
     - { nodeId: <nodeId>, componentName: <name>, fileKey: <fileKey>, state: NEWLY_SKIPPED }
     - { nodeId: <nodeId>, componentName: <name>, fileKey: <fileKey>, state: ALREADY_SKIPPED }
   reason: <reason or "Not specified">
-  summary: <one-line — e.g. "Skipped 2 components, 1 already skipped">
+  summary: <one-line  -  e.g. "Skipped 2 components, 1 already skipped">
 ```
 
 If **all** components were `ALREADY_SKIPPED` (nothing new written, nothing
@@ -324,7 +324,7 @@ committed, nothing pushed), the block looks like:
 ```
 ORCHESTRATOR_RESULT:
   status: NOOP
-  commit: —
+  commit:  - 
   pushed: false
   branch: iteration/develop
   skipped:
@@ -343,7 +343,7 @@ ORCHESTRATOR_RESULT:
   branch: iteration/develop
   skippedBeforeFailure:
     - { nodeId: <nodeId>, componentName: <name>, state: <NEWLY_SKIPPED | ALREADY_SKIPPED> }
-  suggestion: <what to fix — e.g. "resolve rebase conflicts manually and re-run">
+  suggestion: <what to fix  -  e.g. "resolve rebase conflicts manually and re-run">
 ```
 
 ---