@mmerterden/multi-agent-pipeline 11.2.0 → 11.3.1

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

@@ -1,216 +0,0 @@
----
-name: figma-commit
-description: Reviews a Figma component implementation, then creates feature branches across submodules, commits, pushes, and opens PRs. Delegates mobile-common conflict resolution to `COMMON_REBASE.md`.
----
-
-# /figma-commit  -  Review, Branch, Commit & Push
-
-## Purpose
-
-Reviews a Figma component implementation, then creates feature branches across submodules, commits, pushes, and opens PRs. Delegates mobile-common conflict resolution to `COMMON_REBASE.md`.
-
-## Parameters
-
-| Parameter | Required | Default | Description |
-|-----------|----------|---------|-------------|
-| `component-name` | Yes |  -  | PascalCase component name (e.g., `TurkishButton`) |
-| `--jira` | No | `{jira.projectKey}-124692` | Jira issue key |
-| `--gh` | No |  -  | GitHub issue number (for branch name construction) |
-
-```
-/figma-commit TurkishButton
-/figma-commit TurkishButton --jira {jira.projectKey}-99999 --gh 107
-```
-
----
-
-## Workflow
-
-### STEP 0  -  Resolve Parameters
-
-1. Parse `component-name`. Convert to kebab-case for branch name.
-2. Parse `--jira` or use default `{jira.projectKey}-124692`.
-3. Parse `--gh` if provided.
-4. `REPO_ROOT` = git repo root.
-5. Detect current branch:
-   ```bash
-   CURRENT_BRANCH=$(git -C "${REPO_ROOT}/{repos.components.path}" rev-parse --abbrev-ref HEAD)
-   ```
-6. **If already on a `feature/` branch** → use it as `BRANCH_NAME`. Extract `JIRA_ISSUE` from branch name (first segment after `feature/`).
-7. **If on `develop` or `iteration/develop`** → construct branch name:
-   - If `--gh` provided: look up issue to get node-id
-     ```bash
-     NODE_ID=$(gh issue view <GH> --repo ${GH_REPO} --json body --jq '.body' | grep -A1 '### Node ID' | tail -1)
-     NODE_UNDERSCORE=$(echo "${NODE_ID}" | tr '-' '_')
-     BRANCH_NAME="feature/${JIRA_ISSUE}-GH${GH}-N${NODE_UNDERSCORE}-${COMPONENT_KEBAB}"
-     ```
-   - If `--gh` not provided: use simple format
-     ```bash
-     BRANCH_NAME="feature/${JIRA_ISSUE}-${COMPONENT_KEBAB}"
-     ```
-8. Set remaining variables:
-   - `COMPONENT_PASCAL`, `COMPONENT_KEBAB`, `JIRA_ISSUE`, `BRANCH_NAME`
-   - `FIGMA_URL` = from component registry JSON (`confluence.page` field's sibling `figmaUrl`)
-   - `CONFLUENCE_IOS_URL` = from component registry JSON (`confluence.ios` field)
-
-### STEP 1  -  Code Review & Auto-Fix
-
-1. Read `.instructions/figma/figma-commit/REVIEW.md`.
-2. Run the full 13-point review checklist against the component.
-3. Print the review output table.
-4. **If violations found**: Auto-fix every fixable violation (magic numbers, missing identifiers, wrong patterns, missing imports, preview issues, etc.).
-5. After fixing, re-run the review to confirm.
-6. If fixes applied, build to verify:
-   ```bash
-   xcodebuild build -project "${REPO_ROOT}/{build.xcodeproj}" \
-       -scheme {build.scheme} -destination 'generic/platform=iOS' \
-       CODE_SIGNING_ALLOWED=NO -quiet
-   ```
-7. If unfixable violations remain → ask user.
-8. If PASS or WARN → proceed.
-
-### STEP 2  -  Detect Changes Per Repo
-
-`git status --porcelain` shows all tracked changes in short format  -  modified, added, deleted, untracked. Each line starts with a two-character status code (e.g., `M` modified, `??` untracked, `A` added, `D` deleted).
-
-```bash
-HAS_MAIN=$(cd "${REPO_ROOT}" && git status --porcelain | grep -v '^?? {repos.packagesContainer}/Packages/' | head -1)
-HAS_UICOMPONENTS=$(cd "${REPO_ROOT}/{repos.components.path}" && git status --porcelain | head -1)
-HAS_COMMON=$(cd "${REPO_ROOT}/{repos.common.path}" && git status --porcelain | head -1)
-```
-
-**Main repo PR decision**: Skip if only submodule pointer changes (no `.instructions/` or `.claude/skills/` modifications).
-
-### STEP 3  -  Common Submodule (if HAS_COMMON)
-
-**Read and follow `.instructions/figma/figma-commit/COMMON_REBASE.md`**  -  handles stash, branch, conflict resolution, regeneration, validation, commit, push, and PR for mobile-common.
-
-**Do NOT merge the PR**  -  only create it and push. Merging is done manually by the team.
-
-### STEP 4  -  UIComponents Submodule (if HAS_UICOMPONENTS)
-
-UIComponents rarely has conflicts (new files only). Simple flow:
-
-```bash
-UICOMP="${REPO_ROOT}/{repos.components.path}"
-
-# Stash
-cd "${UICOMP}"
-git stash push -u -m "figma-commit: ${COMPONENT_PASCAL} pre-branch stash"
-
-# Branch
-git checkout develop && git pull origin develop
-git checkout -b "${BRANCH_NAME}"
-
-# Pop (should apply cleanly)
-git stash pop
-
-# Commit
-git add -A
-git commit -m "$(cat <<'EOF'
-feat(uicomponents): [${JIRA_ISSUE}] add ${COMPONENT_PASCAL} component
-
-- Implement SwiftUI view with design tokens
-- Add configuration, modifiers, and previews
-- Add Code Connect and documentation
-- Add ViewInspector and snapshot tests
-
-Refs: ${JIRA_ISSUE}
-EOF
-)"
-
-# Push & PR (do NOT merge  -  PR only)
-git push -u origin "${BRANCH_NAME}"
-gh pr create --base develop \
-    --title "feat(uicomponents): [${JIRA_ISSUE}] add ${COMPONENT_PASCAL}" \
-    --body "$(cat <<'EOF'
-## Summary
-- Implement ${COMPONENT_PASCAL} SwiftUI component
-- Add Code Connect, FIGMA.md, tests
-
-## Visual Reference
-- **Figma:** ${FIGMA_URL}
-- **Confluence iOS:** ${CONFLUENCE_IOS_URL}
-
-## Test plan
-- [ ] ViewInspector tests pass
-- [ ] Snapshot tests pass
-- [ ] Build succeeds with remote dependencies
-
-Refs: ${JIRA_ISSUE}
-EOF
-)"
-```
-
-### STEP 5  -  Main Repo (if skill/instruction changes)
-
-```bash
-cd "${REPO_ROOT}"
-git stash push -u -m "figma-commit: ${COMPONENT_PASCAL} pre-branch stash"
-git checkout develop && git pull origin develop
-git checkout -b "${BRANCH_NAME}"
-git stash pop
-
-git add .instructions/ .claude/skills/
-git commit -m "$(cat <<'EOF'
-feat(skills): [${JIRA_ISSUE}] update skills for ${COMPONENT_PASCAL}
-
-- Update workflow instructions and scripts
-
-Refs: ${JIRA_ISSUE}
-EOF
-)"
-
-# Push & PR (do NOT merge  -  PR only)
-git push -u origin "${BRANCH_NAME}"
-gh pr create --base develop \
-    --title "feat(skills): [${JIRA_ISSUE}] skill updates for ${COMPONENT_PASCAL}" \
-    --body "## Summary
-- Update workflow skills and scripts
-
-Refs: ${JIRA_ISSUE}"
-```
-
-Skip this step entirely if no `.instructions/` or `.claude/skills/` changes.
-
-### STEP 6  -  Summary
-
-```
-## Commit Summary: ${COMPONENT_PASCAL}
-
-| Repo | Branch | PR |
-|------|--------|----|
-| common | ${BRANCH_NAME} | PR #N created / No changes |
-| uicomponents | ${BRANCH_NAME} | PR #N created / No changes |
-| main | ${BRANCH_NAME} | PR #N created / Skipped |
-
-Jira: ${JIRA_ISSUE}
-Review: PASS / WARN (N warnings)
-Validation: PASSED (N loc, N a11y, N testing keys)
-```
-
----
-
-## Execution Order
-
-Always: **common first → uicomponents → main repo**. Common PR must be merged before uicomponents PR (uicomponents depends on common via remote URL).
-
----
-
-## Error Handling
-
-- **Branch already exists**: Append `-v2`, `-v3`
-- **Push rejected**: Report error, do NOT force-push
-- **Submodule not on develop**: Warn user, ask confirmation
-- **Common conflicts**: Follow `COMMON_REBASE.md` section4
-- **Validation fails**: Fix before committing  -  NEVER skip
-
----
-
-## Notes
-
-- Always stash before branch creation
-- Submodules branched and pushed independently
-- Review step (Step 1) uses full REVIEW.md checklist  -  NOT optional
-- PRs are created but NOT merged  -  merging is a separate manual action
-- No AI attribution in commit messages  -  follow `GIT_COMMIT_CONVENTION.md`

package/pipeline/skills/figma-common/figma-component-confluence-sync/SKILL.md

@@ -1,223 +0,0 @@
----
-name: figma-component-confluence-sync
-description: Syncs component documentation from the GitHub Wiki (source of truth) to Confluence. Reads wiki markdown, converts to Confluence XHTML, uploads pages and assets. Requires VPN.
----
-
-# /figma-to-swift-ui-confluence-sync  -  Sync Wiki to Confluence
-
-## Purpose
-
-Syncs component documentation from the GitHub Wiki (source of truth) to Confluence. Reads wiki markdown, converts to Confluence XHTML, uploads pages and assets. Requires VPN.
-
-## Parameters
-
-| Parameter | Required | Description |
-|-----------|----------|-------------|
-| `<component-name>` or `<figma-url>` | Yes | Component to sync |
-| `--all` | No | Sync all components that have wiki docs |
-| `--dry-run` | No | Convert markdown to XHTML but skip upload |
-
-```
-/figma-to-swift-ui-confluence-sync ModalsTitle
-/figma-to-swift-ui-confluence-sync https://www.figma.com/design/...?node-id=2820-25995
-/figma-to-swift-ui-confluence-sync --all
-```
-
----
-
-## Constants
-
-```
-WIKI_ROOT       = {repos.wiki.path}
-CONFLUENCE_BASE = {confluence.baseUrl}
-CONFLUENCE_SPACE = DK
-PAGE_IDS_FILE   = .instructions/figma/figma-to-swiftui/scripts/confluence-page-ids.json
-PUBLISH_SCRIPT  = .instructions/figma/figma-to-swiftui/scripts/confluence-publish.py
-STATUS_SCRIPT   = .instructions/figma/figma-to-swiftui/scripts/confluence-component-status.py
-```
-
-### Authentication
-
-Confluence token from macOS Keychain:
-```bash
-CONFLUENCE_TOKEN=$("$HOME/.claude/lib/credential-store.sh" get \1 2>/dev/null)
-```
-
----
-
-## Gate 0: Resolve Component
-
-### If Figma URL provided:
-1. Extract `node-id`, run `FigmaRegistryUtility lookup --node-id`
-2. Get `suggestedComponentName`, `wikiCategory`
-
-### If component name provided:
-1. Search wiki for matching directory:
-```bash
-find ${WIKI_ROOT}/FigmaComponents -name "<ComponentName>.md" -type f
-```
-
-### Locate wiki source:
-```
-WIKI_MD = ${WIKI_ROOT}/FigmaComponents/{category}/{componentName}/{componentName}.md
-WIKI_ASSETS = ${WIKI_ROOT}/FigmaComponents/{category}/{componentName}/assets/
-```
-
-If wiki markdown doesn't exist → HALT: "No wiki documentation found. Run `/figma-to-swiftui phase-7` first."
-
----
-
-## Gate 1: VPN Check
-
-```bash
-curl -s --connect-timeout 5 "${CONFLUENCE_BASE}/rest/api/content?limit=1" \
-  -H "Authorization: Bearer ${CONFLUENCE_TOKEN}" \
-  -o /dev/null -w "%{http_code}"
-```
-
-If not `200` → HALT: "VPN not connected or Confluence token invalid."
-
----
-
-## Gate 2: Convert Markdown to XHTML
-
-Read the wiki markdown file. Read the conversion reference:
-```
-.instructions/figma/figma-to-swiftui/reference/wiki-to-confluence-mapping.md
-```
-
-### Split at `## iOS Implementation`
-
-- Everything **above** `## iOS Implementation` → `main.html`
-- Everything **from** `## iOS Implementation` **onward** → `ios.html`
-
-### Convert each part using the mapping rules:
-
-- Markdown headings → `<h2>`, `<h3>`
-- Markdown tables → `<table><tbody>...`
-- Wiki image syntax `[[/path/assets/file.png|alt]]` → `<ac:image><ri:attachment ri:filename="file.png"/></ac:image>`
-- Code blocks → `<ac:structured-macro ac:name="code">`
-- Wiki links `[[Name]]` → `<ac:link><ri:page ri:content-title="Name"/>`
-- External links → `<a href="...">`
-
-### Prepend to main.html:
-- TOC macro
-
-### Prepend to ios.html:
-- Back-link to main page
-
-### Write output:
-Create a temp directory for the XHTML output:
-```bash
-TEMP_DIR=$(mktemp -d)
-mkdir -p ${TEMP_DIR}/assets
-```
-
-Write `${TEMP_DIR}/main.html` and `${TEMP_DIR}/ios.html`.
-Copy `${WIKI_ASSETS}/*` to `${TEMP_DIR}/assets/`.
-
-If `--dry-run`: print paths and stop.
-
----
-
-## Gate 3: Validate XHTML
-
-```bash
-python3 .instructions/figma/figma-to-swiftui/scripts/validate-phase7a.py \
-    --confluence-path "${TEMP_DIR}" \
-    --component-name "{ComponentName}" \
-    --mode confluence
-```
-
-If FAIL → fix conversion issues and retry.
-
----
-
-## Gate 4: Upload to Confluence
-
-### Resolve parent page
-
-1. Check registry for existing Confluence URLs (update case)
-2. Otherwise, lookup from `confluence-page-ids.json` by category path
-3. Fallback: "Figma Components" root page
-
-### Publish
-
-```bash
-python3 ${PUBLISH_SCRIPT} \
-    --component "{ComponentName}" \
-    --artifact-path "${TEMP_DIR}" \
-    --node-id "{nodeId}" \
-    --parent-page-id "{parentPageId}" \
-    --space "${CONFLUENCE_SPACE}"
-```
-
-This creates/updates:
-- Main page: `{ComponentName}`
-- iOS sub-page: `{ComponentName} - iOS`
-- Android placeholder: `{ComponentName} - Android`
-- Attachments: all images from `assets/`
-
-### Update registry
-
-The publish script updates `{nodeId}.json` with Confluence URLs.
-
----
-
-## Gate 5: Refresh Status Dashboard
-
-```bash
-python3 ${STATUS_SCRIPT}
-```
-
-Updates the global Component Implementation Status page on Confluence.
-
----
-
-## Registry flag ownership (architecture-update)
-
-This skill is a **downstream mirror** of the GitHub Wiki. It **does not** own the `status.ios.wiki` flag in the component registry  -  that flag is set green by `/figma-to-swift-ui-wiki` via `scripts/phase7-finalize.py`, which is upstream of this sync. Confluence URLs are written into `{nodeId}.json.confluence.ios` by the publish script (Gate 4) so downstream readers can link out, but the 4-flag status block is untouched here.
-
-If you run this skill and the `wiki` flag is still gray/yellow, run `/figma-to-swift-ui-wiki` first  -  that's what owns the flag.
-
----
-
-## `--all` Mode
-
-When `--all` is passed:
-
-1. Find all component markdown files:
-```bash
-find ${WIKI_ROOT}/FigmaComponents -name "*.md" -not -name "ComponentImplementationStatus.md" -not -name "_Sidebar.md" -type f
-```
-
-2. For each component, run Gates 2-5 sequentially.
-3. Run status dashboard refresh once at the end (not per component).
-4. Print summary table:
-
-```markdown
-| Component | Status | Confluence URL |
-|-----------|--------|----------------|
-| Checkbox  | Synced | {confluence.baseUrl}/display/DK/Checkbox |
-| Price     | Synced | {confluence.baseUrl}/display/DK/Price |
-| ...       | ...    | ...            |
-```
-
----
-
-## Cleanup
-
-```bash
-rm -rf ${TEMP_DIR}
-```
-
----
-
-## Error Handling
-
-- **VPN not connected**: HALT with VPN instructions.
-- **Wiki markdown not found**: HALT  -  run Phase 7 first.
-- **Confluence token missing**: Prompt user to add to keychain.
-- **XHTML validation failed**: Show violations, retry conversion.
-- **Upload failed (401/403)**: Token expired  -  prompt refresh.
-- **Upload failed (404)**: Wrong parent page ID  -  check confluence-page-ids.json.

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

@@ -1,251 +0,0 @@
----
-name: figma-component-start
-description: Reads a GitHub Issue, extracts component metadata, creates feature branches from `develop` (main repo) / `iteration/develop` (submodules), and checks them out locally. Prepares the workspace to begin implementation.
----
-
-# /figma-to-swift-ui-start  -  Start Implementation from GitHub Issue
-
-## Purpose
-
-Reads a GitHub Issue, extracts component metadata, creates feature branches from `develop` (main repo) / `iteration/develop` (submodules), and checks them out locally. Prepares the workspace to begin implementation.
-
-## Parameters
-
-| Parameter | Required | Default | Description |
-|-----------|----------|---------|-------------|
-| `<issue-number>` | Yes |  -  | GitHub issue number from uicomponents repo |
-
-```
-/figma-to-swift-ui-start #107
-/figma-to-swift-ui-start 107
-```
-
----
-
-## Constants
-
-```
-REPO_ROOT       = git repo root (auto-detect)
-GH_REPO         = {github.componentsRepo}
-BASE_BRANCH     = develop                # main repo; submodules use iteration/develop
-```
-
-### Submodule Paths
-
-```
-MAIN_REPO       = ${REPO_ROOT}
-COMMON          = ${REPO_ROOT}/{repos.common.path}
-UICOMPONENTS    = ${REPO_ROOT}/{repos.components.path}
-WIKI            = ${REPO_ROOT}/{repos.wiki.path}
-```
-
----
-
-## 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
-- **Acceptance Criteria**  -  from `### Acceptance Criteria` section (if not `_No response_`)
-
-Derive:
-- `COMPONENT_PASCAL` = Component Name (e.g., `ModalsTitle`)
-- `COMPONENT_KEBAB` = kebab-case (e.g., `modals-title`)
-- `NODE_UNDERSCORE` = node-id with `-` replaced by `_` (e.g., `2820-25995` → `2820_25995`)
-- `BRANCH_NAME` = `feature/GH${N}-N${NODE_UNDERSCORE}-${COMPONENT_KEBAB}`
-
-Print:
-
-```
--------------------------------------------
-  Issue:      #<N>
-  Component:  <COMPONENT_PASCAL>
-  Node ID:    <NODE_ID>
-  Branch:     feature/GH<N>-N<NODE_UNDERSCORE>-<COMPONENT_KEBAB>
-  Base:       develop (main repo) / iteration/develop (submodules)
--------------------------------------------
-```
-
----
-
-## STEP 1  -  Fetch Latest
-
-Ensure all repos are up to date with remote:
-
-```bash
-cd ${MAIN_REPO}
-git fetch origin
-git checkout develop
-git pull --no-recurse-submodules origin develop
-
-cd ${COMMON}
-git fetch origin
-git checkout iteration/develop
-git pull origin iteration/develop
-
-cd ${UICOMPONENTS}
-git fetch origin
-git checkout iteration/develop
-git pull origin iteration/develop
-```
-
----
-
-## STEP 2  -  Create Feature Branches
-
-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)
-cd ${COMMON}
-git checkout -b ${BRANCH_NAME}
-
-# UIComponents (SwiftUI views, tests, snapshots)
-cd ${UICOMPONENTS}
-git checkout -b ${BRANCH_NAME}
-```
-
-Wiki submodule stays on `master`  -  wiki changes are committed directly.
-
----
-
-## STEP 3  -  Registry Lookup
-
-```bash
-cd ${COMMON}
-.build/debug/FigmaRegistryUtility lookup --node-id <NODE_ID>
-```
-
-Collect:
-- `suggestedComponentLocation`  -  where the Swift files will go
-- `suggestedArtifactPath`  -  where implementation artifacts go
-
-Print:
-
-```
-Component Location: <suggestedComponentLocation>
-Artifact Path:      <suggestedArtifactPath>
-```
-
----
-
-## 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.
-
-```bash
-mkdir -p ${REPO_ROOT}/${suggestedArtifactPath}/pass0
-```
-
-Write `${suggestedArtifactPath}/pass0/specs.md`:
-
-```markdown
-# Implementation Specs: {ComponentName}
-
-## Source
-- Issue: #{N}
-- Figma: {FIGMA_URL}
-
-## Acceptance Criteria
-
-{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}
-```
-
-If no acceptance criteria → skip this step. No file created.
-
----
-
-## STEP 4  -  Assign to Me
-
-Assign the GitHub issue to the current user:
-
-```bash
-gh issue edit <N> --repo ${GH_REPO} --add-assignee @me
-```
-
----
-
-## 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
-Develop is how the board reflects that someone has started working on
-it. If you skip this step, the issue visually stays in the Todo column
-even though work has started.
-
-Set the issue phase to "Implementation" and status to "In Develop" on the Projects V2 board:
-
-```bash
-# 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
-# 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')
-
-# Set Status = In Develop (option id: bc6c45f7)
-gh api graphql -f query='mutation { updateProjectV2ItemFieldValue(input: { projectId: "{github.projectV2Id}", itemId: "'"$ITEM_ID"'", fieldId: "{github.projectV2Fields.status}", value: { singleSelectOptionId: "bc6c45f7" } }) { projectV2Item { id } } }'
-
-# Set Phase = Implementation (option id: 0577dcda)
-gh api graphql -f query='mutation { updateProjectV2ItemFieldValue(input: { projectId: "{github.projectV2Id}", itemId: "'"$ITEM_ID"'", fieldId: "{github.projectV2Fields.phase}", value: { singleSelectOptionId: "0577dcda" } }) { projectV2Item { id } } }'
-```
-
-### Verify the move landed
-
-After the mutations return, confirm Status=In Develop is set (this catches
-silent VALIDATION errors from stale option IDs):
-
-```bash
-gh api graphql -f query='{ node(id: "'"$ITEM_ID"'") { ... on ProjectV2Item { fieldValues(first: 20) { nodes { ... on ProjectV2ItemFieldSingleSelectValue { field { ... on ProjectV2SingleSelectField { name } } name } } } } } }' \
-  --jq '.data.node.fieldValues.nodes[] | select(.field.name == "Status") | .name'
-```
-
-Expected output: `In Develop`. If you see anything else (or empty),
-re-fetch the current option IDs and retry  -  do NOT proceed to implementation
-without the Status set correctly.
-
----
-
-## STEP 6  -  Summary
-
-Print:
-
-```markdown
-Ready to implement:
-
-| Field | Value |
-|-------|-------|
-| Issue | [#N](url) |
-| Component | <COMPONENT_PASCAL> |
-| Branch | `<BRANCH_NAME>` |
-| Base | `develop` (main repo) / `iteration/develop` (submodules) |
-| Component Location | <suggestedComponentLocation> |
-| Artifact Path | <suggestedArtifactPath> |
-
-Next: `/figma <figma-url>` to run the implementation pipeline.
-```
-
----
-
-## Error Handling
-
-- **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.
-- **Main repo not on develop**: Fetch and checkout automatically.
-- **Submodule not on iteration/develop**: Fetch and checkout automatically.