orchestrator

Routes multi-domain development tasks to the appropriate specialist skills.

2|Updated Jun 8, 2026
One-click install
npx skills add https://github.com/lunaticwithaduck/easytech3d --skill orchestrator-lunaticwithaduck
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: orchestrator
Source: https://github.com/lunaticwithaduck/easytech3d/tree/main/.claude/skills/orchestrator
Command: npx skills add https://github.com/lunaticwithaduck/easytech3d --skill orchestrator-lunaticwithaduck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a task spans multiple domains like frontend, backend, payments, and deployment, it is hard to know which skills to combine and in what order. This Skill acts as a meta-router that maps any project or feature request to the right specialist skills. ## Core Features & Use Cases - Task-to-Skill Routing: A decision tree and keyword lookup table map requests like "build a SaaS" or "fix a bug" to concrete skill combinations. - Multi-Skill Workflows: Predefined sequences for new features, bug fixes, and integrations, from user story through deployment and analytics. - SaaS Blueprint: A phased build plan (foundation, core product, monetization, scale) assigning skills to each deliverable. - Use Case: You ask "help me build an e-commerce store" and receive a routed plan combining nextjs, payments, email, seo, and analytics skills in the correct order. ## Quick Start Ask the orchestrator to plan which skills you need to build a full-stack SaaS product from scratch.

Frequently Asked Questions about orchestrator

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

FAQPage Schema
How do I know which skills I need to build an app?▼

Describe what you want to build and the orchestrator matches it against a decision tree and keyword table. For example, an e-commerce store routes to nextjs, payments, email, seo, and analytics skills.

What skills do I need for a SaaS product?▼

The SaaS blueprint covers four phases: foundation (nextjs, database, backend, security), core product (react, testing, devops), monetization (payments, email, analytics, seo), and scale (compliance, integrations, documentation).

How are cross-cutting concerns like authentication split between skills?▼

The orchestrator defines ownership matrices. For auth, backend owns JWT and OAuth flows, security owns hashing and rate limiting, react owns login forms, and nextjs owns middleware.

What happens when a task does not fit any existing skill?▼

The escalation path first checks the keyword table and cross-cutting concern matrices. If the domain is genuinely new, the create-skill skill scaffolds a new specialist skill for it.

When should I use the orchestrator instead of a specialist skill directly?▼

Use the orchestrator when a task spans multiple domains or you are unsure which skill applies. For a single-domain task like writing a Prisma migration, invoke the database skill directly.