CtrlK
BlogDocsLog inGet started
Tessl Logo

product-feature-tech-design

输入 PRD 文档(Markdown 或 PDF),以开发架构师的角色编写字段/接口级精度的功能设计文档(Functional/Technical Design Doc),以 Markdown 格式保存到当前项目 markdown/ 目录。这份文档是开发者、reviewer、测试者三方协作的唯一契约——三者互相隔离、不能看对方的产出物(测试者看不到代码,reviewer 不参与开发),所以必须把每个功能点写到可直接落地、可直接测试的精度:接口请求/响应字段、错误码、状态机、数据模型、异常边界场景都要明确。触发条件:用户提到"功能设计文档"、"技术设计文档"、"tech design"、"functional design"、"从 PRD 生成设计文档"、"帮我把这份 PRD 转成开发文档"、"写一份给开发和测试用的设计文档"、"接口设计 + 验收标准",或者用户上传了一份 PRD 并希望进入开发落地阶段。即使用户只说"基于这个 PRD 帮我写设计文档"或"把这个需求文档详细化成开发能直接看懂的文档",也应立即使用本 skill。不要将本 skill 与 write-prd/write-brd 混淆——那两个 skill 输出的是面向业务评审的需求文档(WHY/WHAT 层),本 skill 输出的是面向研发落地的技术设计文档(HOW 层,包含具体字段和契约),通常以 PRD 作为输入而非从零开始的 idea。

70

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%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 instruction-only skill with excellent progressive disclosure, a clear 5-step workflow, and concrete actionable field/interface-level guidance. The main drag is conciseness — the discursive rhetorical style and the recap-style self-check inflate the body without adding proportional guidance.

Suggestions

Tighten the discursive prose in Step 4 (e.g., the [待确认] business-rule vs. implementation-detail rule can be stated in 2-3 sentences instead of a paragraph of motivational framing) to lift conciseness without losing the nuance.

Either trim the '写作质量自检' section to only the items NOT already covered in Step 4, or move it fully into the template so the body doesn't re-state the same checks twice.

Add one short inline worked example of a complete interface contract (request params + response + error codes) so the guidance is copy-paste-ready rather than only described.

DimensionReasoningScore

Conciseness

Mostly efficient and substantive, but the discursive prose style ('这种专业感是假的', extended '因为…所以' framing, motivational asides) and the self-check section re-covering Step 4 material could be tightened; it leans noticeably above a lean token budget despite earning most of its length.

3 / 5

Actionability

Concrete, specific guidance throughout — '请求参数表:参数名、类型、是否必填、默认值、约束规则', named error-code categories, file naming `[product-name-en]-tech-design.md`, output to `markdown/`, and Mermaid `graph TD` — but lacks an inline worked example of a complete filled-in module, which lives only in the referenced template.

4 / 5

Workflow Clarity

A clearly sequenced 5-step workflow with an overview diagram and a terminal '写作质量自检' checklist, but validation is a single post-hoc recap rather than inter-step checkpoints, and there are no error-recovery feedback loops.

4 / 5

Progressive Disclosure

SKILL.md is an overview that pushes detail to two real one-level-deep bundle files signaled by name in prose ('详细判断标准见 references/precision-rules.md', '使用 references/module-template.md 中的模板展开'); the split is appropriate and navigation is easy.

5 / 5

Total

16

/

20

Passed

Description

100%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 densely informative description that nails all four dimensions: concrete capabilities, abundant natural triggers in both languages, explicit what/when, and proactive disambiguation from related skills. Its only weakness is verbosity — the trigger list and disambiguation could be trimmed without losing coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions at field/interface precision — '接口请求/响应字段、错误码、状态机、数据模型、异常边界场景都要明确' and '以 Markdown 格式保存到当前项目 markdown/ 目录' — giving comprehensive coverage of what the skill produces, not just the domain.

5 / 5

Completeness

Explicitly answers both 'what' (编写字段/接口级精度的功能设计文档, output to markdown/) and 'when' (a dedicated '触发条件' clause with concrete trigger phrases and an 'even if the user only says…' extension), satisfying the top anchor.

5 / 5

Trigger Term Quality

Comprehensive natural trigger coverage in both Chinese and English: '功能设计文档', '技术设计文档', 'tech design', 'functional design', '从 PRD 生成设计文档', '帮我把这份 PRD 转成开发文档', plus the upload-a-PRD scenario and informal paraphrases users would actually say.

5 / 5

Distinctiveness Conflict Risk

Actively disambiguates from sibling skills — '不要将本 skill 与 write-prd/write-brd 混淆…本 skill 输出的是面向研发落地的技术设计文档(HOW 层)' — carving a clear niche with minimal overlap risk.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
digoal/blog
Reviewed

Table of Contents

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.