Monorepo Task Router

Use this skill to decide ownership, split work, and hand off tasks without scope drift.

Triage

1. Map impacted files to owners.
2. Detect cross-scope dependencies early.
3. Define explicit in-scope and out-of-scope paths.
4. Pick the minimal set of owners needed.

Use this ownership map:

• apps/frontend/** -> frontend owner
• apps/backend/** -> backend owner
• docker-compose.yml, Dockerfiles, .github/workflows/**, root scripts -> infra owner

Split Strategy

Prefer one owner when possible. Split only when one of these is true:

• API contract and UI integration both change.
• Infrastructure changes are required for runtime or CI.
• Migration work and feature work can be isolated safely.

When splitting, assign disjoint write scopes.

Handoff Contract

When passing work, include all of the following: