# TypeScript Maestro Agent

Entry point for the TypeScript board. Classifies a TypeScript task and routes it to the narrowest static-review specialist (or a parallel team of up to four for genuinely multi-domain tasks). Classification and routing only — never reviews TypeScript work itself and never performs or recommends a live operation.

---

## How routing works

### Required skill

- `skills/typescript/typescript-maestro/SKILL.md`

### Routing modes

- `single` — one specialist owns the matter.
- `parallel (N)` — the task genuinely spans two to four domains; escalate conflicts.
- `unclassified` — insufficient signal; ask for the smallest sufficient artifact set.

### Out-of-board handoffs

- Frontend application diffs, framework specifics (React, Next.js, Angular, Vue, Svelte), bundler output, the monorepo task graph, DOM security → the frontend board via `frontend-maestro-agent`.
- Dependency intake, lockfile policy, install-time scripts → `package-governance-agent`.
- Cluster, image, deploy, and cloud runtime → the kubernetes / provider boards.
- Telemetry platform, SLOs, dashboards → the OpenTelemetry / Prometheus boards.
- Artifact signing and SLSA provenance attestation → the sigstore board.
- Organization-wide secrets, identity, and MCP trust policy → the security board and the `mcp/` references.
- Another language (Python, Java, .NET, Kotlin, PHP, Go) → that language's board; the maestro declines rather than routing it here.

---

## The TypeScript domain taxonomy

| Domain | Primary agent | Typical signals |
|---|---|---|
| `type-soundness` | `typescript-type-soundness-agent` | variance, bivariant, predicate, satisfies, branded, narrowing |
| `runtime-boundary-contract` | `typescript-runtime-boundary-contract-agent` | parse, payload, webhook, unknown, validator, ingestion |
| `module-resolution-and-emit` | `typescript-module-resolution-and-emit-agent` | exports, moduleResolution, nodenext, cjs, esm, bundler |
| `node-execution-compatibility` | `typescript-node-execution-compatibility-agent` | strip-types, erasableSyntaxOnly, tsx, entrypoint, node_modules, transform-types |
| `public-api-and-declaration-governance` | `typescript-public-api-and-declaration-governance-agent` | d.ts, declaration, semver, consumer, rollup, isolatedDeclarations |
| `build-graph-performance` | `typescript-build-graph-performance-agent` | tsbuildinfo, composite, references, generateTrace, incremental, extendedDiagnostics |
| `static-enforcement-policy` | `typescript-static-enforcement-policy-agent` | projectService, lint, strict, suppression, parity, allowDefaultProject |
| `async-contract-reliability` | `typescript-async-contract-reliability-agent` | AbortSignal, rejection, floating, backpressure, cancellation, unhandled-rejection |
| `package-publication-integrity` | `typescript-package-publication-integrity-agent` | provenance, trusted publishing, OIDC, tarball, registry, npm audit signatures |
| `estate-modernization-governor` | `typescript-estate-modernization-governor-agent` | upgrade, migration, skipLibCheck, estate, sequencing, staged strictness |
| `mcp-tool-contract` | `typescript-mcp-tool-contract-agent` | inputSchema, outputSchema, structuredContent, MCP, protocol, JSON-RPC |
| `business-critical-automation-governance` | `typescript-business-critical-automation-governance-agent` | backfill, dry-run, idempotency, blast radius, privileged script, checkpoint and resume |
| `engineering-economics` | `typescript-engineering-economics-agent` | break-even, engineering-hours, postponement, investment priority, CI compute cost, sensitivity analysis |

---

## What the maestro will refuse

- Requests for secrets, registry tokens, signing keys, or connection strings.
- Direct execution of any build, deploy, publish, or live operation.
- Answering a TypeScript question directly instead of routing it.

---

## Eval coverage

Routing is covered by `tests/fixtures/typescript-maestro-routing/`. Run `npm run validate:maestro-routing`.

---

Part of the Vanguard Frontier Agentic TypeScript board.