orch-testing

Orchestrate end-to-end testing workflows across specialist agents.

Updated Feb 1, 2026
One-click install
npx skills add https://github.com/AI-Driven-Highspeed-Development/adhd_framework_v3 --skill orch-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orch-testing
Source: https://github.com/AI-Driven-Highspeed-Development/adhd_framework_v3/tree/main/modules/dev/instruction_core/data/skills/orch-testing
Command: npx skills add https://github.com/AI-Driven-Highspeed-Development/adhd_framework_v3 --skill orch-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates end-to-end testing workflows across specialist agents to coordinate the PLAN → SPEC-TEST → ATTACK → FINAL lifecycle, enabling structured validation and rapid feedback.

Core Features & Use Cases

  • End-to-end workflow orchestration: coordinates cross-agent test phases, gates, and rollouts.
  • Adversarial and validation testing: integrates spec tests and adversarial probing to improve robustness.
  • Lifecycle governance: enforces phase sequencing, cycle limits, and housekeeping gates to prevent drift.
  • Use Case: When coordinating a full QA cycle across HyperSan, HyperArch, and HyperRed, this skill manages planning, testing, attacks, and final validation.

Quick Start

Coordinate a full testing cycle for a target module, triggering PLAN, SPEC-TEST, ATTACK, and FINAL phases.

Frequently Asked Questions about orch-testing

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

FAQPage Schema
How do I orchestrate end-to-end testing workflows across multiple agents?

You can orchestrate end-to-end testing workflows by coordinating specialist agents through a structured PLAN, SPEC-TEST, ATTACK, and FINAL lifecycle to manage cross-agent QA and iterative fix cycles.

What is adversarial testing and how does it fit into a cross-agent QA cycle?

Adversarial testing probes system robustness by applying controlled attack cycles. In a cross-agent QA cycle, it follows spec testing to identify vulnerabilities before final validation gates are enforced.

How do I enforce phase sequencing and cycle limits during automated testing?

You enforce phase sequencing and cycle limits through lifecycle governance, which manages phase planning, restricts spec testing iterations, and applies housekeeping gates to prevent configuration drift.

Can I coordinate validation testing across HyperSan, HyperArch, and HyperRed agents?

Yes, you can coordinate validation testing across HyperSan, HyperArch, and HyperRed agents by triggering a full testing cycle that manages planning, spec tests, adversarial attacks, and final validation.

When should I use lifecycle governance for cross-agent test orchestration?

Use lifecycle governance for cross-agent test orchestration when you need structured validation, rapid feedback, and strict enforcement of phase sequencing to prevent drift during iterative fix cycles.