test-leader

Coordinate tester assignments and generate VerificationReport with annotated artifact paths.

11|1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/ylxmf2005/AgentCorp --skill test-leader
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-leader
Source: https://github.com/ylxmf2005/AgentCorp/tree/main/agentcorp/test-leader
Command: npx skills add https://github.com/ylxmf2005/AgentCorp --skill test-leader

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill centralizes verification activities for AgentCorp changes, ensuring that every decision is grounded in inspectable evidence rather than green status alone.

Core Features & Use Cases

  • Orchestrates tester assignments across API, E2E, and regression verification lanes.
  • Enforces evidence handling rules, tracks status, and compiles a final verification report.
  • Provides templates and handoff guidance to stakeholders for consistent verification workflows.

Quick Start

Review the TestPlan and evidences, assign testers for the verify phase, and generate the verification report.

Frequently Asked Questions about test-leader

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

FAQPage Schema
How do I coordinate verification evidence for a software release?

Coordinate verification evidence by orchestrating tester assignments across API, E2E, and regression lanes, enforcing structured evidence handling rules, and compiling a final VerificationReport with annotated artifact paths for verifiable releases.

What is the best way to track verification status across multiple test assignments?

Track verification status by applying assigned categories such as approve, needs_more_evidence, and blocked across tester assignments, ensuring every final decision is grounded in inspectable evidence rather than a green status alone.

How do I generate a verification report with annotated artifact paths?

Generate a verification report by reviewing the TestPlan and collected evidences during the verify phase, which enforces evidence handling rules and compiles the final decision into a structured VerificationReport with annotated artifact paths.

Can I use structured evidence handling to block a release if verification fails?

Structured evidence handling supports blocking a release by assigning the blocked status category to tester assignments when evidence is insufficient, ensuring the final verification report reflects the needs_more_evidence or blocked state.

When do I need to assign testers across different verification lanes?

Assign testers across verification lanes during the verify phase when orchestrating API, E2E, and regression checks, ensuring evidence collection is distributed and tracked before generating the final verification report.