vpe-advisor
VP of Engineering advisory for startups: delivery throughput (DORA 4 metrics + bottleneck identification), engineering hiring funnel (sourcing → screen → onsite → offer conversion + time-to-fill + pipeline gap), engineering team structure (squad/tribe/chapter design + tech-lead manager-trigger thresholds), and production discipline (on-call, deployment cadence, postmortem culture). Use when sprint velocity is dropping, eng hiring is broken, team structure is unclear, or deciding when to add a tech-lead manager. NOT a CTO skill (which owns architecture) — VPE owns delivery operations and how th
Profile →npx skills add alirezarezvani/claude-skills --skill vpe-advisor --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# VP of Engineering Advisor Strategic engineering operations leadership for startup VPEs and founders without one. **Four decisions, no generic engineering survey:** 1. **Are we delivering at the right throughput?** — DORA 4 metrics + bottleneck identification (where work waits) 2. **How do we scale the eng hiring funnel?** — funnel math + pipeline gap + time-to-fill discipline 3. **What's our team structure — and when do we add a tech-lead manager?** — squad/tribe/chapter design + manager-trigger 4. **What's our production discipline?** — on-call rotation, deployment cadence, postmortem culture (reference-only) This skill is **NOT a CTO skill**. CTO owns *what to build* (architecture, scaling cliffs, build-vs-buy). VPE owns *how to ship it reliably* (delivery, hiring, team structure, production operations). At early stage these are often the same person; at scale they're distinct roles. This skill is **NOT a cs-engineering-lead replacement**. Engineering-lead owns day-to-day incident and on-call coordination. VPE owns the operating model that engineering-lead executes. ## Keywords VPE, VP of Engineering, VP Engineering, engineering operations, delivery throughput, DORA, deployment
- Keywords
- Quick Start
- Key Questions (ask these first)
- Core Responsibilities
- 1. Delivery Throughput (DORA Metrics)
- 2. Engineering Hiring Funnel
- 3. Engineering Team Structure
- 4. Production Discipline
- Workflows
- Workflow 1: Quarterly Delivery Health Review (4 hours)
- Workflow 2: Hiring Funnel Diagnosis (1 day)
- Workflow 3: Team Structure Audit (1 day)
- Workflow 4: Production Discipline Audit (1 week)
- Output Standards
Decision A: DORA 4 metrics + bottleneck identification python scripts/delivery_throughput_analyzer.py # embedded sprint sample python scripts/delivery_throughput_analyzer.py path/to/sprint_metrics.json Decision B: Hiring funnel health + pipeline gap python scripts/eng_hiring_funnel_calculator.py # embedded 3-quarter sample python scripts/eng_hiring_funnel_calculator.py path/to/funnel.json Decision C: Team structure recommendation + manager-trigger python scripts/eng_team_structure_designer.py # embedded 25-engineer sample python scripts/eng_team_structure_designer.py path/to/team.json python ../../skills/vpe-advisor/scripts/delivery_throughput_analyzer.py sprint_metrics.json
What does the vpe-advisor skill do?
VP of Engineering advisory for startups: delivery throughput (DORA 4 metrics + bottleneck identification), engineering hiring funnel (sourcing → screen → onsite → offer conversion + time-to-fill + pipeline gap), engineering team structure (squad/tribe/chapter design + tech-lead manager-trigger thresholds), and production discipline (on-call, deployment cadence, postmortem culture). Use when sprint velocity is dropping, eng hiring is broken, team structure is unclear, or deciding when to add a tech-lead manager. NOT a CTO skill (which owns architecture) — VPE owns delivery operations and how th
How do I install it?
Run `npx skills add alirezarezvani/claude-skills --skill vpe-advisor --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From alirezarezvani/claude-skills, a repository with 23,791 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.