Menu
Enforces a strict, turn-based TDD ping-pong cycle by defining and orchestrating two specialized subagents (Player One and Player Two).
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Enforces data governance by verifying Knowledge Catalog Aspects before recommending BigQuery tables.
Ensures the game has a fun easter egg that turns the screen black and white, sepia or gameboy monotone colours. Use when creating or modifying a game.
Ensures platformer games have polished movement, responsive controls, and balanced jump mechanics. Use ONLY when the game type is "platformer".
Guides the creation of a new game and is the high-level orchestrator skill that MUST be invoked first. Use when tasked with creating a new game.
Arcade game must have a retro asthetic. Use when creating or modifying a game to ensure that the game looks retro and maintains a consistent look and feel with all games.
Game will always use the same control scheme/buttons and mapping of the gamepad and keyboard. Use when creating or modifying a game.
| name | ping_pong_pairing |
| description | Enforces a strict, turn-based TDD ping-pong cycle by defining and orchestrating two specialized subagents (Player One and Player Two). |
Use this skill to orchestrate an automated, turn-based Ping-Pong TDD loop using Antigravity subagents. The main agent acts as the Coordinator, while delegating the coding and testing tasks to two specialized subagents: Player One and Player Two.
At the start of the session, the Coordinator MUST define the two subagents using the define_subagent tool:
tdd_player_one:
enable_write_tools: true).You are Player One in a Ping-Pong pairing pair.
Your task is to:
1. Check which phase of the TDD cycle you are in.
2. If writing a test: Identify the next smallest, simplest unit of functionality to test, write exactly one new failing unit test, verify it fails, and report back (RED phase).
3. If implementing code: Write the absolute minimum amount of production code to make the current failing test pass, verify all tests pass, and report back (GREEN phase).
tdd_player_two:
enable_write_tools: true).You are Player Two in a Ping-Pong pairing pair.
Your task is to:
1. Check which phase of the TDD cycle you are in.
2. If writing a test: Identify the next smallest, simplest unit of functionality to test, write exactly one new failing unit test, verify it fails, and report back (RED phase).
3. If implementing code: Write the absolute minimum amount of production code to make the current failing test pass, verify all tests pass, and report back (GREEN phase).
The Coordinator drives the process by invoking the subagents sequentially using invoke_subagent and checkpointing their progress in git:
tdd_player_one with the prompt:
"Write the next failing unit test for [feature description/checklist item]. Verify it fails, then report back."git add <file>), and commit:
git commit -m "Player One: Add failing test for [feature]"tdd_player_two with the prompt:
"Implement the minimum code to pass the current failing test. Run the test suite, verify it passes, then report back."git add <file>), and commit:
git commit -m "Player Two: Implement minimum code for [feature]"tdd_player_two with the prompt:
"Write the next failing unit test for [next checklist item]. Verify it fails, then report back."git add <file>), and commit:
git commit -m "Player Two: Add failing test for [next feature]"tdd_player_one with the prompt:
"Implement the minimum code to pass the current failing test. Run the test suite, verify it passes, then report back."git add <file>), and commit:
git commit -m "Player One: Implement minimum code for [next feature]"Repeat this loop (alternating roles after every Green implementation) until all features are complete.
git commit -m "Refactor: [description]"To minimize repeated permission prompts during the turn-based loop:
Workspace: 'inherit' (default). Avoid using 'branch' (sandbox mode) because temporary worktree paths bypass project-specific permission rules.