Conciseness

The body is dense and expert-specific throughout with no padding about concepts Claude already knows, but at ~22KB it duplicates material already in the bundle (the Receipts quotes reappear in references/quotes.md, and play tactics overlap references/frameworks.md), so it could be tightened.

Actionability

Fully actionable instruction-only content: specific diagnostic questions with routing rationale, a situation-to-play routing table, numbered tactics with concrete numbers (five-day rule, one blocking approver, six-week ceiling, 10% working version), a paste-ready deliverable template, and a grading rubric with explicit 1/3/5 anchors.

Workflow Clarity

Clear multi-step sequence (Diagnose -> Pick the play -> Run it) with explicit validation checkpoints: 'State your diagnosis in one sentence before you recommend anything... If you cannot, you are guessing', 'If you cannot name the top priority, stop here and run Play D', per-play 'Done when' criteria, and stability guardrails in the deliverable.

Progressive Disclosure

Good structure with real, clearly signaled one-level-deep references (references/frameworks.md and references/quotes.md both exist and are described in 'Go deeper'), but some content duplicated between the inline plays/quotes and the reference files keeps the split from being clean.

Specificity

Lists multiple concrete outputs ('a baseline, a bottleneck map, the top 3 interventions and a stop-doing list') with comprehensive coverage, but uses second person ('your product team', 'Use it when you say') which the guidelines penalize by 1 on specificity.

Completeness

Explicitly answers both what ('Diagnoses why your product team ships slowly and produces a velocity plan with a baseline, a bottleneck map, the top 3 interventions and a stop-doing list') and when ('Use it when you say...') with concrete trigger phrases.

Trigger Term Quality

Comprehensive natural trigger phrases users would actually say ('we're too slow', 'how do we ship faster', 'projects keep slipping', 'too many meetings', 'approvals take forever', 'our releases are scary', 'velocity', 'cycle time', 'we hired more people and nothing got faster', 'AI made coding fast but we still ship slowly') including synonyms and AI-era variations.

Distinctiveness Conflict Risk

Clear niche in product-team shipping velocity, but triggers like 'too many meetings', 'velocity' and 'cycle time' carry minor overlap risk with closely related meetings or metrics skills; the description does not disambiguate against them.