@mmerterden/multi-agent-pipeline 11.2.0 → 11.3.1

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

@@ -1,282 +0,0 @@
----
-name: figma-cli-iterate
-description: Runs the complete Figma-to-SwiftUI pipeline for one or more issues: pick → start → implement (phases 0-7) → commit. Returns a structured `ORCHESTRATOR_RESULT` block that the CLI orchestrator can parse.
----
-
-# /figma-cli-iterate  -  Full Pipeline Orchestrator for CLI
-
-## Purpose
-
-Runs the complete Figma-to-SwiftUI pipeline for one or more issues: pick → start → implement (phases 0-7) → commit. Returns a structured `ORCHESTRATOR_RESULT` block that the CLI orchestrator can parse.
-
-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:**
-
-- `/figma-to-swift-ui-implement` (Phases 0-4)
-- `/figma-to-swift-ui-test` (Phase 5)
-- `/figma-to-swift-ui-code-connect` (Phase 6)
-- `/figma-to-swift-ui-wiki` (Phase 7)
-- `/figma-iteration-commit`
-- `/figma-to-swiftui` (entire pipeline)
-
-Instead, dispatch the **leaf phase instruction files** directly via Agent tool.
-
-## Parameters
-
-```
-/figma-cli-iterate #230           ← implement specific issue
-/figma-cli-iterate                ← auto-pick next available
-```
-
----
-
-## Constants
-
-```
-GH_REPO         = {github.componentsRepo}
-REPO_ROOT       = git repo root (auto-detect)
-COMMON          = ${REPO_ROOT}/{repos.common.path}
-UICOMPONENTS    = ${REPO_ROOT}/{repos.components.path}
-WIKI            = ${REPO_ROOT}/{repos.wiki.path}
-PHASE_DIR       = .instructions/figma/figma-to-swiftui/phases
-REF_DIR         = .instructions/figma/figma-to-swiftui/reference
-SCRIPT_DIR      = .instructions/figma/figma-to-swiftui/scripts
-```
-
----
-
-## 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`, `jiraKey`, `registryName`, `figmaPage`, `acceptanceCriteria`.
-
----
-
-## 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)
-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".
-
----
-
-## required PRE-READ
-
-Before dispatching any phase subagent, read:
-  ${REF_DIR}/orchestrator-discipline.md
-
-These 6 rules govern orchestrator behavior. Violations have caused repeated failures. Follow them strictly.
-
----
-
-## STEP 2  -  Implement (Phases 0-7)
-
-This is the core orchestration. Run each phase by dispatching leaf subagents and scripts.
-
-### Spec Injection (Option A)
-
-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
-
-This ensures spec requirements become indistinguishable from standard gates.
-
-### Phase Dispatch Table
-
-All instruction files relative to `${PHASE_DIR}/`.
-
-| Phase | Instruction | Model | Subagent? |
-|-------|-------------|-------|-----------|
-| 0 | `phase-0-init.md` | opus | Yes (leaf) |
-| 1 | `${SCRIPT_DIR}/phase1-gather.py` | N/A | No (script) |
-| 2A | `phase-2a-testing-identifiers.md` | opus | Yes (leaf) |
-| 2B | `phase-2b-localization.md` | sonnet | Yes (leaf) |
-| 2C | `phase-2c-accessibility.md` | opus | Yes (leaf) |
-| 2D | `phase-2d-analytics.md` | sonnet | Yes (leaf) |
-| 3A | `phase-3a-location.md` | sonnet | Yes (leaf) |
-| 3C | `phase-3c-nested.md` | sonnet | Yes (leaf) |
-| 3H | `phase-3h-variant-config.md` | opus | Yes (leaf) |
-| 3D | `phase-3d-patterns.md` | opus | Yes (leaf) |
-| 4A | `phase-4a-configuration.md` | opus | Yes (leaf, COMPLEX only) |
-| 4B | `phase-4b-view.md` | opus | Yes (leaf) |
-| 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 | `phase-5a-viewinspector.md` | sonnet | Yes (leaf) |
-| 5B | `phase-5b-snapshot.md` | sonnet | Yes (leaf) |
-| 5C | `phase-5c-unit.md` | sonnet | Yes (leaf, if applicable) |
-| 6 | `phase-6-code-connect.md` | opus | Yes (leaf) |
-| 7 | `phase-7a-wiki-generate.md` | sonnet | Yes (leaf) |
-
-### Dispatch Prompt Template
-
-For each leaf subagent:
-
-```
-You are executing {Phase Name} of the Figma-to-SwiftUI workflow.
-
-## Context
-- Component: {componentName}
-- File Key: {fileKey}
-- Node ID: {nodeId}
-- Artifact Path: {artifactPath}
-- Component Location: {componentLocation}
-- GitHub Issue: {issueNumber} (omit if not available)
-
-## CRITICAL SPEC GATES (only if specs exist)
-{Concrete requirements extracted from specs  -  phrased as mandatory instructions, not a file reference}
-
-## Tool Restrictions
-{from dispatch table}
-
-## Your Instructions
-Read and STRICTLY FOLLOW your phase instructions gate-by-gate from this file:
-  {PHASE_DIR}/{instruction file}
-
-Read the return protocol from:
-  {REF_DIR}/halt-return-protocol.md
-
-## Reference Files
-{relevant reference files from the read-order table in figma-to-swiftui/SKILL.md}
-
-## Previous Phase Artifacts
-{artifact paths in read order  -  compact first}
-```
-
-### Phase Execution Flow
-
-**Phase 0**: Dispatch subagent → verify `IMPLEMENTATION_HISTORY.md` created.
-
-**Phase 1**: Run script:
-```bash
-python3 ${SCRIPT_DIR}/phase1-gather.py \
-  --file-key "{fileKey}" --node-id "{nodeId}" \
-  --artifact-path "{artifactPath}" --component-name "{componentName}"
-```
-If `COMPLETE_WITH_DEFERRED` → dispatch Phase 1 deferred resolution subagent.
-
-**Phase 2**:
-1. Pre-check: verify `pass1/_index.md`
-2. Normalize: check sublayers in `design_context_response.json`
-3. Registry lookup: `FigmaRegistryUtility utility-lookup --node-id '{nodeId}'`
-4. Wave 1 (parallel): dispatch 2A + 2B + 2C subagents simultaneously
-5. Wave 2: dispatch 2D subagent
-6. Finalize: `python3 ${SCRIPT_DIR}/phase2-finalize.py ...`
-
-**Phase 3**:
-1. Wave 1 (parallel): `python3 ${SCRIPT_DIR}/phase3-scripts.py wave1 ...` + dispatch 3A + 3C + 3H subagents
-2. Missing token resolution: check `pass3/02_token_mapping.md` for "⚠️ not found". If any → dispatch resolution subagent
-3. Wave 2: dispatch 3D subagent
-4. Wave 3: `python3 ${SCRIPT_DIR}/phase3-scripts.py 3g ...`
-5. Spec: `python3 ${SCRIPT_DIR}/phase3-scripts.py spec ...`
-6. Write `pass3/_index.md`
-
-**Phase 4**:
-1. Read `pass3/05_complexity.md` → SIMPLE or COMPLEX
-2. Prepare directory: `mkdir -p {componentLocation}`
-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
-
-**Phase 5**:
-1. Switch to local common: comment out remote URL in Package.swift, add local path
-2. Wave 1 (parallel): dispatch 5A + 5B subagents
-3. Wave 2 (conditional): dispatch 5C if component has model logic
-4. Run tests sequentially via `${SCRIPT_DIR}/run-uicomponents-tests.sh`
-5. Revert Package.swift to remote
-
-**Phase 6**: Dispatch subagent → run `${SCRIPT_DIR}/phase6-finalize.py` as safety net.
-
-**Phase 7**: Dispatch subagent.
-
----
-
-## STEP 3  -  Commit
-
-Run inline. Read `.instructions/figma/figma-iteration-commit/SKILL.md` for the full procedure:
-
-1. Rebase submodules to `iteration/develop` if on feature branch
-2. Build validation
-3. Commit to `iteration/develop` (common → uicomponents → wiki)
-4. Push with rebase-retry loop
-5. Clean up feature branches
-6. Issue housekeeping (comment, phase update, wiki link)
-7. Auto-unblock dependents
-
----
-
-## 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
-
-Output EXACTLY this block as your FINAL message. Nothing else after it.
-
-### On success (per component):
-
-```
-ORCHESTRATOR_RESULT:
-  status: COMPLETE
-  issueNumber: <N>
-  componentName: <name>
-  figmaUrl: <url>
-  nodeId: <nodeId>
-  jiraKey: <key>
-  commits:
-    common: <SHA>
-    uicomponents: <SHA>
-    wiki: <SHA>
-  phases: [0, 1, 2, 3, 4, 5, 6, 7]
-  testsRun: <count>
-  summary: <one-line>
-```
-
-### On failure:
-
-```
-ORCHESTRATOR_RESULT:
-  status: FAILED
-  issueNumber: <N>
-  componentName: <name>
-  failedPhase: <phase>
-  reason: <exact reason>
-  suggestion: <what to fix>
-```
-
-### On full iteration completion:
-
-```
-ORCHESTRATOR_RESULT:
-  status: ITERATION_COMPLETE
-  completed:
-    - { issue: <N>, component: <name>, commits: { common: <SHA>, uicomponents: <SHA>, wiki: <SHA> } }
-  failed:
-    - { issue: <N>, component: <name>, phase: <phase>, reason: <reason> }
-  remaining: <count>
-```
-
----
-
-## Error Handling
-
-- **No available issues**: Output ORCHESTRATOR_RESULT with status ITERATION_COMPLETE, empty completed/failed.
-- **Blocked issue**: Output FAILED.
-- **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.