rounds

Coordinate spawned agents across verification rounds until exit criteria are met.

5|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/humblemuzzu/ghosttyyy --skill rounds
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rounds
Source: https://github.com/humblemuzzu/ghosttyyy/tree/main/pi-setup/config-skills/rounds
Command: npx skills add https://github.com/humblemuzzu/ghosttyyy --skill rounds

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating spawned agents to verify results converge across rounds and ensure decisions are validated against explicit criteria.

Core Features & Use Cases

  • Round lifecycle orchestration: spawn agents, collect reports, assess convergence, spawn fixes, and advance rounds until criteria are met.
  • Explicit exit criteria and issue-tracking: define when rounds are considered clean and document changes across iterations.
  • Composability with spar: orchestrate parallel debates and use dedicated skills to handle sub-tasks.

Quick Start

Initiate a multi-round verification by spawning agents, collecting reports, and escalating fixes until two consecutive clean rounds are achieved.

Frequently Asked Questions about rounds

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

FAQPage Schema
How do I coordinate multi-agent verification to ensure results converge across rounds?

You coordinate multi-agent verification by orchestrating a round lifecycle that spawns agents, collects reports, assesses convergence, and escalates fixes until explicit exit criteria are satisfied across consecutive clean rounds.

What is the round lifecycle for orchestrating bounded multi-round verification tasks?

The round lifecycle for multi-round verification follows a spawn, wait, assess, and escalate sequence. It tracks issues and advances iterations until decisions validate against defined exit criteria and achieve two consecutive clean rounds.

How do I define exit criteria for multi-agent verification rounds?

Exit criteria for verification rounds are defined explicitly to determine when iterations are considered clean. The process documents changes across iterations and requires two consecutive clean rounds to achieve convergence.

Do I need prerequisite skills to spawn and coordinate agents for verification?

Yes, inter-agent coordination requires prerequisite skills like spawn, coordinate, and report. These skills handle sub-tasks and enable the orchestration of the round lifecycle to verify results effectively.

Can I orchestrate parallel debates and handle sub-tasks during multi-round verification?

Yes, you can orchestrate parallel debates and handle sub-tasks through composability with spar. This allows dedicated skills to manage sub-tasks while coordinating spawned agents across verification rounds.

When should I not use a multi-round verification approach for agent coordination?

Multi-round verification applies to bounded tasks requiring explicit exit criteria and issue tracking. You should avoid this approach for unbounded tasks or processes that lack strict convergence validation requirements across iterations.