coding-orchestration

Coordinates delegation, ownership, and verification for multi-worker repository execution tasks.

Updated Jun 28, 2026
One-click install
npx skills add https://github.com/AO-HyS/aohys.com --skill coding-orchestration-ao-hys
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: coding-orchestration
Source: https://github.com/AO-HyS/aohys.com/tree/main/.agents/skills/coding-orchestration
Command: npx skills add https://github.com/AO-HyS/aohys.com --skill coding-orchestration-ao-hys

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Non-trivial coding work often fails when tasks are delegated without clear ownership, verification criteria, or evidence requirements. This Skill pins an execution contract before any worker starts, so delegated repository work stays bounded, verifiable, and accountable. ## Core Features & Use Cases - Pinned Execution Contracts: Every worker receives a compact packet naming the objective, root and revision, owned paths, authorization, checks, evidence receipt, and stop conditions. - Two Delegation Modes: Choose exact-instruction recipes or outcome delegation, both carrying the same verification and ownership requirements. - Test Change Governance: Enforces a default policy where workers cannot add or modify test files without a reviewed exception validated by a policy helper. - Use Case: When splitting a large feature across parallel CLI workers on disjoint paths, use this Skill to pin each worker's contract, collect completion receipts, and verify the integrated result before release. ## Quick Start Ask the assistant to orchestrate this repository task using the coding-orchestration skill with a pinned execution contract for each worker.

Frequently Asked Questions about coding-orchestration

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

FAQPage Schema
How do I delegate coding tasks to parallel AI workers safely?▼

Pin one execution contract per worker naming the objective, root and revision, owned paths, checks, and stop conditions. Parallel workers are allowed only on disjoint paths with no shared dependency sequence, and completion events serve as the synchronization boundary.

What is the difference between exact instructions and outcome delegation modes?▼

Exact instructions provide an ordered recipe the worker follows, reporting the first mismatch. Outcome delegation specifies the observable result and constraints, letting the worker choose the implementation while still running every enumerated mandatory check.

Can a delegated worker add or modify test files?▼

No, the default policy is allowedChanges empty, so workers cannot add, modify, or delete test files. The parent must first close a reviewed exception naming each path, its SHA-256, reason, and issue, validated by the findTestPolicyViolations helper.

How does the skill handle worker failures or interruptions?▼

On interruption, verify the live candidate and worker state before resuming, and retain evidence whose inputs are unchanged. After a failure, identify the prerequisite that must change before retrying rather than repeating the same attempt.

Does a passing test run or clean diff close a delegated task?▼

No. A clean diff, first implementation, or green test run never substitutes for verified observable behavior. The worker must return changed paths, commands, results, and remaining gaps against the contract's acceptance criteria.