alirezarezvani/vpe-review
c-level-advisor/c-level-agents/skills/vpe-review/SKILL.md
/cs:vpe-review <plan> — Throughput-first VP of Engineering interrogation of any plan that touches delivery, eng hiring, team structure, or production discipline. Use when cycle time balloons, DORA metrics slide, or before committing to an eng hiring wave or a reorg.
$ install --global
skillsauthnpx skillsauth add alirezarezvani/claude-skills vpe-reviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 13, 2026, 4:12 AM32.5s1 file scanned
SKILL.md
- name:
- vpe-review
- description:
- /cs:vpe-review <plan> — Throughput-first VP of Engineering interrogation of any plan that touches delivery, eng hiring, team structure, or production discipline. Use when cycle time balloons, DORA metrics slide, or before committing to an eng hiring wave or a reorg.
/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 close discipline is weak
4. Is the team structure healthy for the headcount?
5-9 ICs per squad; 5-8 ICs per EM; 4-6 EMs per director.
- Run
eng_team_structure_designer.py - Manager-trigger fires when 5+ ICs have no dedicated EM
- Director-trigger fires when 3+ EMs report directly to VPE/CTO
5. What's the production discipline maturity?
Level 1-5; aim for Level 3 at growth stage.
- On-call rotation ≥ 6 people
- Severity-defined incident response with blameless postmortems
- SLOs on customer-facing services (pair with
engineering/slo-architect/) - Continuous deployment OR scheduled — not "usually one, sometimes the other"
6. Are we adding a VPE separately, or is CTO doing both?
If CTO is spending > 50% on management vs strategy, VPE is needed.
- Or: VPE complement when CTO is co-founder more comfortable with strategy
- VPE owns operating model; CTO owns architecture
- At small scale (< 20 eng), one person can do both
Workflow
# 1. Delivery throughput
python ../../../skills/vpe-advisor/scripts/delivery_throughput_analyzer.py sprint_metrics.json
# 2. Hiring funnel
python ../../../skills/vpe-advisor/scripts/eng_hiring_funnel_calculator.py funnel.json
# 3. Team structure
python ../../../skills/vpe-advisor/scripts/eng_team_structure_designer.py team.json
Output Format
# VPE Review: <plan>
**Date:** YYYY-MM-DD
## The Decision Being Made
[throughput | hiring | structure | production | VPE-vs-CTO]
## Delivery Throughput (if applicable)
- DORA overall: Elite / High / Medium / Low
- Worst metric: <DF | LT | MTTR | FR>
- Bottleneck: <stage> (X% of cycle time)
- Top fix: <action + owner>
## Hiring Funnel (if applicable)
- End-to-end conversion: X%
- Weakest stage: <stage>
- Pipeline gap: +N candidates needed
- Top fix: <specific action>
## Team Structure (if applicable)
- Recommended: <informal pods / squads / tribes>
- Manager trigger fired: yes/no
- Director trigger fired: yes/no
- Action: <hire EM | hire director | split squad>
## Production Discipline (if applicable)
- Current maturity level: 1-5
- Next practice to add: <specific>
- SLO coverage: X / Y services
## Verdict
🟢 SHIP | 🟡 SHARPEN | 🔴 BLOCK
## Next Steps
[3 concrete actions]
Routing
/cs:cto-review— for architectural causes of throughput problemscs-chro-advisoragent — for hiring funnel comp/leveling issues/cs:cfo-review— for cost-per-hire envelope and eng budget/cs:ciso-review— for production discipline + compliance overlap/cs:decide— log the verdict/cs:freeze 30— on multi-year hiring commitments
Related
- Agent:
cs-vpe-advisor - Skill:
vpe-advisor - Adjacent:
../../../../engineering/slo-architect/,../../../../engineering/feature-flags-architect/,../../../../engineering/chaos-engineering/
Version: 1.0.0
Related Skills
alirezarezvani/weekly-review
development
VerifiedTrustedCommunity
Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says "/cs:weekly-review". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.
22,702SKILL.mdUpdated Jul 18, 2026
alirezarezvani/meetings
development
VerifiedTrustedCommunity
Use when someone wants to decide whether a meeting is worth calling, price a meeting in dollars, build a timeboxed agenda with desired outcomes, or turn messy meeting notes into owned action items — or says "should this be a meeting", "/cs:meeting-prep", or "/cs:meeting-actions". Runs a cost gate (ASYNC / NOT-READY / MEET), builds a decision-first agenda, and extracts an owner + due-date checklist that flags every orphan.
22,702SKILL.mdUpdated Jul 18, 2026
alirezarezvani/fable-goal
development
VerifiedTrustedCommunity
Convert a rambling description of a desired outcome into one polished, autonomous /goal prompt ready to paste into a fresh session. Use when the user says "/fable-goal", "turn this into a goal prompt", "write me a fable prompt", "write the prompt that builds X", or rambles about something they want made and asks for the prompt that makes it happen. The output is a single copy-paste prompt, never the build itself. Do NOT use when the user wants the thing built right now in this session — only when they want the PROMPT that will make it happen in a fresh session.
22,702SKILL.mdUpdated Jul 18, 2026
alirezarezvani/deep-work
development
VerifiedTrustedCommunity
Use when someone wants to plan a deep work day, time-block their calendar or task list, budget or cut shallow work, protect focus hours, track deep-work sessions and streaks, run an end-of-day shutdown ritual, or says "/deep-work" or "/time-block". Classifies tasks deep vs shallow, builds an energy-first time-blocked schedule that refuses deep demand past the 4-hour ceiling, batches shallow work into at most two windows, and logs focus sessions against a weekly target.
22,702SKILL.mdUpdated Jul 18, 2026