td-feature-qa

Coordinate offline gates, cross-boundary checks, and live Bridge validation for tdmcp features.

30|6|Updated May 25, 2026
One-click install
npx skills add https://github.com/Pantani/tdmcp --skill td-feature-qa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: td-feature-qa
Source: https://github.com/Pantani/tdmcp/tree/main/.agents/skills/td-feature-qa
Command: npx skills add https://github.com/Pantani/tdmcp --skill td-feature-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures end-to-end quality for integrated tdmcp features by coordinating offline gates, cross-boundary checks, and live TouchDesigner validation. This skill helps teams verify that a feature cooks correctly in TD, aligns CLI and docs with the registry, and surfaces defects before release.

Core Features & Use Cases

  • Offline gates: run type checks, build, and tests to validate code integrity without needing TouchDesigner.
  • Cross-boundary checks: validate consistency across Tool↔CLI, Tool↔registry, Tool↔docs, and TD integration boundaries to prevent drift.
  • Live TD validation when the bridge is available: execute the feature against a live bridge to gather get_preview and post-cook node errors and ensure real behavior matches expectations.
  • Report-based QA: generate a consolidated workspace/04_qa<feature|batch>.md report with PASS/FAIL/UNVERIFIED statuses and concrete next steps.
  • Iterative defect handling: guide a two-to-three round fix loop, assigning defects to owners and revalidating until stable.

Quick Start

Run the end-to-end QA workflow for a new or updated tdmcp feature and verify the bridge results and TD validation.

Frequently Asked Questions about td-feature-qa

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

FAQPage Schema
How do I validate TouchDesigner features for cooking errors before release?

Cross-boundary checks validate consistency across Tool↔CLI, Tool↔registry, Tool↔docs, and TD integration boundaries to prevent drift. They ensure feature components align correctly before live TouchDesigner validation.

How do I automate quality assurance for TouchDesigner MCP feature development?

The QA workflow generates a consolidated _workspace/04_qa_<feature|batch>.md report containing PASS, FAIL, or UNVERIFIED statuses. It provides concrete next steps and actionable failure details for any identified defects.

Does the TouchDesigner Bridge need to be running to perform TD feature QA?

When the Bridge is available, live TD validation executes the feature against it to capture get_preview and post-cook node errors. This ensures the real cooking behavior in TouchDesigner matches expected outcomes.

What is the best way to handle defect resolution during TouchDesigner feature validation?

Yes, the workflow validates CLI and docs alignment with the registry through cross-boundary checks. This prevents drift by ensuring the Tool, CLI, registry, and documentation remain consistent across feature updates.