implement-orchestrator

Coordinate Sonnet agents to implement designs across multiple subsystems.

7|4|Updated Mar 2, 2026

Search Tags:#automation #design #agents #code-generation #orchestrate #sonnet

Ready to run

npx skills add https://github.com/nklisch/skills --skill implement-orchestrator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implement-orchestrator
Source: https://github.com/nklisch/skills/tree/main/plugins/workflow/skills/implement-orchestrator
Command: npx skills add https://github.com/nklisch/skills --skill implement-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrate end-to-end implementation by grounding design documents, project conventions, and the codebase, then coordinate multiple Sonnet agents to translate plans into production-ready code.

Core Features & Use Cases

Grounding: reads design docs, CLAUDE.md, and existing code to align implementation work.
Task planning: decomposes the design into agent-sized work units with clear dependencies.
Parallel execution: spawns Sonnet agents to work on independent subsystems, tracks progress, and supports cross-session resumes.

Quick Start

Provide the design document and start the orchestration to spawn Sonnet agents that implement the plan.

Frequently Asked Questions about implement-orchestrator

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

FAQPage Schema

How do I automate code generation for large software designs with multiple subsystems?▼

Automating code generation for large designs is handled by grounding project docs and spawning Sonnet agents to parallelize implementation across subsystems. The orchestrator decomposes designs into agent-sized work units, tracks dependencies, and ensures production-ready code aligned with project conventions.

What is agent orchestration for design-to-code implementation?▼

Agent orchestration for design-to-code implementation coordinates multiple Sonnet agents to translate design documents into production-ready code. It works by grounding the design, planning tasks with clear dependencies, and executing parallel work units to ensure alignment with project conventions.

When do I need to orchestrate multiple agents for code generation?▼

Orchestrating multiple agents for code generation is needed for large designs with 20+ files or multiple subsystems. It requires careful dependency management and progress tracking to parallelize implementation effectively and ensure verified builds.

Can I use orchestration to align generated code with existing project conventions?▼

Orchestration aligns generated code with existing project conventions by grounding the implementation in design docs, CLAUDE.md, and the codebase. Sonnet agents use these conventions to produce production-ready code that passes verified builds and tests.

How do I start orchestrating agents to implement a design document?▼

To start orchestrating agent implementation, provide the design document and start the orchestration. The process grounds the design and project docs, spawns Sonnet agents to work on independent subsystems, tracks progress, and supports cross-session resumes.

Does agent orchestration support resuming implementation across multiple sessions?▼

Agent orchestration supports resuming implementation across multiple sessions by tracking progress for each spawned Sonnet agent. This allows large designs with 20+ files to be implemented and verified over time without losing dependency management state.