「orchestrator」の検索結果

This skill should be used when designing or implementing systems with multiple AI agents that coordinate to accomplish tasks. Triggers on "multi-agent", "orchestrator", "sub-agent", "coordination", "delegation", "parallel agents", "sequential pipeline", "fan-out", "map-reduce", "spawn agents", "agent hierarchy".

日本語の概要は準備中です。原文の説明を表示しています。

Expert guide for Backend.AI distributed computing platform. Automatically activates when users ask about: - Backend.AI architecture, components (Manager, Agent, Storage Proxy, Webserver, App Proxy) - Features (session scheduling, Sokovan orchestrator, multi-tenancy, resource allocation) - APIs (REST, GraphQL), authentication, RBAC authorization - Container runtime (kernels, jail sandbox, hook library, virtual folders) - Accelerator support (CUDA, ROCm, TPU, NPU, Graphcore IPU) - Client SDKs (Python, Java, JavaScript, PHP) - Setup, requirements (Python 3.13+, Docker, PostgreSQL, Redis, etcd) - How WebUI connects to/interacts with Backend.AI backend - Plugin interfaces, development setup, infrastructure Use when user mentions "Backend.AI", "backend.ai", "Sokovan", component names, or asks about the backend platform this WebUI connects to. allowed-tools: WebFetch, Read

日本語の概要は準備中です。原文の説明を表示しています。

Orchestrates Spec Driven Development by coordinating spec, plan, and task skills. Use when running the full speckit workflow from spec to implementation.

日本語の概要は準備中です。原文の説明を表示しています。

Manages parent/child agent relationships with task delegation and result aggregation. Supports sequential chains, parallel fans, conditional routing, retry logic, timeout handling, and YAML-based visual workflow definition.

日本語の概要は準備中です。原文の説明を表示しています。

Main application building orchestrator. Creates full-stack applications from natural language requests. Determines project type, selects tech stack, coordinates agents.

日本語の概要は準備中です。原文の説明を表示しています。

A meta-skill that understands task requirements, dynamically selects appropriate skills, tracks successful skill combinations using agent-memory-mcp, and prevents skill overuse for simple tasks.

日本語の概要は準備中です。原文の説明を表示しています。

Delegate coding tasks to the Google Antigravity CLI (`agy`) only when the user explicitly requests it, while the orchestrator retains review and landing responsibility.

日本語の概要は準備中です。原文の説明を表示しています。

Delegate coding tasks to Aider (`aider`) only when the user explicitly requests it, while the orchestrator retains review and landing responsibility.

日本語の概要は準備中です。原文の説明を表示しています。

Meta-skill que orquestra todos os agentes do ecossistema. Scan automatico de skills, match por capacidades, coordenacao de workflows multi-skill e registry management.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention.

日本語の概要は準備中です。原文の説明を表示しています。

Main agent orchestrator that coordinates a specialized squad of agents

日本語の概要は準備中です。原文の説明を表示しています。

Use when coordinating complex tasks across multiple AI agents with a centralized handoff document for planning, execution tracking, and feedback fusion.

日本語の概要は準備中です。原文の説明を表示しています。

Full Stock Analysis Orchestrator — launches 5 parallel subagents for comprehensive multi-dimensional stock analysis with composite Trade Score

日本語の概要は準備中です。原文の説明を表示しています。

Full Ad Strategy Orchestrator. Launches 5 parallel subagents to build a complete advertising strategy from a single URL — audience personas, creative concepts, funnel architecture, competitive intelligence, and budget allocation. Produces a composite Ad Readiness Score (0-100) with a unified, client-ready strategy report.

日本語の概要は準備中です。原文の説明を表示しています。

Launch and watch Guaardvark's Swarm Orchestrator: parallel coding agents, each in its own git worktree, working a markdown plan and merging back deterministically. Use when the user wants several agents on one codebase at once, says "swarm this", or asks about a running swarm, worktrees, or merge status.

日本語の概要は準備中です。原文の説明を表示しています。

Dead code removal via parallel scanning, reference verification, batch execution, and atomic commits. You are the ORCHESTRATOR — you scan, verify, batch, then delegate ALL removals.

日本語の概要は準備中です。原文の説明を表示しています。

Dynamic MCP server discovery and code-mode execution via central registry. Use for multiple MCP integrations, tool discovery, progressive disclosure, or encountering MCP context bloat, changing server sets, large tool sets.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user asks to run or continue an autonomous build: turn a goal into an approved plan, dispatch implementation and review agents, and finish with one pull request. The Lead is a provider-neutral orchestrator that makes decisions but never writes code, edits files, runs commands, or reviews its own work.

日本語の概要は準備中です。原文の説明を表示しています。

The Auto 档 scenario — a soft-plan orchestrator for a complete fundamental equity research thesis: understand → financials → valuation → synthesize. The body is a soft plan (stages), not a rigid DAG; correctness is enforced by each referenced skill's own requires: preconditions, never by this plan's rigidity (Q2).

日本語の概要は準備中です。原文の説明を表示しています。

Launches 5 parallel AI agents to produce a comprehensive property analysis with composite Property Score (0-100), investment grade, and actionable recommendations

日本語の概要は準備中です。原文の説明を表示しています。

Symfony UX frontend stack -- decision tree and orchestrator for choosing between Stimulus, Turbo, TwigComponent, LiveComponent, UX Icons, and UX Map. Use when the user is unsure which tool fits, wants to combine multiple UX packages, or asks a general frontend architecture question in Symfony. Also trigger when the user asks "which UX package should I use", "how to make this interactive", "should I use Stimulus or LiveComponent", "how to structure my Symfony frontend", "what is the difference between Turbo and LiveComponent", "should this be a Frame or a LiveComponent", "how do these UX packages work together", "what is the Symfony way to do frontend". Do NOT trigger when the user clearly names a specific tool (stimulus, turbo, twig-component, live-component, ux-icons, ux-map) -- defer to the specialized skill instead.

日本語の概要は準備中です。原文の説明を表示しています。

Plan-driven orchestrator. Reads plan.json (from /blueprint) or requirements.md, then dispatches workers to build the system. Use when: "/execute", "execute", "plan 실행", "blueprint 실행"

日本語の概要は準備中です。原文の説明を表示しています。

Recon-first browser automation. Orchestrator explores the site first via chromux, saves a guide file with insights, then delegates execution to browser-explorer agent. Use when: "/browser-work", "브라우저 작업", "사이트에서 해줘", "웹에서 해줘", "LinkedIn에서", "크롬으로", "browser task", "automate this site".

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user wants a short, design-led motion graphic where motion is the message: kinetic typography, stat or number count-up, chart/data-viz hit, logo sting, brand lockup, lower-third, callout, social overlay, animated headline/tweet/news item, motion poster, or quick captured-page highlight. Usually under 10s and up to ~30s, with no live-action subject. Can render to MP4 or transparent overlay. Not for longer, multi-scene, or brand-reel pieces (use general-video), topic explainers (faceless-explainer), PR videos (pr-to-video), or captions on existing footage (embedded-captions). When unsure whether it's a quick motion-first piece or a longer treatment, see /hyperframes.

日本語の概要は準備中です。原文の説明を表示しています。