trio:tc-management

Coordinate test-case lifecycle governance from PRD alignment to tc-write dispatch.

5|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/10XTeams/trio --skill trio-tc-management
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trio:tc-management
Source: https://github.com/10XTeams/trio/tree/main/src-plugin/skills/trio%3Atc-management
Command: npx skills add https://github.com/10XTeams/trio --skill trio-tc-management

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates the governance of test-case lifecycles, ensuring PRD alignment and reliable dispatch of tc-write actions, reducing drift between planning docs and test artifacts.

Core Features & Use Cases

  • Audit-path workflow: declares Test Mode, validates framework discovery, checks folder alignment with PRD, runs coverage and false-pass audits, and dispatches trio:tc-write with add / skip / rewrite.
  • Patch-path workflow: applies explicit modifications via a patch manifest to trio:tc-write with decision=patch, skipping audits, and enforcing strengthen-only operations.
  • Output governance: guarantees per-TC traceability with provenance and enforces safety constraints to avoid unintended changes.

Quick Start

Declare the Test Mode and let the skill validate PRD alignment, run coverage audits, and dispatch trio:tc-write with the chosen decision.

Frequently Asked Questions about trio:tc-management

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

FAQPage Schema
How do I automate test-case lifecycle governance from PRD alignment to dispatch?

Test-case lifecycle governance is automated by validating PRD alignment, checking folder structure, running coverage audits, and dispatching updates with add, skip, or rewrite decisions while enforcing preconditions and provenance.

What is the difference between audit-path and patch-path workflows for test management?

The audit-path workflow runs full coverage and false-pass audits before dispatching add, skip, or rewrite decisions, while the patch-path workflow applies explicit manifest modifications with a strengthen-only constraint, skipping audits entirely.

How do I apply strengthen-only test case updates using a patch manifest?

Strengthen-only test case updates are applied via the patch-path workflow, which uses an explicit patch manifest to dispatch modifications, skipping audits and enforcing safety constraints to prevent unintended changes.

Why does test case dispatch require declaring Test Mode beforehand?

Declaring Test Mode is a required precondition that ensures the system validates framework discovery and folder alignment with the PRD before dispatching any test-case updates or applying patch paths.

Can I skip coverage audits when adding test cases?

Coverage audits can only be skipped when using the patch-path workflow with an explicit manifest, which restricts operations to strengthen-only changes and bypasses the audit-path validation steps.

What is the best way to prevent drift between planning docs and test artifacts?

Preventing drift between planning docs and test artifacts requires orchestrating test-case lifecycles through PRD alignment validation, folder checks, and per-TC traceability with provenance guardrails during dispatch.