Back to Details

validate-skill-coverage

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Validate Skill Coverage

验证Skill覆盖范围

Overview

概述

Meta-skill that audits the skills index against product development lifecycle phases. Identifies which phases are well-covered, which have gaps, and how skills are distributed across the lifecycle. Outputs a coverage report directly in the conversation.
这是一项Meta-skill，用于对照产品开发生命周期各阶段审计skills index。它会识别哪些阶段覆盖完善、哪些存在缺口，以及技能在生命周期中的分布情况，并直接在对话中输出覆盖范围报告。

Workflow

工作流程

  1. Read the skills index — Read 
    skills/skills-index.yaml
    to get the full list of registered skills with their categories, tiers, and descriptions.
  2. Read individual skill files — For each skill in the index, read its 
    SKILL.md
    to understand what lifecycle phase(s) it covers. Note the skill's tier (Tier 1 = daily driver, Tier 2 = important, Tier 3 = reference/stack-specific).
  3. Define lifecycle phases — Map skills against these standard product development phases:
    • Discovery: User research, JTBD analysis, feedback synthesis
    • Definition: PRD writing, user stories, requirements
    • Design: API design, data modeling, experiment design
    • Planning: Estimation, backlog scoring, sprint planning
    • Implementation: Coding patterns, code review, commit messages
    • Testing: Test plans, test coverage validation, testing patterns
    • Release: Release checklists, release notes, rollback plans
    • Operations: Incident reports, debugging, security audits
    • Evaluation: Metrics analysis, decision logging, research synthesis
    • Governance: ADRs, RFCs, tech debt management
  4. Generate the coverage matrix — For each phase, list: (a) skills that cover it, (b) the tier of each skill, (c) whether the coverage is complete or partial.
  5. Identify gaps — Flag phases with no skills or only Tier 3 (reference) coverage. Prioritize gaps by impact: phases that every team needs (implementation, testing) are higher priority than niche phases.
  6. Assess distribution — Check for imbalances: too many skills in one phase (redundancy), missing Tier 1 skills for critical phases, or Tier 3 skills without corresponding Tier 1/2 foundations.
  7. Report in conversation — Present the coverage matrix, gap analysis, and recommendations directly in the conversation. Do not write a file.
  1. 读取skills index — 读取
    skills/skills-index.yaml
    文件，获取所有已注册技能的完整列表，包括它们的分类、层级（Tier）和描述。
  2. 读取单个技能文件 — 针对索引中的每个技能，读取其
    SKILL.md
    文件，以了解它覆盖哪些生命周期阶段。记录技能的层级（Tier 1 = 日常必备工具，Tier 2 = 重要技能，Tier 3 = 参考/特定技术栈技能）。
  3. 定义生命周期阶段 — 将技能与以下标准产品开发阶段进行映射：
    • 发现阶段（Discovery）：用户研究、JTBD分析、反馈整合
    • 定义阶段（Definition）：PRD撰写、用户故事、需求梳理
    • 设计阶段（Design）：API设计、数据建模、实验设计
    • 规划阶段（Planning）：工作量估算、待办事项评分、迭代规划
    • 实施阶段（Implementation）：编码模式、代码评审、提交信息规范
    • 测试阶段（Testing）：测试计划、测试覆盖验证、测试模式
    • 发布阶段（Release）：发布检查清单、发布说明、回滚计划
    • 运维阶段（Operations）：事件报告、调试、安全审计
    • 评估阶段（Evaluation）：指标分析、决策记录、研究整合
    • 治理阶段（Governance）：ADR、RFC、技术债务管理
  4. 生成覆盖矩阵 — 针对每个阶段，列出：(a) 覆盖该阶段的技能，(b) 每个技能的层级，(c) 覆盖是否完整或部分。
  5. 识别缺口 — 标记出没有技能覆盖或仅拥有Tier 3（参考级）技能覆盖的阶段。根据影响程度对缺口进行优先级排序：所有团队都需要的阶段（如实施、测试）优先级高于小众阶段。
  6. 评估分布情况 — 检查是否存在失衡情况：某一阶段技能过多（冗余）、关键阶段缺少Tier 1技能、或Tier 3技能没有对应的Tier 1/2基础技能支撑。
  7. 在对话中生成报告 — 直接在对话中呈现覆盖矩阵、缺口分析和建议。请勿生成文件。

Output

输出

  • Format: Coverage report delivered in the conversation (no file written)
  • Key sections: Coverage Matrix (phase x skill table), Gap Analysis (uncovered phases ranked by priority), Distribution Assessment (tier balance), Recommendations (suggested new skills to fill gaps)
  • 格式：在对话中交付覆盖范围报告（不生成文件）
  • 核心板块：覆盖矩阵（阶段×技能表格）、缺口分析（按优先级排序的未覆盖阶段）、分布评估（层级平衡情况）、建议（填补缺口的推荐新技能）

Anti-patterns

反模式

  • Treating all gaps equally — A missing "sprint planning" skill is lower priority than a missing "security audit" skill. Prioritize gaps by risk and frequency of need.
  • Ignoring tier balance — A phase covered only by Tier 3 reference skills lacks the opinionated guidance that Tier 1/2 skills provide. Flag this as partial coverage, not full coverage.
  • Static analysis only — Coverage on paper does not mean coverage in practice. Note if skills exist but are likely underused (e.g., too complex, too niche).
  • Recommending skills for every gap — Not every gap needs a skill. Some phases are better served by external tools, team processes, or existing documentation. Recommend skills only where agent assistance adds clear value.
  • 对所有缺口一视同仁 — 缺少“迭代规划”技能的优先级低于缺少“安全审计”技能的优先级。应根据风险和需求频率对缺口进行优先级排序。
  • 忽略层级平衡 — 仅由Tier 3参考级技能覆盖的阶段缺少Tier 1/2技能所提供的指导性意见。需将此标记为部分覆盖，而非完全覆盖。
  • 仅进行静态分析 — 纸面的覆盖情况并不等同于实际应用中的覆盖情况。如果技能存在但可能未被充分使用（例如过于复杂、过于小众），需对此进行说明。
  • 为每个缺口都推荐技能 — 并非每个缺口都需要技能填补。有些阶段通过外部工具、团队流程或现有文档就能更好地满足需求。仅当Agent协助能带来明确价值时，才推荐技能。