ios-swift-orchestrator

Route iOS/Swift tasks to appropriate sub-skills using a routing guide.

1|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/oozoofrog/codex-skills --skill ios-swift-orchestrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ios-swift-orchestrator
Source: https://github.com/oozoofrog/codex-skills/tree/main/ios-swift-orchestrator
Command: npx skills add https://github.com/oozoofrog/codex-skills --skill ios-swift-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Route iOS/Swift tasks between multi-agent delivery workflow and deep Swift domain expertise. Use when Codex needs a single entry point to decide whether to apply ios-multi-agent-dev, swift-master, or both for iOS bug fixes, features, refactors, SwiftUI/SwiftData/concurrency issues, Swift 6 migrations, release-sensitive changes, or code review.

Core Features & Use Cases

  • Orchestrates routing between ios-multi-agent-dev, swift-master, and claude-code-bridge for iOS tasks.
  • Enforces serial execution by default and escalates to the next sub-skill only after verification.
  • References routing guide to determine task type, risk, and the optimal sub-skill path for bug fixes, migrations, or reviews.
  • Supports optional sub-skill chaining when multi-skill expertise is required.

Quick Start

Route this iOS/Swift task through the appropriate sub-skill by first reading the routing guide and selecting a single main sub-skill to activate.

Frequently Asked Questions about ios-swift-orchestrator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route iOS Swift tasks between multi-agent workflows and domain expertise?

Route iOS Swift tasks by reading a routing guide that evaluates task type and risk to activate the correct sub-skill, such as ios-multi-agent-dev or swift-master. It enforces serial execution by default and escalates only after verification.

What is the best way to orchestrate a Swift 6 migration across multiple expert skills?

Orchestrate a Swift 6 migration by using a routing guide to select a single main sub-skill, enforcing sequential activation with a final verification step. Optional sub-skill chaining supports multi-skill expertise when required for complex migrations.

Does this routing approach support parallel execution for iOS bug fixes and refactors?

No, this routing approach enforces serial execution by default for iOS bug fixes and refactors. It escalates to the next sub-skill only after verifying the previous step, ensuring safe sequential activation across the delivery workflow.

Can I use this orchestrator for SwiftUI and SwiftData concurrency code reviews?

Yes, you can use this orchestrator for SwiftUI and SwiftData concurrency code reviews. It routes the task between multi-agent delivery workflow and deep Swift domain expertise to determine the optimal combination of sub-skills.

When should I chain multiple sub-skills for an iOS feature delivery?

Chain multiple sub-skills for an iOS feature delivery when multi-skill expertise is explicitly required. The orchestrator applies optional sub-skill chaining after checking routing rules to determine task type, risk, and the optimal path.

Why does my iOS task require explicit activation of sub-skills before execution?

Your iOS task requires explicit activation of sub-skills to enforce sequential activation with a final verification step. This ensures the routing guide determines the correct combination of ios-multi-agent-dev, swift-master, or claude-code-bridge before proceeding.