Individual skill
vpe-review
Use for /c-level-agents:vpe-review, or to challenge a plan touching delivery speed, eng hiring, team structure or on-call.
c-level-agents/skills/vpe-review/SKILL.md
Source commit 9ef0c3c213932e645cc5cbeeb3c35c3a762a2437
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 29,540
- Repository last updated
- Nov 5, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agentic-ai Repository topic
- anthropic-claude Repository topic
- claude-ai Repository topic
- claude-code Repository topic
- claude-skills Repository topic
- claude-code-skills Repository topic
- ai-coding-agent Repository topic
- claude-code-plugins Repository topic
- developer-tools Repository topic
- openai-codex Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Read excerpt
# /c-level-agents:vpe-review — VPE Forcing Questions
**Command:** `/c-level-agents: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"