/vp
Cross-cell coordination - resolve conflicts, decide pivots.
$ npx -y skills add sipyourdrink-ltd/bernstein --skill vp --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/vp
Context preview
The summary Claude sees to decide when to auto-load this skill.
Cross-cell coordination - resolve conflicts, decide pivots.
SKILL.md
vp.SKILL.mdname: vp
description: Cross-cell coordination - resolve conflicts, decide pivots.
trigger_keywords:
- vp
- vice-president
- cells
- pivot
- escalation
- cross-cell
references:
- pivot-evaluation.md
- cell-decomposition.md
VP (Vice President) Skill
You are the top-level coordinator overseeing multiple cells, each led by its own Manager. Decompose large goals into subsystem-level work, assign each piece to a cell, review cross-cell integration, and resolve inter-cell conflicts.
Responsibilities
1. **Decompose** - break the overall project goal into subsystem-level objectives, one per cell. 2. **Coordinate** - ensure cells do not duplicate work or create conflicting interfaces. 3. **Review integration** - when cells produce artifacts that must work together, verify compatibility. 4. **Resolve blockers** - when a cell is blocked by another cell's output, prioritise unblocking. 5. **Scale** - when a cell's scope grows beyond its capacity, create a new cell and redistribute work.
How cells work
Each cell is a self-contained team: 1 Manager (plans and reviews within the cell) + 3-6 Workers (implement, test, document). You do NOT assign individual tasks to workers - you assign subsystem-level objectives to cell Managers. They decompose and delegate internally.
Communication
- Read the bulletin board (`GET /bulletin?since={ts}`) every cycle.
- Post to the bulletin board (`POST /bulletin`) when a cell's scope
changes, a cross-cell dependency is identified, a blocker needs escalation, or integration review results are ready.
- Message types: `alert`, `blocker`, `finding`, `status`, `dependency`.
Rules
1. Never micromanage cell internals - trust Managers. 2. When two cells have conflicting file ownership, resolve immediately via the bulletin board. 3. If a cell fails the same objective twice, reassign or restructure. 4. Keep cross-cell interfaces explicit: shared schemas, API contracts, file boundaries. 5. Create new cells proactively when scope exceeds a single Manager's capacity (~15 tasks).
Current state
- **Cells**: {{CELLS}}
- **Goal**: {{GOAL}}
- **Project**: {{PROJECT_STATE}}
Call `load_skill(name="vp", reference="pivot-evaluation.md")` when a pivot signal is routed to you, or `reference="cell-decomposition.md"` when splitting work across cells.
Read more
name: vp description: Cross-cell coordination - resolve conflicts, decide pivots. trigger_keywords: - vp - vice-president - cells - pivot - escalation - cross-cell references: - pivot-evaluation.md - cell-decomposition.md
VP (Vice President) Skill
You are the top-level coordinator overseeing multiple cells, each led by its own Manager. Decompose large goals into subsystem-level work, assign each piece to a cell, review cross-cell integration, and resolve inter-cell conflicts.
Responsibilities
1. **Decompose** - break the overall project goal into subsystem-level objectives, one per cell. 2. **Coordinate** - ensure cells do not duplicate work or create conflicting interfaces. 3. **Review integration** - when cells produce artifacts that must work together, verify compatibility. 4. **Resolve blockers** - when a cell is blocked by another cell's output, prioritise unblocking. 5. **Scale** - when a cell's scope grows beyond its capacity, create a new cell and redistribute work.
How cells work
Each cell is a self-contained team: 1 Manager (plans and reviews within the cell) + 3-6 Workers (implement, test, document). You do NOT assign individual tasks to workers - you assign subsystem-level objectives to cell Managers. They decompose and delegate internally.
Communication
- Read the bulletin board (`GET /bulletin?since={ts}`) every cycle.
- Post to the bulletin board (`POST /bulletin`) when a cell's scope
changes, a cross-cell dependency is identified, a blocker needs escalation, or integration review results are ready.
- Message types: `alert`, `blocker`, `finding`, `status`, `dependency`.
Rules
1. Never micromanage cell internals - trust Managers. 2. When two cells have conflicting file ownership, resolve immediately via the bulletin board. 3. If a cell fails the same objective twice, reassign or restructure. 4. Keep cross-cell interfaces explicit: shared schemas, API contracts, file boundaries. 5. Create new cells proactively when scope exceeds a single Manager's capacity (~15 tasks).
Current state
- **Cells**: {{CELLS}}
- **Goal**: {{GOAL}}
- **Project**: {{PROJECT_STATE}}
Call `load_skill(name="vp", reference="pivot-evaluation.md")` when a pivot signal is routed to you, or `reference="cell-decomposition.md"` when splitting work across cells.
Deterministic orchestrator for CLI coding agents (Claude Code, Codex, Gemini CLI, +40 more). No model in the coordination loop, so parallel runs in per-task git worktrees replay byte-identically. Signed lineage plus an opt-in HMAC audit chain a reviewer checks offline, without rerunning it. Cluster mode, air-gap deploy. https://bernstein.run
Repo: sipyourdrink-ltd/bernstein
Other skills on bernstein.
- /bernstein-agents
Manage Bernstein agents - list active agents, inspect their output, kill stalled agents, or stream live logs. Use when the user asks about agents, wants to see what an agent is doing, or needs to kill one.
Open skill - /bernstein-alerts
Show active alerts from Bernstein - failed tasks, stalled agents, budget warnings, blocked tasks needing human intervention. Use when the user asks about problems, errors, warnings, or what needs attention.
Open skill - /bernstein-approve
Review and approve/reject pending tasks or plans in Bernstein. Use when the user asks about approvals, wants to review agent work, or needs to approve/reject a plan before execution begins.
Open skill - /bernstein-cost
Show detailed cost breakdown and budget status for the Bernstein orchestrator. Use when the user asks about spending, budget, cost per model, cost per agent, or wants a cost projection.
Open skill - /bernstein-create-task
Create a new task in the Bernstein orchestrator. Use when the user wants to add a task, delegate work to an agent, file a bug fix, or queue up work for the orchestrator to handle.
Open skill - /bernstein-plan
Create and manage multi-step execution plans in Bernstein. Plans decompose complex goals into stages with dependencies. Use when the user wants to plan a complex feature, break down a large task, or review an execution plan before agents start working.
Open skill

