team-dogfood

Name: team-dogfood
Availability: InStock
Author: gtpgg1013

Orchestrate parallel dogfood browser QA against a TARGET_URL in team verify.

Updated Mar 21, 2026

Search Tags:#automation #qa #claude-code #team #browser-testing #dogfood

Ready to run

npx skills add https://github.com/gtpgg1013/claude-skills-collection --skill team-dogfood

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: team-dogfood
Source: https://github.com/gtpgg1013/claude-skills-collection/tree/main/skills/claude-local/team-dogfood
Command: npx skills add https://github.com/gtpgg1013/claude-skills-collection --skill team-dogfood

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill extends the /team orchestration to add parallel dogfood browser QA in the verify stage, enabling faster, more comprehensive validation of web apps before release.

Core Features & Use Cases

Team-wide orchestration: uses /team as base and adds parallel dogfood QA workers.
Browser-based testing: leverages agent-browser to perform automated QA against a TARGET_URL.
Guardrails & aggregation: aggregates per-worker reports into a combined outcome, supports re-test cycles on fixes.

Quick Start

Trigger this skill with a deployment task description and a TARGET_URL, for example: /team-dogfood 4 "build a web app with QA" --url http://localhost:3000.

Frequently Asked Questions about team-dogfood

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

FAQPage Schema

How do I run parallel browser QA for a deployed web app in Claude Code?▼

Parallel browser QA in Claude Code is handled by spawning multiple dogfood workers during the team verify stage to test a specified TARGET_URL. This skill uses agent-browser to automate page analysis and aggregates per-worker reports into a combined outcome.

What is dogfood browser testing and when do I need it for release validation?▼

Dogfood browser testing is the process of using your own automated workers to validate a web app before release. You need it when standard verification is insufficient and you require parallel, browser-based page analysis against a live TARGET_URL.

How do I trigger automated browser testing alongside a standard team verify workflow?▼

You trigger automated browser testing by invoking the skill with a deployment task and a TARGET_URL, such as /team-dogfood 4 "build a web app with QA" --url http://localhost:3000. This injects dogfood tasks into the standard team workflow.

Can I use agent-browser for parallel QA testing within a Claude Code team orchestration?▼

Yes, you can use agent-browser for parallel QA testing within a Claude Code team orchestration. The skill extends the /team base orchestration to spawn multiple dogfood workers that leverage agent-browser for automated page analysis.

Does parallel dogfood QA support re-test cycles after fixing web app bugs?▼

Parallel dogfood QA supports re-test cycles on fixes. After aggregating per-worker reports into a combined outcome, you can run subsequent test cycles to validate that the targeted web app fixes are resolved.

What are the limitations of using parallel dogfood workers for browser QA?▼

Parallel dogfood workers for browser QA require a running web app at a specified TARGET_URL and operate within the Claude Code team workflow. The skill depends on the /team orchestration base and the agent-browser tool to function correctly.