product-feature-tech-design

将 PRD 翻译成「可独立测试」的功能设计文档。文档的下游使用者包括开发者、评审者、测试者,且三方互相隔离(测试者看不到开发者写的代码),所以必须把行为、状态、接口、数据、权限、异常、验收标准全部显式化,让测试者能独立从文档推导用例。输入是一份已写好的 PRD 文档,输出是一份完整的 Markdown 功能设计文档,保存到当前项目的 `markdown/` 目录。适用于:写功能设计文档、技术设计文档、Tech Design、详细设计说明书、FDD、Functional Design Doc、Detailed Design、模块设计文档、把 PRD 翻译成开发设计、把需求拆成可开发/可测试/可评审的规格。

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable skill body with a clear validated workflow, strong checklist, and excellent progressive disclosure via real reference templates. The only weaknesses are minor redundancy in the contract sections and detail delegated to external templates rather than inline.

Suggestions

Dedupe the 接口规格/状态机/测试矩阵 guidance between workflow step 3 and the 给开发者/给测试者 contract sections to tighten conciseness.

Inline one small concrete example (e.g., a minimal Given/When/Then acceptance criterion or a sample error-code row) so the body is self-contained beyond the referenced templates.

Add a one-line note in the workflow stating what each reference template provides at a glance, reducing the need to open all four files to plan the work.

Dimension	Reasoning	Score
Conciseness	Efficient and free of padding about concepts Claude already knows, using a compact table and checklist; some redundancy between workflow step 3 and the 给开发者/给测试者 contract sections could be trimmed.	4 / 5
Actionability	Provides concrete, specific guidance — template file references, the filename pattern markdown/<topic>-feature-design-<YYYYMMDD>.md, Given/When/Then, and numeric thresholds (p99 ≤ 200ms) — but most executable structure is delegated to the referenced template files, a minor gap for an instruction-only skill.	4 / 5
Workflow Clarity	Six clearly sequenced steps with an explicit input guard (stop and ask if no PRD), a self-check step with a feedback loop ('如果任一项不过,补完后再交付'), and a 10-item delivery checklist; file creation is non-destructive so no cap applies.	5 / 5
Progressive Disclosure	SKILL.md is a concise overview pointing to four one-level-deep reference templates, all verified to exist and clearly signaled in both the workflow and the 参考资料 section, with content appropriately split.	5 / 5
	Total	18 / 20 Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly states what it does and when to use it, with rich bilingual trigger synonyms and a well-delineated niche. Slightly below perfect specificity only because actions are expressed as goals rather than a crisp enumerated verb list.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions (translating PRD into a testable design doc, making behavior/state/interface/data/permission/exception/acceptance explicit, deriving test cases, saving to markdown/) but they are framed partly as goals rather than a clean enumeration of discrete verbs, leaving minor gaps versus the comprehensive anchor.	4 / 5
Completeness	Explicitly answers both 'what' (translates a finished PRD into a complete Markdown functional design doc) and 'when' via the '适用于:...' clause listing concrete trigger scenarios.	5 / 5
Trigger Term Quality	Comprehensive natural-term coverage including Chinese and English synonyms (功能设计文档, 技术设计文档, Tech Design, 详细设计说明书, FDD, Functional Design Doc, Detailed Design, 模块设计文档) that users would actually say.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche — PRD-to-testable functional design with a three-isolated-party constraint — with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: digoal/blog
Path: skills/product-feature-tech-design/SKILL.md
Commit: 3b9c83d

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.