Mono Plan
Invoke as $mono-plan.
Use this skill when the user needs to plan safe parallel work across a monorepo. Generates lane specs aligned to package boundaries with lockfile and root config safety built in.
Run after /roadmap sets agent-team or implementation-safe on a phase, before /plan-phase decomposes it.
Process
- Detect monorepo structure (
pnpm-workspace.yaml, turbo.json, lerna.json, package.json workspaces). Stop if not a monorepo.
- Enumerate packages, read each
package.json, build internal dependency graph.
- Identify shared chokepoints: lockfiles (
pnpm-lock.yaml, package-lock.json, yarn.lock, bun.lockb), root configs (tsconfig.base.json, turbo.json, etc.), high-fan-out shared packages (3+ dependents).
- Read the target phase from
tasks/roadmap.md, map scope to specific packages.
- Classify packages: independent, dependent, or shared.
- Recommend strategy:
agent-team (independent packages with branch-backed lanes), serial (linear chain), or mixed with dependency edges.
- Generate lane specs in execution profile format:
- Lane 0 (deps): serial lane owning lockfiles if any lane needs dependency installs. All write lanes depend on it.
- Package lanes: one per package,
Owns scoped to package dir, Must not edit includes all lockfiles + root configs + other lanes' paths, and Branch uses agent-team/phase-N-<package-or-lane>. Scope text includes "Do NOT run pnpm install or any lockfile-modifying command."
- Consolidation/PR review: add a final review lane or implementation step that reviews every package lane branch/PR before integration.
- Validate: disjoint Owns, all lockfiles excluded from write lanes, valid DAG, unique non-primary branches, and a consolidation/PR review gate.
Output
- Monorepo tool and package count
- Shared Chokepoints: lockfiles, root configs, high-fan-out packages
- Package Dependency Graph: in-scope packages with dependency edges
- Recommended Strategy: parallel mode and rationale
- Lane Specifications: in execution profile format (Agent, Role, Mode, Scope, Owns, Must not edit, Branch, Depends on, Deliverable)
- Consolidation/PR Review: required final gate for
agent-team package lanes, including branch/PR review and boundary checks before integration
Constraints
- Do not modify task files — output is advisory only.
- Do not run package manager install/add commands.
- Maximum 12 parallel write lanes — group if more packages are in scope.
- Do not recommend
agent-team if the project cannot push lane branches to GitHub and review PRs; use implementation-safe, research-only, or serial instead.
Alignment Page
When this skill produces durable deliverables (research, specs, plans, reports, prototypes, or any document output), build a full-depth HTML alignment page following ALIGNMENT-PAGE.md in this skill's directory. Output: alignment/mono-plan-{topic}.html.
Default Shipping Contract
Follow the shared shipping contract convention in CLAUDE.md.
1---2name: mono-plan-33description: Detect monorepo structure, identify shared chokepoints, and generate safe parallel lane specs aligned to package boundaries4---5
6# Mono Plan
7
8Invoke as `$mono-plan`.
9
10Use this skill when the user needs to plan safe parallel work across a monorepo. Generates lane specs aligned to package boundaries with lockfile and root config safety built in.
11
12Run after `/roadmap` sets `agent-team` or `implementation-safe` on a phase, before `/plan-phase` decomposes it.
13
14## Process
15
161. Detect monorepo structure (`pnpm-workspace.yaml`, `turbo.json`, `lerna.json`, `package.json` workspaces). Stop if not a monorepo.
172. Enumerate packages, read each `package.json`, build internal dependency graph.
183. Identify shared chokepoints: lockfiles (`pnpm-lock.yaml`, `package-lock.json`, `yarn.lock`, `bun.lockb`), root configs (`tsconfig.base.json`, `turbo.json`, etc.), high-fan-out shared packages (3+ dependents).
194. Read the target phase from `tasks/roadmap.md`, map scope to specific packages.
205. Classify packages: independent, dependent, or shared.
216. Recommend strategy: `agent-team` (independent packages with branch-backed lanes), `serial` (linear chain), or mixed with dependency edges.
227. Generate lane specs in execution profile format:
23 - **Lane 0 (deps):** serial lane owning lockfiles if any lane needs dependency installs. All write lanes depend on it.
24 - **Package lanes:** one per package, `Owns` scoped to package dir, `Must not edit` includes all lockfiles + root configs + other lanes' paths, and `Branch` uses `agent-team/phase-N-<package-or-lane>`. Scope text includes "Do NOT run pnpm install or any lockfile-modifying command."
25 - **Consolidation/PR review:** add a final review lane or implementation step that reviews every package lane branch/PR before integration.
268. Validate: disjoint Owns, all lockfiles excluded from write lanes, valid DAG, unique non-primary branches, and a consolidation/PR review gate.
27
28## Output
29
30- **Monorepo tool and package count**
31- **Shared Chokepoints**: lockfiles, root configs, high-fan-out packages
32- **Package Dependency Graph**: in-scope packages with dependency edges
33- **Recommended Strategy**: parallel mode and rationale
34- **Lane Specifications**: in execution profile format (Agent, Role, Mode, Scope, Owns, Must not edit, Branch, Depends on, Deliverable)
35- **Consolidation/PR Review**: required final gate for `agent-team` package lanes, including branch/PR review and boundary checks before integration
36
37## Constraints
38
39- Do not modify task files — output is advisory only.
40- Do not run package manager install/add commands.
41- Maximum 12 parallel write lanes — group if more packages are in scope.
42- Do not recommend `agent-team` if the project cannot push lane branches to GitHub and review PRs; use `implementation-safe`, `research-only`, or `serial` instead.
43
44## Alignment Page
45
46When this skill produces durable deliverables (research, specs, plans, reports, prototypes, or any document output), build a full-depth HTML alignment page following `ALIGNMENT-PAGE.md` in this skill's directory. Output: `alignment/mono-plan-{topic}.html`.
47
48## Default Shipping Contract
49
50Follow the shared shipping contract convention in CLAUDE.md.
GeorgeQLe