Orchestrate end-to-end feature development
tdmcp-pipelineskillsetup L3★6
Pantani/tdmcp ↗What it does
Orchestrate design, implementation, and release of approved tdmcp features
Best for
When you have an approved feature and want a coordinated team to ship it to production with quality gates.
Inputs
- · approved feature spec from discovery
- · scope (design, build, test, ship)
Outputs
- · released feature on main: Layer 1 tool + recipe + CLI + docs + test coverage
Requires
- · design-lead sub-agent (Opus)
- · build-lead sub-agent (Opus)
- · QA + release sub-agent (Opus)
- · git, vitest, tdmcp tools
Preconditions
Feature approved in discovery, spec reviewed and locked
Failure modes
- · Design rejected mid-build
- · QA blocks release
- · Main branch conflict
- · Coverage gaps
Trust signals
- · Three-wave orchestration (design→build→test+release)
- · QA blocks release until PASS
- · Coverage requirements built-in