orchestrate

Coordinates implement, test, CI, review, and PR agents for Asana tasks.

Updated May 11, 2026
One-click install
npx skills add https://github.com/thachrocky12345/local-agent-train-workstation --skill orchestrate-thachrocky12345
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestrate
Source: https://github.com/thachrocky12345/local-agent-train-workstation/tree/main/qvac/packages/ocr-onnx/.agent/skills/orchestrate
Command: npx skills add https://github.com/thachrocky12345/local-agent-train-workstation --skill orchestrate-thachrocky12345

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually coordinating implementation, testing, CI validation, code review, and PR creation for each task is repetitive and error-prone. This Skill automates the full pipeline from an Asana task to a reviewed pull request. ## Core Features & Use Cases - End-to-End Pipeline: Runs branch setup, planning, implementation, test writing, CI validation, code review, and PR creation in sequence. - Multi-Agent Coordination: Delegates work to implementer, test-writer, ci-validator, and code-reviewer agents with retry and failure handling. - Asana Integration: Reads task details, comments plans and results, and links the final PR back to the task. - Use Case: Given an Asana task URL for a new feature, the Skill creates a feature branch, implements and tests the change, validates CI for affected native addon packages, reviews the diff, and opens a linked PR. ## Quick Start Run the orchestrate pipeline for Asana task https://app.asana.com/0/1234567890/1213560067347874 and create a PR when finished.

Frequently Asked Questions about orchestrate

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

FAQPage Schema
How do I automate the implement to PR workflow for an Asana task?

Run the orchestrate pipeline with an Asana task ID or URL. It creates a feature branch, drafts a plan for approval, implements and tests the change, validates CI, reviews the code, and opens a linked pull request.

How does the pipeline decide when CI validation is needed?

It runs git diff against main and checks changed files against a CI package mapping. Native addon packages require CI validation, SDK packages are validated automatically on PR creation, and docs or config changes skip CI entirely.

Can I approve the implementation plan before code is written?

Yes. Phase 0.5 drafts an implementation plan listing files to change, design decisions, and verification steps, then waits for explicit user approval before launching the implementer agent.

What happens when CI fails during the pipeline?

Code errors send the failure details back to the implementer agent for another attempt, while infrastructure errors are retried by the ci-validator. The pipeline stops after two failed implement-to-CI loops and reports the issue.

Does the pipeline write tests automatically for new features?

Yes, when changes add public APIs, new behavior, or bug fixes, a test-writer agent creates tests matching existing patterns. Refactors, docs-only changes, and changes already covered by tests are skipped.