Mono Plan

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

1. Detect monorepo structure (pnpm-workspace.yaml, turbo.json, lerna.json, package.json workspaces). Stop if not a monorepo.
2. Enumerate packages, read each package.json, build internal dependency graph.
3. 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).
4. Read the target phase from tasks/roadmap.md, map scope to specific packages.
5. Classify packages: independent, dependent, or shared.
6. Recommend strategy: agent-team (independent packages with branch-backed lanes), serial (linear chain), or mixed with dependency edges.
7. 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.
8. 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

Follow the shared alignment-page convention via the packaged convention resolver; output path is alignment/mono-plan-{topic}.html. By default, report results inline and write only this skill's normal durable artifacts; create an alignment page only when explicitly requested or when a concrete clarification/review need cannot be handled cleanly inline.

Default Shipping Contract

Follow the shared shipping contract convention in CLAUDE.md.