/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.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
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 ../../../c-level-advisor/skills/vpe-advisor/scripts/delivery_throughput_analyzer.py sprint_metrics.json
# 2. Hiring funnel
python ../../../c-level-advisor/skills/vpe-advisor/scripts/eng_hiring_funnel_calculator.py funnel.json
# 3. Team structure
python ../../../c-level-advisor/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 problemscs-chro-advisor agent — 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
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Accessibility audit skill for scanning, fixing, and verifying WCAG 2.2 Level A and AA compliance across React, Next.js, Vue, Angular, Svelte, and plain HTML codebases. Use when auditing accessibility, fixing a11y violations, checking color contrast, generating compliance reports, or integrating accessibility checks into CI/CD pipelines.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.
日本語の概要は準備中です。原文の説明を表示しています。
When the user needs to generate, iterate, or scale ad creative for paid advertising. Use when they say 'write ad copy,' 'generate headlines,' 'create ad variations,' 'bulk creative,' 'iterate on ads,' 'ad copy validation,' 'RSA headlines,' 'Meta ad copy,' 'LinkedIn ad,' or 'creative testing.' This is pure creative production — distinct from paid-ads (campaign strategy). Use ad-creative when you need the copy, not the campaign plan.
日本語の概要は準備中です。原文の説明を表示しています。
Adversarial code review that breaks the self-review monoculture. Use when you want a genuinely critical review of recent changes, before merging a PR, or when you suspect Claude is being too agreeable about code quality. Forces perspective shifts through hostile reviewer personas that catch blind spots the author's mental model shares with the reviewer.
日本語の概要は準備中です。原文の説明を表示しています。
Answer Engine Optimization (AEO) skill — optimize content to be cited by AI language models (ChatGPT, Perplexity, Claude, Gemini, Mistral) as authoritative sources. Distinct from SEO — AEO optimizes for citation in LLM-generated responses, not search rankings. Use when planning content for AI-first search audiences, auditing existing content for E-E-A-T signals, tracking which pages get cited by which LLMs, or building a citation-friendly content strategy. Triggers — 'AEO audit', 'optimize for ChatGPT', 'get cited by Perplexity', 'LLM citation strategy', 'answer engine optimization', 'content for AI search', 'E-E-A-T audit'. Output is a markdown audit report (default) or JSON for pipeline integration. Stdlib-only Python tools.
日本語の概要は準備中です。原文の説明を表示しています。
Mint a tamper-evident, post-quantum-signed receipt for a consequential agent action (deploy, delete, pay, grant-access, model decision) so it can be verified later from the certificate alone. Use when an autonomous agent takes a side-effecting action that may need to be proven later, or when satisfying EU AI Act Article 12 record-keeping. Three decisions: whether an action needs a receipt, minting it, verifying it. Signing is delegated to the open-source OpenAgentOntology package. Not after-the-fact log analysis; not a hosted notary; not a legal opinion.
日本語の概要は準備中です。原文の説明を表示しています。