orchestrate-v2

Name: orchestrate-v2
Availability: InStock
Author: drdatarulz

Automate PR-based project orchestration with engineering review gates.

3|Updated Feb 20, 2026

Search Tags:#automation #workflow #github #governance #pipeline #pr #orchestrate

Ready to run

npx skills add https://github.com/drdatarulz/TI-Engineering-Standards --skill orchestrate-v2

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: orchestrate-v2
Source: https://github.com/drdatarulz/TI-Engineering-Standards/tree/main/skills/archive/orchestrate-v2
Command: npx skills add https://github.com/drdatarulz/TI-Engineering-Standards --skill orchestrate-v2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end PR-based project orchestration with engineering review gates to streamline delivery workflows and ensure governance across tickets.

Core Features & Use Cases

Sequential, PR-based pipeline: Refine story, implement changes, perform engineering reviews, security review, integration tests, and close the issue.
Review loop governance: Enforce iterative feedback between roles (reviewer, implementer, test-writer) with bounded iterations.
Project-board integration: Automates status updates and PR merges while maintaining traceability across the GitHub project board.

Quick Start

Provide the mode (supervised or autonomous) and a comma-separated list of tickets to begin processing.

Frequently Asked Questions about orchestrate-v2

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

FAQPage Schema

How do I automate a GitHub PR pipeline with mandatory review gates?▼

Automate a GitHub PR pipeline by applying deterministic stage sequencing to refine stories, implement code, enforce engineering review gates, run security tests, and close issues. This orchestrates ticket-driven delivery workflows end-to-end.

Can I enforce iterative review loops between implementers and reviewers in a GitHub workflow?▼

Yes, you can enforce iterative review loops in a GitHub workflow using bounded iterations for feedback between the reviewer, implementer, and test-writer roles. This ensures governance and quality control before changes are merged.

How does GitHub project board integration work with automated PR pipelines?▼

GitHub project board integration automates status updates and PR merges while maintaining traceability across tickets. It links the PR pipeline directly to ticket-driven delivery workflows for seamless board synchronization.

Do I need to provide specific inputs to start automated ticket-driven delivery in supervised mode?▼

Yes, to start automated ticket-driven delivery you need to provide the operation mode—either supervised or autonomous—and a comma-separated list of tickets. This initiates the deterministic stage sequencing for the specified issues.

What is the difference between supervised and autonomous modes for PR orchestration?▼

Supervised and autonomous modes control the level of human oversight during PR orchestration. Both modes execute the deterministic stage sequencing, review gates, and GitHub integration, but autonomous mode requires less manual intervention across the pipeline.

Are there limitations when using deterministic stage sequencing for per-ticket pipelines?▼

Deterministic stage sequencing for per-ticket pipelines requires strict adherence to the defined stages: story refinement, implementation, review, security testing, and closure. Deviating from this sequence or bypassing review gates will disrupt the orchestration workflow.