Orchestrate progressive automated test coverage across L1, L2, and L3 layers.
npx skills add https://github.com/tcytan/tecton --skill team-testing-tcytan
Please help me install this Agent Skill. Skill: team-testing Source: https://github.com/tcytan/tecton/tree/main/.claude/skills/team-testing Command: npx skills add https://github.com/tcytan/tecton --skill team-testing-tcytan
This Skill orchestrates a multi-agent testing pipeline that increases confidence by generating, executing, and iteratively improving tests across L1/L2/L3 coverage layers when quality gates are not met.
Orchestrate multi-agent test generation and execution for the current change set by triggering the pipeline with the message "team testing" and providing your test task description.
High-intent search queries and answers about installing and using this skill.
Progressive test coverage is orchestrated by mapping change scope into L1 unit, L2 integration, and L3 E2E layers, running a coordinator-selected pipeline that generates, executes, and iteratively improves tests until quality gates are met.
Generator-Critic loops for automated test generation work by having a generator create tests, a critic revise them, and an executor re-run them up to configured max iterations until pass-rate and layer coverage targets are satisfied.
Automating test generation with quality gates involves a strategist-to-analyst workflow that executes tests, analyzes results, and applies pass-rate and layer coverage targets to gate progression, writing structured artifacts to a session directory for auditability.
Multi-agent test orchestration requires YAML-defined role routing to execute phase-by-phase tasks, routing work through the strategist, generator, executor, and analyst roles while managing shared session artifacts and convergence limits.
Targeted testing scenarios are supported alongside standard and comprehensive pipelines, allowing the coordinator to select the appropriate testing depth based on the mapped change scope and proceed with the corresponding L1, L2, and L3 execution.
Multi-agent orchestration for test coverage should be avoided when simple change sets require no iterative refinement, as the Generator-Critic convergence loops and sessionized artifacts add overhead unnecessary for basic, single-layer unit testing.
AesopScottConvert role artifacts into agent briefs with job, authority, and boundaries.
robotijnParse cross-format coverage reports to enforce branch and diff thresholds and gate merges.
tikazyqAnalyze unit, integration, and end-to-end test distribution against CRAFT standards.
corbat-techAutomates iterative code refinement cycles combining ML and AI technologies with a focus on quality, safety, and efficiency.
