CtrlK
BlogDocsLog inGet started
Tessl Logo

product-feature-tech-implement

基于功能设计文档与现有源码,端到端实现一个产品功能:开发、代码 review、测试用例编写与执行, 循环迭代直到测试通过,最终产出用户手册与实现总结文档(保存到当前项目 markdown/ 目录)。 触发条件:用户提供了功能设计文档(PRD/设计文档/需求描述)+ 源码目录(或代码库路径), 并希望"实现这个功能"、"开发这个功能"、"把这个设计文档变成代码"、"做这个功能的开发+测试"、 "完整实现并测试"、"端到端开发",或明确要求按"开发-review-测试"循环推进直到测试通过。 也适用于需要额外运行环境的开发任务,例如 PostgreSQL/MySQL 等数据库插件开发 (可能需要编译、搭建实例、配置参数、初始化、跑测试)、需要启动服务进程才能测试的后端功能、 需要特定运行时环境的库或框架功能。 即使用户只是说"帮我把这个功能做出来"、"按设计文档实现一下"、"这个功能开发完了麻烦测试一下", 但同时给出了设计文档和代码路径,也应使用本 skill。 本 skill 的核心是严格的"开发 ⇄ Review"循环 + "测试者不预先看代码"的盲测试原则, 因此当用户提到"独立测试"、"测试不能看代码"、"先写测试用例再看代码"、"black-box 测试"时, 也应优先使用本 skill。 不适用于:只是要求"写一个脚本"、"改一行代码"、"快速修一个 bug"等轻量级、 无需走完整开发-review-测试闭环的任务;也不适用于纯粹的代码评审(无需新开发功能) 或纯粹的测试用例编写(无设计文档、无需开发)这类单一环节请求—— 这些更适合直接处理而非套用本 skill 的完整闭环流程。

66

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/skills_for_claude_web/product_feature_tech_implement/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

62%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.

The workflow is modeled with unusual clarity — an explicit state machine, validation checkpoints, feedback loops, and escalation criteria — but the body is verbose and leans on referenced agents/ files that are absent from the bundle, undermining both actionability and navigation.

Suggestions

Add the missing agents/developer.md, agents/reviewer.md, agents/tester.md files referenced in the "角色说明" section, or inline the essential per-role input/output contracts so the skill is self-contained.

Tighten the rationale sections ("为什么要盲测试", the no-sub-agent environment narrative) to bullet points or a few sentences — the core principle can be conveyed without the conversational elaboration.

Move the detailed PostgreSQL environment-setup content fully into references/postgres-extension.md (already started) and keep only a one-line pointer in the body, reducing inline environment discussion.

DimensionReasoningScore

Conciseness

Mostly efficient operational guidance, but conversational padding and elaborated rationale ("为什么要盲测试", "诚实面对这个限制", "硬着头皮空转") add tokens that could be tightened without losing the skill-specific insight.

3 / 5

Actionability

Provides a concrete state machine, a state-file JSON schema, file-naming conventions, and stopping criteria, but delegates core per-role execution to an "agents/" directory whose files (developer.md, reviewer.md, tester.md) are not present in the bundle, leaving key execution details unfulfilled.

3 / 5

Workflow Clarity

A clear state-machine diagram sequences 循环 A (dev⇄review until pass) → tester → on test-fail back to 循环 A → on pass to docs, with explicit validation verdicts (review/test 通过/未通过), feedback loops, and a four-item "何时该向用户求助" escalation checklist.

5 / 5

Progressive Disclosure

Section structure is reasonable and references/postgres-extension.md exists as a clean one-level-deep reference, but the three referenced agents/*.md files do not exist in the bundle, breaking navigation to the core per-role detail that the body explicitly defers to them.

3 / 5

Total

14

/

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, well-scoped description that clearly states what the skill does and when to use it, with rich natural trigger phrasing and explicit boundary guidance. Voice is appropriately third-person/imperative throughout.

DimensionReasoningScore

Specificity

Lists several concrete actions — "开发、代码 review、测试用例编写与执行,循环迭代直到测试通过,最终产出用户手册与实现总结文档" — with good coverage of the dev-review-test loop, though a couple of items ("开发") are phase-level rather than fine-grained operations.

4 / 5

Completeness

Explicitly answers both "what" (end-to-end implement: dev, review, test, iterate until pass, produce docs) and "when" via a dedicated "触发条件" section with concrete trigger phrases plus a "不适用于" negative-scope section.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases users would actually say, including casual variants — "实现这个功能", "把这个设计文档变成代码", "帮我把这个功能做出来", "这个功能开发完了麻烦测试一下", "black-box 测试" — covering synonyms and informal phrasings.

5 / 5

Distinctiveness Conflict Risk

Carves a clear niche — strict dev⇄Review loop with blind-testing — and explicitly excludes adjacent single-purpose requests (pure code review, pure test writing, quick bug fixes), minimizing overlap with generic coding skills.

5 / 5

Total

19

/

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.