vpe-reviewlisted

# /cs:vpe-review — VPE Forcing Questions **Command:** `/cs:vpe-review <plan>` The throughput-first VPE pressure-tests any plan touching eng operations. Six questions before any delivery commitment, eng hiring expansion, team restructure, or production-discipline change. ## When to Run - Before quarterly delivery commitment (sprint planning, OKR review) - Before approving an eng hiring plan - Before restructuring eng teams (splitting/merging squads, adding tribes) - Before deciding whether to hire a VPE separately from CTO (or merge them) - When production incidents are increasing - When sprint velocity is dropping but everyone says "we're working hard" ## The Six VPE Questions ### 1. What's the cycle time, and where does work wait? **No DORA, no diagnosis.** - Lead Time for Changes is the single best health metric - If you can't decompose cycle time into stages, you can't fix the bottleneck - Run `delivery_throughput_analyzer.py` ### 2. What's the DORA performance level on all 4 metrics? **One Elite metric and three Lows = bad. Four Highs = healthy.** - Deployment Frequency, Lead Time, MTTR, Change Failure Rate - The worst metric defines overall level - Fix lead time first; everything else follows ### 3. Where is the hiring funnel leaking? **"Can't find good engineers" is wrong.** - Specific stage is over-filtering OR top-of-funnel volume is too low OR offer-to-accept is broken - Run `eng_hiring_funnel_calculator.py` - If offer-to-accept < 70%, comp is below market or