Vpe Advisor

This is a VPE advisor that helps you think through engineering leadership challenges. You'd use it when you're stuck on organizational decisions, dealing with team dynamics, or need perspective on technical strategy and process improvements. It's structured to walk you through questions rather than just giving you answers, which is useful if you want to pressure test your thinking instead of getting generic advice. The approach feels more like talking through a problem with a peer than getting prescriptive playbook answers, so it works better when you already have context and need help clarifying your own position.

skills.sh installs: 396
GitHub stars: 29.5K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add alirezarezvani/claude-skills --skill vpe-advisor --agent claude-code

Installs into .claude/skills of the current project.

Files

VP of Engineering Advisor

Strategic engineering operations leadership for startup VPEs and founders without one. Four decisions, no generic engineering survey:

Are we delivering at the right throughput? — DORA 4 metrics + bottleneck identification (where work waits)
How do we scale the eng hiring funnel? — funnel math + pipeline gap + time-to-fill discipline
What's our team structure — and when do we add a tech-lead manager? — squad/tribe/chapter design + manager-trigger
What's our production discipline? — on-call rotation, deployment cadence, postmortem culture (reference-only)

This skill is NOT a CTO skill. CTO owns what to build (architecture, scaling cliffs, build-vs-buy). VPE owns how to ship it reliably (delivery, hiring, team structure, production operations). At early stage these are often the same person; at scale they're distinct roles.

This skill is NOT a cs-engineering-lead replacement. Engineering-lead owns day-to-day incident and on-call coordination. VPE owns the operating model that engineering-lead executes.