@mmerterden/multi-agent-pipeline 11.2.0 → 11.3.1

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

@@ -1,208 +0,0 @@
----
-name: figma-iterate
-description: Picks the next available component issue and runs the full pipeline end-to-end: start → implement → commit. Loops until no more issues are available or the user stops it.
----
-
-# /figma-iterate  -  Automated Implementation Pipeline
-
-## Purpose
-
-Picks the next available component issue and runs the full pipeline end-to-end: start → implement → commit. Loops until no more issues are available or the user stops it.
-
-## Parameters
-
-| Parameter | Required | Default | Description |
-|-----------|----------|---------|-------------|
-| `[#N]` | No |  -  | Specific issue to implement. If omitted, auto-picks next available. |
-| `--count <N>` | No | all | Number of components to implement before stopping. |
-
-```
-/figma-iterate              ← auto-pick, loop until no more issues
-/figma-iterate --count 3    ← auto-pick, implement 3 components then stop
-/figma-iterate --count 1    ← same as implementing one component
-/figma-iterate #107         ← implement specific issue only
-```
-
----
-
-## Constants
-
-```
-GH_REPO = {github.componentsRepo}
-```
-
----
-
-## STEP 0  -  Pick Next Issue
-
-### If issue number provided:
-
-Use that issue. Verify it's open and not blocked:
-
-```bash
-gh issue view <N> --repo ${GH_REPO} --json number,title,state,labels --jq '{number, title, state, labels: [.labels[].name]}'
-```
-
-If closed → HALT: "Issue #N is already closed."
-If has `blocked` label → HALT: "Issue #N is blocked. Unblock first with `/figma-issue unblock #N`."
-
-### If no issue number  -  auto-pick:
-
-Find the next available issue: open, `component` label, not `blocked`, not assigned.
-
-```bash
-gh issue list --repo ${GH_REPO} \
-  --state open \
-  --label component \
-  --json number,title,labels,assignees \
-  --jq '[.[] | select(
-    (.labels | map(.name) | index("blocked") | not) and
-    (.assignees | length == 0)
-  )] | sort_by(.number) | .[0]'
-```
-
-If no issue found → print "No available issues. All are either assigned, blocked, or closed." and exit.
-
-Print:
-
-```
-Next available issue:
-  #<N>  -  <title>
-```
-
-Print and STOP. Wait for user confirmation or "skip" to pick next.
-
----
-
-## STEP 1  -  Start (`/figma-to-swift-ui-start`)
-
-Run the start skill logic inline (not as a sub-skill invocation):
-
-1. Read issue #N → get component name, Figma URL, node ID, Jira key
-2. Fetch + checkout `develop` on main, `iteration/develop` on common, uicomponents
-3. Create feature branches (only if not already on one)
-4. Registry lookup → component location + artifact path
-5. Assign to me (GitHub + Jira)
-6. Set issue to In Progress on Projects V2
-
-Print:
-
-```
-Started: <ComponentName> (#N)
-Branch:  feature/<JIRA>-GH<N>-N<NODE>-<component>
-```
-
----
-
-## required PRE-READ
-
-Before dispatching any phase subagent, read:
-  .instructions/figma/figma-to-swiftui/reference/orchestrator-discipline.md
-
-These 6 rules govern orchestrator behavior. Violations have caused repeated failures. Follow them strictly.
-
----
-
-## STEP 2  -  Implement (Phases 0-7)
-
-Extract Figma URL from the issue body.
-
-**Orchestrate inline**  -  run each phase by dispatching leaf-phase subagents and scripts directly. Read the full orchestration logic from `.instructions/figma/figma-cli-iterate/SKILL.md` STEP 2.
-
-**NEVER dispatch multi-phase meta-skills as subagents:**
-- `/figma-to-swiftui`, `/figma-to-swift-ui-implement`, `/figma-to-swift-ui-test`, `/figma-to-swift-ui-code-connect`, `/figma-to-swift-ui-wiki`
-
-Instead, dispatch individual phase instruction files (e.g., `phase-2a-testing-identifiers.md`, `phase-4b-view.md`) as leaf subagents.
-
-**Spec injection (Option A):** If `{artifactPath}/pass0/specs.md` exists, read specs and inject concrete requirements into each subagent dispatch prompt as CRITICAL SPEC GATES  -  not as a sidecar file reference.
-
-Phases 0-7:
-- Phase 0: Init (subagent, leaf)
-- Phase 1: Data Gathering (script)
-- Phase 2: Derived Artifacts (parallel waves of leaf subagents + finalize script)
-- Phase 3: Analysis (parallel waves of leaf subagents + scripts)
-- Phase 4: Implementation (parallel waves of leaf subagents + validate + build)
-- Phase 5: Testing (parallel leaf subagents + test execution)
-- Phase 6: Code Connect (leaf subagent)
-- Phase 7: Wiki Documentation (leaf subagent)
-
-If any phase HALTs → print the halt reason, ask user to resolve, then resume.
-
----
-
-## STEP 3  -  Commit (`/figma-iteration-commit`)
-
-Run the iteration commit logic inline:
-
-1. Validate  -  build, tests, key sync, review + auto-fix
-2. Commit to `iteration/develop` (common → uicomponents → wiki) + PR to `develop` (main, if needed)
-3. Push each
-4. Comment on issue with commit SHAs
-5. Update issue phase
-6. Auto-unblock dependents
-
-Print:
-
-```
-Committed: <ComponentName> (#N)
-  common:       <SHA>
-  uicomponents: <SHA>
-  wiki:         <SHA>
-```
-
----
-
-## STEP 4  -  Loop
-
-If specific issue `#N` was provided → print summary and exit (single run).
-
-If `--count` was provided → decrement counter. If counter reaches 0 → print summary and exit.
-
-Otherwise → go back to STEP 0, auto-pick next available issue.
-
-Before picking next, print:
-
-```
-═══════════════════════════════════════
-  Completed: <ComponentName> (#N)
-  Moving to next available issue...
-═══════════════════════════════════════
-```
-
-### Loop exit conditions:
-
-- No more available issues → print "All available issues completed." and exit.
-- `--count` reached → print summary and exit.
-- User interrupts → exit gracefully.
-- 3 consecutive HALTs → print "Multiple failures. Stopping iteration." and exit.
-
----
-
-## STEP 5  -  Final Summary
-
-Print at the end of the loop:
-
-```
-Iteration Complete
-
-| # | Issue | Component | Status |
-|---|-------|-----------|--------|
-| 1 | #107  | ModalsTitle | Committed |
-| 2 | #108  | ModalsBodyList | Committed |
-| 3 | #109  | LogoStopover | HALT (Phase 3) |
-
-Completed: 2
-Halted: 1
-Remaining: N open issues
-```
-
----
-
-## Error Handling
-
-- **No available issues**: Exit cleanly with message.
-- **Blocked issue (manual pick)**: HALT  -  don't implement blocked components.
-- **Phase HALT**: Show reason, ask user. If resolved → resume. If skipped → mark issue, move to next.
-- **Build/test failure in commit**: HALT  -  don't push broken code.
-- **3 consecutive HALTs**: Stop iteration to prevent infinite failure loops.
-- **Submodules not on iteration/develop**: Auto-checkout before starting.