qa-lead-routing

Name: qa-lead-routing
Availability: InStock
Author: hiddink-ai

Route QA testing tasks to planner, writer, and engineer agents.

1|Updated May 21, 2026

Search Tags:#automation #workflow #testing #qa #orchestration #test-planning

Ready to run

npx skills add https://github.com/hiddink-ai/hiddink-harness --skill qa-lead-routing-hiddink-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-lead-routing
Source: https://github.com/hiddink-ai/hiddink-harness/tree/main/templates/skills/qa-lead-routing
Command: npx skills add https://github.com/hiddink-ai/hiddink-harness --skill qa-lead-routing-hiddink-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates manual coordination overhead in quality assurance by automatically routing testing tasks to the appropriate specialized agents for planning, documentation, and execution.

Core Features & Use Cases

Intelligent Routing: Automatically delegates tasks to qa-planner, qa-writer, or qa-engineer based on the specific testing phase.
Workflow Orchestration: Manages complex, multi-step QA cycles including test planning, documentation, and execution.
Use Case: When a user requests a full test cycle for a new feature, this skill coordinates the sequential handoff between planning, writing, and execution agents to ensure comprehensive coverage.

Quick Start

Trigger the qa-lead-routing skill to initiate a full quality assurance cycle for the current project module.

Frequently Asked Questions about qa-lead-routing

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

FAQPage Schema

How do I automate QA test planning and execution workflows?▼

Automated QA test planning and execution workflows are orchestrated by routing tasks to specialized planner, writer, and engineer agents. This eliminates manual coordination overhead by automatically managing the sequential handoff between phases for comprehensive coverage.

What is multi-agent orchestration for software testing?▼

Multi-agent orchestration for software testing coordinates specialized agents to handle distinct testing phases. It automatically routes tasks to planner, writer, and engineer agents to ensure test planning, documentation, and execution maintain sequential workflow integrity.

How do I coordinate sequential handoffs between test planning and execution?▼

Sequential handoffs between test planning and execution are coordinated by routing tasks to specialized agents based on the testing phase. The workflow automatically delegates tasks to a planner, then a writer, and finally an engineer to ensure integrity.

Do I need MCP-based agent discovery to run automated QA cycles?▼

MCP-based agent discovery is required to run automated QA cycles. This integration maintains sequential workflow integrity by enabling the orchestrator to locate and route testing tasks to the appropriate specialized planner, writer, and engineer agents.

Can I use multi-agent routing for test documentation generation?▼

Multi-agent routing can be used for test documentation generation by delegating tasks to a specialized writer agent. This manages complex, multi-step QA cycles by automatically routing documentation tasks alongside the planning and execution phases.

When should I not use orchestrated workflows for software testing?▼

Orchestrated workflows for software testing should not be used without the Agent tool and MCP-based agent discovery. Without these dependencies, the system cannot maintain sequential workflow integrity or route testing tasks to specialized agents.