product-feature-tech-implement

基于功能设计文档(由 product-feature-tech-design 产出或等价输入)、源码目录、以及测试所依赖的环境信息(例如 PostgreSQL 插件开发需要的 PG 源码/实例、第三方依赖),编排「开发者 ↔ 评审者 ↔ 测试者」三方隔离的实施循环,直至评审通过、且所有测试(新增 + 已有)通过。三方互不可见,测试者绝对不能看到开发者写的代码。完成后输出 markdown 总结报告到当前项目的 `markdown/` 目录。适用于:实施功能设计文档、按设计稿开发并自验证、闭环式开发流程、PostgreSQL 插件/扩展开发、需要 build + 部署 + 跑测的工程项目、TDD 式实施循环。

Quality

84%

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-engineered orchestration skill body: the three-party loop is sequenced with explicit validation checkpoints, feedback loops, anti-infinite-loop guards, and a delivery checklist, with detailed prompts correctly split into existing one-level-deep references. It is only marginally held back by mild redundancy of the isolation constraint and prompts living in references rather than inline.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Claude's intelligence (no explanations of what review/TDD/subagents are), but the critical 'tester cannot see code' constraint is restated in 核心约束, the role-contract table, and the QA checklist — useful emphasis yet slightly redundant, placing it just below the lean 5.	4 / 5
Actionability	Concrete, actionable specifics abound — exact input tables, role can/cannot-see contracts, report path templates ('markdown/<topic>-review-<round>-<YYYYMMDD>.md'), verdict strings ('verdict: pass'), and anti-loop thresholds — but the executable subagent prompts themselves live in referenced files rather than inline, so it is mostly rather than fully executable.	4 / 5
Workflow Clarity	The ASCII flow diagram sequences loop A in 7 numbered steps with explicit exit conditions for loop A and the overall process, validation checkpoints ('review 通过?', '测试通过?'), feedback loops (fail → back to dev), a 3-round anti-infinite-loop escalation, and a delivery QA checklist — matching the 'clear sequence with explicit validation, feedback loops, and checklists' anchor.	5 / 5
Progressive Disclosure	The body is an orchestration overview that cleanly offloads the four detailed subagent prompts/templates to one-level-deep references (developer-prompt.md, reviewer-prompt.md, tester-prompt.md, summary-template.md), all of which exist and are clearly signaled both inline and in the 参考资料 section, matching the 'clear overview with well-signaled one-level-deep references' anchor.	5 / 5
	Total	18 / 20 Passed

Description

83%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, third-person description that clearly states both capability and trigger conditions with concrete, mostly natural trigger terms. The only weakness is a couple of broadly-scoped applicability triggers that raise minor conflict risk with generic engineering/TDD skills.

Dimension	Reasoning	Score
Specificity	Names the domain (three-party isolated dev loop) and several concrete actions — '编排...实施循环', '评审通过、且所有测试(新增 + 已有)通过', '输出 markdown 总结报告到...markdown/ 目录' — with only minor coverage gaps, fitting the 'lists several specific actions' anchor rather than the fully comprehensive 5.	4 / 5
Completeness	Explicitly answers 'what' (orchestrates the three-party isolated loop until review+tests pass, emits a markdown summary) and 'when' via the concrete '适用于:' trigger list, matching the 'clearly and explicitly answers both what AND when with concrete trigger phrases' anchor; voice is third person, so no cap applies.	5 / 5
Trigger Term Quality	The '适用于:' clause surfaces natural user phrases — '实施功能设计文档', 'TDD 式实施循环', 'PostgreSQL 插件/扩展开发', '闭环式开发流程' — with some synonyms (插件/扩展), but not the full synonym-and-extension coverage of a 5.	4 / 5
Distinctiveness Conflict Risk	The three-party isolated loop and PG-plugin niche are highly distinct, but the broader triggers '需要 build + 部署 + 跑测的工程项目' and 'TDD 式实施循环' create minor overlap with general engineering/TDD skills, placing it just below the minimal-conflict 5.	4 / 5
	Total	17 / 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-implement/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.