菜单
One clear sentence on what this skill does AND when Claude should use it. Include the trigger words a user would actually type (e.g. "readiness score", "spec review"), because this description is the only thing Claude sees when deciding whether to load the skill.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Review generated feature specs (Gherkin, NFRs, evaluation criteria) before GovKit execution. Use for refinement conversations where Product, QA, and Engineering improve a draft together before AI-assisted coding starts. Tool-agnostic; works with any generator (e.g. Aha!) and any tracker (e.g. Azure DevOps, Jira). Trigger whenever the user mentions Gherkin, acceptance criteria, feature refinement, 3 Amigos, Draft 0, Development Token, spec review, PM pre-review, QA evidence review, or asks to review, score, or rewrite a feature spec before coding begins — even if they don't name GovKit explicitly.
Generate synthetic test data for a GovKit feature package using Python Faker — a seeded, repeatable generator script plus committed data files derived from the feature's Gherkin scenarios. Use whenever the user asks to "generate test data", "create synthetic data", "seed data", "fixtures", "fake data", "sample records", or "load-test data" for a feature, work item, or acceptance.feature — even if they don't say GovKit or Faker. Also use after a feature package passes readiness and the team needs data to exercise the scenarios. Works for any target stack; only the generator itself is Python.
Emit structured Tier 1 metric events (NDJSON) from a GovKit-governed repository's exhaust — feature packages, .govkit/marker.json, eval_criteria.yaml, CI gate runs, PR exports, and git history. Use this skill whenever the user wants to compute, emit, export, or audit delivery/quality metrics from a GovKit repo: spec completeness scores, gate-readiness audits, metric event streams for an aggregator, velocity/quality pair inputs, or "which features aren't gate-ready." Trigger on mentions of GovKit metrics, metric events, telemetry emission, feature package audit, spec completeness, or AIPOS Tier 1 metrics — even if the user doesn't name this skill.
| name | govkit-skill-name |
| description | One clear sentence on what this skill does AND when Claude should use it. Include the trigger words a user would actually type (e.g. "readiness score", "spec review"), because this description is the only thing Claude sees when deciding whether to load the skill. |
What this skill helps a team do, in one or two sentences.
Step-by-step guidance Claude follows when this skill is active.
