qa-delegate

Delegates browser UI verification walks to a Sonnet subagent using written test plans.

Updated May 12, 2026
One-click install
npx skills add https://github.com/fryanpan/ai-team-lead --skill qa-delegate-fryanpan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-delegate
Source: https://github.com/fryanpan/ai-team-lead/tree/main/plugin/team-lead-fleet/skills/qa-delegate
Command: npx skills add https://github.com/fryanpan/ai-team-lead --skill qa-delegate-fryanpan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running browser-based UI verification inside the main agent session floods its context with screenshots and DOM state, leaving little room for actual fixing work. This Skill enforces a delegation pattern that keeps visual QA out of the main context while still producing repeatable, reviewable test plans. ## Core Features & Use Cases - Repeatable Test Plans: Requires writing a concrete test plan (user goals, steps, expected results) before any browser walk begins, with human review for high-stakes changes. - Subagent-Driven Walks: A Sonnet subagent owns the entire navigate → screenshot → judge loop, keeping screenshots and DOM in its own context. - Concise Reporting: The main agent receives only pass/fail per goal, findings, and screenshot paths, then fixes issues and re-delegates for re-verification. - Use Case: After shipping a UI change, hand the subagent the staging URL and test plan; it reports which goals pass or fail, and the main agent patches the code and re-runs the walk. ## Quick Start Ask the agent to verify the updated checkout flow in the browser by delegating a QA walk with a written test plan to a subagent.

Frequently Asked Questions about qa-delegate

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

FAQPage Schema
How do I run browser UI testing without bloating my agent's context?▼

Delegate the entire browser walk to a subagent. Write a test plan first, hand the subagent the URL and plan, and let it own the navigate, screenshot, and judge loop so screenshots and DOM stay in its context, not yours.

How to delegate visual QA to a subagent in Claude Code?▼

Give the subagent the target URL, a written test plan listing user goals and expected results, and the instruction to run it and report back. It returns pass/fail per goal, findings, and screenshot paths.

Should the main agent run browser verification itself?▼

No. The main agent should never drive the walk because screenshots and DOM state balloon its context. It should delegate the goal and plan, receive concise results, fix broken code, and re-delegate to re-verify.

When should the QA test plan be reviewed by a human?▼

Review the test plan with a human before running it when the change is high-stakes or when the definition of correct behavior is ambiguous. For routine changes, the plan can be executed directly.

What heuristics can the QA subagent use during walkthroughs?▼

The subagent can run the /ux-review command for walkthrough heuristics while executing the test plan, complementing the goal-by-goal pass/fail judgment defined in the plan.