noob-pool

Orchestrate QA agents for ticket test cases with round-robin assignment.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/ganeshgaxy/apps-for-testing --skill noob-pool
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: noob-pool
Source: https://github.com/ganeshgaxy/apps-for-testing/tree/main/.claude/skills/noob-pool
Command: npx skills add https://github.com/ganeshgaxy/apps-for-testing --skill noob-pool

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates QA/test execution for a ticket by coordinating multiple agents to prevent race conditions and ensure consistent results when parallel processes run.

Core Features & Use Cases

  • Per-test-case assignment: Enumerate all pending test cases upfront and assign each to a specific agent invocation to eliminate competition.
  • Thread-safe orchestration: Pre-claim entries atomically before spawning sub-agents and track progress via the pool dashboard.
  • Flexible configuration: Supports multiple agent configs, optional target/role/file/launch-dir fields, and a MAX_SPAWNS cap to control parallelism.

Quick Start

Register a ticket, fetch the latest run pack, and dispatch pending test cases to agents in a round-robin fashion.

Frequently Asked Questions about noob-pool

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

FAQPage Schema
How do I prevent race conditions when running parallel QA agents on the same ticket?

To prevent race conditions during parallel QA execution, you can orchestrate agents by pre-claiming pending test case entries atomically before spawning sub-agents. This thread-safe pre-claim process eliminates competition by assigning each test case to a specific agent invocation upfront.

What is round-robin task dispatch for parallel test execution?

Round-robin task dispatch for parallel execution is a method of cycling through a pool of agent configurations to assign pending test cases. It reads the latest run pack, filters pending entries, and distributes them sequentially to agents to ensure balanced workload distribution.

How do I set up QA orchestration to assign test cases to multiple agents?

To set up QA orchestration, register a ticket, fetch the latest run pack, and dispatch pending test cases to agents in a round-robin fashion. You can configure multiple agent profiles with optional target, role, file, and launch-dir fields before spawning sub-agents.

Can I control the parallelism level when spawning sub-agents for test orchestration?

Yes, you can control the parallelism level of test orchestration by setting a MAX_SPAWNS cap. This configuration limits the number of sub-agents spawned simultaneously, preventing resource exhaustion while maintaining parallel execution across your agent pool.

How do I monitor the progress of dispatched QA agents and pending test cases?

You can monitor dispatched QA agents and pending test cases via a pool dashboard URL. This dashboard is provided automatically by the orchestrator after pre-claiming entries and spawning sub-agents, allowing you to track real-time execution progress.