Help us improve
Share bugs, ideas, or general feedback.
From c-level-agents
/cs:vpe-review <plan> — Throughput-first VP of Engineering interrogation of any plan that touches delivery, eng hiring, team structure, or production discipline.
npx claudepluginhub kruxshnx/claude-skills-devin --plugin c-level-agentsHow this skill is triggered — by the user, by Claude, or both
Slash command
/c-level-agents:vpe-reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Command:** `/cs:vpe-review <plan>`
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Share bugs, ideas, or general feedback.
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.
No DORA, no diagnosis.
delivery_throughput_analyzer.pyOne Elite metric and three Lows = bad. Four Highs = healthy.
"Can't find good engineers" is wrong.
eng_hiring_funnel_calculator.py5-9 ICs per squad; 5-8 ICs per EM; 4-6 EMs per director.
eng_team_structure_designer.pyLevel 1-5; aim for Level 3 at growth stage.
engineering/slo-architect/)If CTO is spending > 50% on management vs strategy, VPE is needed.
# 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
# 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]
/cs:cto-review — for architectural causes of throughput problems/cs:chro-review — 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 commitmentscs-vpe-advisorvpe-advisor../../../../engineering/slo-architect/, ../../../../engineering/feature-flags-architect/, ../../../../engineering/chaos-engineering/Version: 1.0.0