orchestrator

Orchestrate software development tasks through a Plan→Execute→Validate→Deliver pipeline.

1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/YuluoY/nimis --skill orchestrator-yuluoy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestrator
Source: https://github.com/YuluoY/nimis/tree/main/skills-en/orchestrator
Command: npx skills add https://github.com/YuluoY/nimis --skill orchestrator-yuluoy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The orchestrator coordinates end-to-end software development work by turning a user request into a disciplined Plan → Execute → Validate → Deliver pipeline, preventing ad-hoc coding and ensuring traceable, recoverable progress across slices and quality gates.

Core Features & Use Cases

  • Adaptive input classification and context sensing that detect project type (new project, feature, bug, refactor) and gather targeted project facts.
  • Difficulty scoring, scope slicing, and route selection (A/B/C/D) to break work into ordered, independently deliverable slices.
  • Enforced phase guards and mandatory docs-output/project-context writeback to create mechanical evidence and enable resumable sessions.
  • Variant strategies (lite / standard / plus) including TDD-driven execution, SubAgent isolation for + variant, and automatic reconcile/audit during Deliver.
  • Use case: Start a full-feature implementation, run through macro clarification, split into slices, and reliably produce persisted docs, tests, and context syncs for each slice.

Quick Start

Ask the orchestrator to "Plan and execute end-to-end implementation of <requirement>, run context sensing, slice the scope, and deliver each slice with Plan→Execute→Validate→Deliver quality gates".

Frequently Asked Questions about orchestrator

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

FAQPage Schema
How do I orchestrate end-to-end software development workflows with phase guards?

End-to-end development workflows are orchestrated by routing requests through a controlled Plan, Execute, Validate, and Deliver pipeline, enforcing phase guards and docs-output synchronization to ensure traceable progress. This prevents ad-hoc coding across slices.

What is scope slicing in software engineering and when do I need it?

Scope slicing is a technique that uses difficulty scoring and route selection to break work into ordered, independently deliverable slices. You need it during feature additions or refactorings to enable resumable sessions and recoverable progress.

How to apply TDD-driven execution to a feature implementation pipeline?

TDD-driven execution applies to feature implementation pipelines by selecting the plus variant, which supports SubAgent isolation for task execution. This ensures tests are written and validated before delivery through automatic reconcile and audit.

Can I use a subagent workflow for bug fixes in an existing project context?

Yes, subagent workflows can be used for bug fixes in an existing project context by applying adaptive input classification and context sensing. The orchestrator detects the project type and gathers targeted facts to execute isolated bug resolution slices.

What is the best way to manage project-context writeback during code refactoring?

The best way to manage project-context writeback during refactoring is through mandatory phase guards that mechanically persist context updates. This creates mechanical evidence and enables session resumption across independently delivered slices.

Why does ad-hoc coding fail when implementing complex features across multiple slices?

Ad-hoc coding fails because it lacks enforced quality gates and docs-output synchronization, preventing traceable progress. Coordinated pipelines solve this by enforcing phase guards and project-context writeback for each delivered slice.