trio:test-management

Name: trio:test-management
Availability: InStock
Author: 10xteams

Dispatch per-submodule test executors, persist partial results, and assemble reports.

5|Updated Apr 26, 2026

Search Tags:#automation #e2e #reporting #submodule #bug-tracking #test-execution

Ready to run

npx skills add https://github.com/10XTeams/trio --skill trio-test-management

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: trio:test-management
Source: https://github.com/10XTeams/trio/tree/main/src-plugin/skills/trio%3Atest-management
Command: npx skills add https://github.com/10XTeams/trio --skill trio-test-management

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill orchestrates end-to-end test execution and compiles modular reports, ensuring traceability and verifiability of test outcomes.

Core Features & Use Cases

Modular dispatch: sequentially runs per sub-module and persists partial results to disk.
Coverage gating: enforces a ≥90% test coverage threshold before proceeding to report assembly.
Report assembly: builds report.md and bugs.json from partial results, with a dedicated bug schema for failed cases.
Safe boundaries: stops on failures and requires explicit user action to trigger bugfix planning.

Quick Start

Run /trio:subsprint-planner to begin by selecting modules and dispatching test execution for each sub-module.

Frequently Asked Questions about trio:test-management

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

FAQPage Schema

How do I coordinate end-to-end test execution across multiple sub-modules?▼

End-to-end test execution across sub-modules is coordinated by dispatching per-submodule test executors sequentially, persisting partial results to disk, and assembling a final consolidated report.

How does test coverage gating work during modular test suite execution?▼

Test coverage gating enforces a strict 90% threshold before proceeding to report assembly, ensuring modular test suites meet minimum coverage standards before finalizing results.

What's the best way to automate bug tracking from failed e2e test cases?▼

Automate bug tracking from failed e2e test cases by assembling a bugs.json file from partial test results using a dedicated bug schema, capturing failed cases for explicit user-driven bugfix planning.

How do I generate test execution reports for modular test suites?▼

Generate test execution reports by assembling partial results persisted from per-submodule dispatch into a report.md file, ensuring full traceability and verifiability of test outcomes.

Can I use this workflow if my test coverage is below 90%?▼

No, this workflow enforces a 90% coverage gate and stops on failures requiring a separate bugfix step, ensuring modular test suites meet coverage standards before finalizing reports.

Why does my test execution stop on failures instead of continuing to the next module?▼

Test execution stops on failures to enforce safe boundaries, requiring explicit user action to trigger bugfix planning before proceeding, preventing cascading errors across sub-modules.