Orchestration QA

Validate orchestration workflows for Skills and Subagents against documented patterns.

200|22|Updated May 22, 2025

Search Tags:#validation #qa #orchestration #token-cost #agent-routing #execution-graphs #pattern-tracking

Ready to run

npx skills add https://github.com/jpicklyk/task-orchestrator --skill orchestration-qa

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Orchestration QA
Source: https://github.com/jpicklyk/task-orchestrator/tree/main/src/main/resources/claude/skills/orchestration-qa
Command: npx skills add https://github.com/jpicklyk/task-orchestrator --skill orchestration-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides quality assurance for Task Orchestrator workflows by validating that Skills and Subagents follow their documented patterns, detecting deviations, and suggesting continuous improvements.

Core Features & Use Cases

Interactive configuration - User chooses analyses to enable, optimizing token usage
Pre-execution validation - Capture context and set validation checkpoints
Post-execution review - Validate workflow adherence and output quality
Specialized quality analysis - Execution graphs, tag coverage, information density
Efficiency analysis - Token optimization and tool selection
Deviation reporting - Structured findings with severity (ALERT/WARN/INFO)
Pattern tracking - Continuous improvement and pattern learning

Quick Start

To start QA, run orchestration-qa(phase="configure") to select analyses, then initialize the QA session with orchestration-qa(phase="init"). Use orchestration-qa for ongoing reviews after each Skill or Subagent completes.

Frequently Asked Questions about Orchestration QA

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

FAQPage Schema

How do I validate that my orchestration workflows follow documented patterns?▼

Orchestration QA validates Skills and Subagents against their documented patterns across configuration, initialization, and execution phases. Run orchestration-qa(phase="configure") to select analyses, then orchestration-qa(phase="init") to establish checkpoints, and use orchestration-qa after each workflow step to detect deviations and capture structured QA reports with severity levels.

Can I optimize token usage while running QA checks on my workflows?▼

Yes. Orchestration QA includes interactive configuration where you choose which analyses to enable, and token-aware efficiency analysis that identifies tool-selection and routing improvements. This reduces unnecessary token consumption while maintaining validation coverage.

What does a QA report include for orchestration workflows?▼

QA reports deliver structured findings with severity levels (ALERT/WARN/INFO), actionable recommendations, execution graphs, tag coverage analysis, information density metrics, and deviation details. Reports highlight where Subagents and Skills diverge from patterns and propose continuous improvements.

When should I run validation checks—before or after execution?▼

Orchestration QA supports both pre-execution validation to capture context and set checkpoints before workflows run, and post-execution review to validate adherence and output quality after Skills or Subagents complete. Use pre-execution to prevent issues and post-execution to identify and track deviations.

How does pattern tracking help improve orchestration workflows over time?▼

Pattern tracking monitors workflow adherence continuously across execution cycles, detecting recurring deviations and suggesting incremental improvements. Combined with deviation reporting, it enables persistent optimization of how Skills and Subagents execute against documented patterns.