Menü
Cross-cell coordination - resolve conflicts, decide pivots.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| 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"] |
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.
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.
GET /bulletin?since={ts}) every cycle.POST /bulletin) when a cell's scope
changes, a cross-cell dependency is identified, a blocker needs
escalation, or integration review results are ready.alert, blocker, finding, status, dependency.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.
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.
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.
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.
Show quality metrics for Bernstein runs - success rates per model, lint/test pass rates, completion time distributions. Use when the user asks about quality, reliability, which model performs best, or pass rates.
Show Bernstein orchestrator status - active agents, task progress, costs, and alerts. Use when the user asks about orchestrator status, what agents are doing, task progress, how much has been spent, or what's happening with the build.
System design - module boundaries, API contracts, ADRs.