harness-orchestration

Route user goals to skill combinations and execution order across five standard workflows.

Updated Jun 18, 2026
One-click install
npx skills add https://github.com/zhengguangli/harness-engineering-kit --skill harness-orchestration-zhengguangli
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: harness-orchestration
Source: https://github.com/zhengguangli/harness-engineering-kit/tree/main/skills/harness-orchestration
Command: npx skills add https://github.com/zhengguangli/harness-engineering-kit --skill harness-orchestration-zhengguangli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When a project offers many skills, users often do not know which ones to combine, in what order, or which to skip. This Skill acts as a read-only routing advisor that maps a user's goal to the right skill mix and execution sequence, preventing wasted context from running the full suite or skipping prerequisite steps. ## Core Features & Use Cases - Three-Layer Routing Framework: Narrows decisions from project lifecycle phase to task type to specific skills and order, avoiding a search across all skills at once. - Five Standard Workflows: Covers Greenfield initialization, daily feature development, code quality fixes, harness extension, and prompt optimization, each with defined skill sequences and omission rules. - Cross-Workflow Handoff Management: Defines upstream-output-to-downstream-consumer handoff tables so multi-workflow goals execute with verified prerequisites. - Use Case: A user says "fix this bug and make sure it never happens again" — the Skill decomposes it into Workflow 2 (fix) followed by Workflow 3 (encode the pattern as a golden principle), with an explicit handoff point between them. ## Quick Start Ask the orchestrator which skills to use and in what order for your current goal, for example "I just entered this project, what should I run first?"

Frequently Asked Questions about harness-orchestration

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

FAQPage Schema
How do I decide which skills to use for a new project?▼

Use the Greenfield Initialization workflow: run project-intake first to produce a structured project card, then bootstrap to generate the skeleton, then repo-map to verify. Small projects can skip architecture-boundaries.

How to combine multiple skills for a complex task?▼

Decompose the goal into independent sub-goals, route each through its own workflow, then combine them with explicit handoff points. Complete one workflow before starting the next to avoid context fragmentation.

When should I skip skill orchestration entirely?▼

Skip orchestration when you explicitly know which skill to use, when the task involves only a single skill, or when you are asking about a specific skill's usage rather than combinations. Use the skill directly instead.

What is the difference between Workflow 2 and Workflow 3 routing?▼

Workflow 2 handles functional defects and feature development, while Workflow 3 handles code quality and style drift. When a user says "fix", ask one clarifying question — functional defect or code quality — to disambiguate.

Why must project-intake run before bootstrap?▼

The bootstrap skeleton is generated from the project card produced by project-intake. Skipping intake risks generating a skeleton that does not match the actual project, causing rework. The routing halts bootstrap until intake completes.

What are the limitations of automated skill routing?▼

Routing is read-only advice, not execution — it cannot invoke skills or create files. It also cannot route to newly added skills until the skill is registered in the dependency validator, architecture docs, and trigger regression tests.