vp-engineering
VP Engineering perspective - org design (team topologies), process improvement, cross-team dependencies, engineering culture, OKRs, incident management maturity, platform strategy, DX optimization, release management at scale
npx skills add vibeeval/vibecosystem --skill vp-engineering --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Orients an AI agent to address VP Engineering concerns across multiple domains: organizational design (team topologies), process improvement, cross-team dependency management, engineering culture, OKR setting, incident management maturity, platform strategy, developer experience optimization, and scalable release management. It presents a structured lens for evaluating or producing guidance in these areas, with emphasis on team types, interaction modes, org design templates, anti-patterns, agile maturity, dependency strategies, culture pillars, OKR frameworks, incident governance, platform charter, DX metrics, and improvement roadmaps.
How it works
- Provides sections covering specific domains (e.g., Engineering Org Design, Process Improvement, Cross-Team Dependency Management, Engineering Culture Building, OKR Setting, Incident Management Maturity, Platform Team Strategy, Developer Experience).
- Uses tabular schemas and markdown blocks to outline team roles, interaction modes, anti-patterns, maturity levels, responsibilities, metrics, and templates.
- Includes concrete templates and examples (e.g., Org Design Template, Dependency Matrix, OKR templates, incident roles, and maturity steps) for the agent to reference or adapt.
- Instructs the agent to reason about organization design, collaboration patterns, governance structures, and measurement criteria, then propose or critique plans aligned with these templates.
- Emphasizes self-service, cross-functional collaboration, and measurable outcomes through defined metrics and checklists.
When to use it
- When advising or designing a VP-level engineering organization or presenting a platform-oriented, cross-team operating model.
- When aligning team topology, interaction modes, and coupling with platform teams to reduce cognitive load on stream teams.
- When establishing or maturing incident management, DX, OKRs, and culture programs within an engineering org.
What it can touch
- Tools and artifacts named in the templates (e.g., CI/CD, observability, developer portal, Backstage-like portals) as part of Platform Team Charter and DX sections.
- It references standard governance artifacts: runbooks, post-mortems, SLAs, SLOs, incident commander roles, and governance checklists.
Caveats
- Contains prescriptive templates and examples; applicability may vary by company size and domain.
- Does not guarantee outcomes; it provides structures to discuss and implement, not finished solutions.
# VP Engineering Perspective ## Engineering Org Design (Team Topologies) ### Team Types | Type | Purpose | Characteristics | Size | |------|---------|----------------|------| | **Stream-aligned** | Deliver user/business value | Full-stack, autonomous, owns entire feature slice | 5-8 | | **Platform** | Reduce cognitive load for stream teams | Internal products, self-service APIs/tools | 3-6 | | **Enabling** | Help teams adopt new capabilities | Coaching, not doing; temporary engagement | 2-3 | | **Complicated subsystem** | Deep specialist expertise | ML, payments, security, real-time systems | 2-4 | ### Interaction Modes | Mode | Description | When to Use | |------|-------------|-------------| | **Collaboration** | Teams work together closely | New capability discovery, high uncertainty | | **X-as-a-Service** | One team provides, other consumes | Well-defined API/platform capability | | **Facilitating** | One team coaches another | Skill transfer, technology adoption | ### Org Design Template ```markdown ## Engineering Organization: [Company Name] ### Team Map Stream-aligned Teams: ├── Team Alpha: [product area] (5 people) │ Owns: [service/feature list] │ Stack: [tech stack] ├── Tea
- Engineering Org Design (Team Topologies)
- Team Types
- Interaction Modes
- Org Design Template
- Org Design Anti-Patterns
- Process Improvement (Agile Maturity)
- Agile Maturity Model
- Process Improvement Framework
- Common Process Fixes
- Cross-Team Dependency Management
- Dependency Mapping
- Dependency Resolution Strategies
- Dependency Anti-Patterns
- Engineering Culture Building
What does the vp-engineering skill do?
VP Engineering perspective - org design (team topologies), process improvement, cross-team dependencies, engineering culture, OKRs, incident management maturity, platform strategy, DX optimization, release management at scale
How do I install it?
Run `npx skills add vibeeval/vibecosystem --skill vp-engineering --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From vibeeval/vibecosystem, a repository with 521 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.