Orchestration QA

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.

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.

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.

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.

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.