orchestrator-tech-lead

Generate implementation instructions for Android, iOS, and Web orchestrator projects.

29|3|Updated Dec 10, 2025
One-click install
npx skills add https://github.com/parallax-ai-llc/claude-orchestrator --skill orchestrator-tech-lead
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestrator-tech-lead
Source: https://github.com/parallax-ai-llc/claude-orchestrator/tree/main/src/skills/orchestrator-tech-lead
Command: npx skills add https://github.com/parallax-ai-llc/claude-orchestrator --skill orchestrator-tech-lead

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill equips Tech Leads to translate planning documents and design specs into clear, implementable instructions for developers, reducing ambiguity and rework.

Core Features & Use Cases

  • Implementation Planning: Outline architecture, files, and patterns for the task.
  • Step-by-step Instructions: Provide detailed, testable steps with acceptance criteria.
  • Token Referencing: Reference Designer's design tokens for UI implementation.

Quick Start

Convert a planning document into a task assignment with specific files to create, target platform, and acceptance criteria.

Frequently Asked Questions about orchestrator-tech-lead

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

FAQPage Schema
How do I convert a design specification into step-by-step developer instructions?

Convert design specs into actionable developer instructions by outlining platform-specific architecture, required files, design token references, and acceptance criteria. This reduces ambiguity and rework by giving developers a clear roadmap for implementation across Android, iOS, or Web projects.

What should I include when planning Android, iOS, or Web implementation tasks?

Include platform-specific architecture patterns—Android MVVM with ViewModel and StateFlow, iOS MVVM with ObservableObject and SwiftUI, or Web component-based TypeScript—along with file delineation, design token usage, error handling strategies, testing criteria, and explicit orchestrator integration points.

Can I reference design tokens in my implementation instructions?

Yes. Design token referencing lets you tie UI implementation directly to Designer specifications, ensuring consistency across the project and reducing the gap between design and code.

How do I break down a planning document into testable developer tasks?

Structure planning documents into discrete tasks by specifying which files to create, target platform, architecture decisions, and measurable acceptance criteria. Each task becomes independently testable and traceable to functional and technical requirements.

Does this approach work for cross-platform projects?

Yes. The Skill supports Android, iOS, and Web projects, adapting instructions to each platform's architecture patterns, frameworks, and integration requirements while maintaining consistent task structure and acceptance criteria.

What's the best way to ensure developers understand integration points with the orchestrator?

Explicitly document orchestrator integration points—where components connect, data flows, and state transitions occur—within each task. This clarity prevents implementation divergence and reduces integration rework downstream.

Related Skills