vpe-review

Interrogates engineering plans using six VP of Engineering forcing questions on delivery, hiring, and structure.

25.3k|3.6k|Updated Oct 19, 2025
One-click install
npx skills add https://github.com/alirezarezvani/claude-skills --skill vpe-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vpe-review
Source: https://github.com/alirezarezvani/claude-skills/tree/main/c-level-agents/skills/vpe-review
Command: npx skills add https://github.com/alirezarezvani/claude-skills --skill vpe-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Engineering leaders often commit to delivery plans, hiring waves, or team restructures without pressure-testing throughput, DORA metrics, hiring funnel health, or production discipline. This Skill applies a throughput-first VP of Engineering interrogation to any plan before commitment.

Core Features & Use Cases

  • Six Forcing Questions: Systematically probes cycle time, DORA performance levels, hiring funnel leaks, team structure ratios, production discipline maturity, and the VPE-vs-CTO split.
  • Deterministic Analysis Scripts: Runs delivery throughput, hiring funnel, and team structure calculators to ground the review in data.
  • Structured Verdict Output: Produces a markdown review with SHIP, SHARPEN, or BLOCK verdicts plus concrete next steps.
  • Use Case: Before approving a quarterly delivery commitment or an engineering hiring plan, run the review to identify the bottleneck stage, weakest funnel conversion, and whether manager or director triggers have fired.

Quick Start

Ask the AI to run a VPE review on your engineering hiring plan, including DORA metrics analysis and team structure recommendations.

Frequently Asked Questions about vpe-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review an engineering hiring plan before approving it?

Run the VPE review on the hiring plan to analyze funnel conversion by stage, identify the weakest stage, and compute the pipeline gap. It flags when offer-to-accept rates fall below 70 percent, indicating compensation or closing discipline problems.

What are DORA metrics and how do I measure them?

DORA metrics are Deployment Frequency, Lead Time for Changes, Mean Time to Recovery, and Change Failure Rate. The review classifies each as Elite, High, Medium, or Low, and the worst metric defines the overall performance level.

When should a startup hire a VP of Engineering separately from the CTO?

Hire a separate VPE when the CTO spends more than 50 percent of time on management rather than strategy, or when the CTO is a strategy-focused co-founder. Below roughly 20 engineers, one person can cover both roles.

What team structure ratios indicate healthy engineering organization?

Healthy structures have 5-9 individual contributors per squad, 5-8 ICs per engineering manager, and 4-6 EMs per director. The manager trigger fires when 5 or more ICs lack a dedicated EM, and the director trigger fires when 3 or more EMs report directly to the VPE or CTO.

Why is my sprint velocity dropping even though the team works hard?

Dropping velocity usually signals a cycle time bottleneck rather than effort problems. Decompose lead time into stages to find where work waits, since the stage consuming the largest share of cycle time is the fix priority.