build-coordinator

Coordinate cross-package changes and assign tasks across a 22-package TypeScript monorepo.

21|4|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/tylerjrbuell/reactive-agents-ts --skill build-coordinator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-coordinator
Source: https://github.com/tylerjrbuell/reactive-agents-ts/tree/main/.agents/skills/build-coordinator
Command: npx skills add https://github.com/tylerjrbuell/reactive-agents-ts --skill build-coordinator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate and sequence cross-cutting changes across a multi-package TypeScript monorepo to prevent downstream breakage, reduce context thrashing, and ensure workspace-wide correctness when implementing incremental features, refactors, or API changes.

Core Features & Use Cases

  • Dependency-aware planning: Analyze package dependency layers and determine safe change ordering for interface edits and new features.
  • Task assignment & parallelization: Break large cross-package work into sized tasks, assign them to teammates, and indicate which tasks can run in parallel versus sequentially.
  • Gate & validation checklist: Enforce upstream test passing, workspace-wide typechecks, index export verification, and full integration validation before allowing dependent work to proceed.
  • Use Case: Roll out a new memory API across core, llm-provider, and runtime by sequencing upstream edits, assigning package owners, running per-package tests, and then executing workspace-wide validation.

Quick Start

Assign and sequence tasks for an incremental feature affecting core and memory, ensure upstream package tests pass, and run a workspace-wide typecheck before allowing downstream changes.

Frequently Asked Questions about build-coordinator

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

FAQPage Schema
How do I coordinate cross-package changes in a TypeScript monorepo?

Coordinate cross-package changes by analyzing dependency layers, sequencing upstream edits, assigning package owners, and enforcing per-package test gates before downstream work proceeds. This ensures safe change ordering and workspace-wide correctness across multi-package refactors.

What's the best way to parallelize tasks across monorepo packages without breaking dependencies?

Parallelize monorepo tasks by breaking cross-package work into sized assignments and identifying which can run concurrently versus sequentially based on the dependency graph. This prevents downstream breakage while maximizing parallel execution efficiency.

How do I enforce integration testing and typecheck gates before allowing dependent package work?

Enforce integration testing and typecheck gates by requiring upstream package tests to pass, running workspace-wide typechecks, and verifying index exports before allowing downstream changes. Full integration validation must complete before dependent work proceeds.

Can I use dependency graph ordering to sequence API changes across multiple monorepo packages?

Yes, dependency graph ordering sequences API changes across monorepo packages by analyzing package dependency layers to determine safe change ordering for interface edits. Upstream edits are sequenced first, followed by per-package tests and workspace-wide validation.

When should I use cross-package monorepo coordination for incremental features?

Use cross-package monorepo coordination when implementing incremental features, refactors, or API changes that span multiple packages. It prevents downstream breakage and reduces context thrashing by enforcing dependency-aware planning and integration gating.

Why does downstream package work fail after upstream interface changes in a monorepo?

Downstream package work fails after upstream interface changes when integration gating is skipped. Without enforcing upstream test passage, workspace-wide typechecks, and index export verification, dependent packages encounter type errors and broken imports.