CtrlK
BlogDocsLog inGet started
Tessl Logo

tapd-story-clarification

TAPD 需求澄清技能。从 TAPD 提取"规划中"状态的需求,按照研发最佳实践对需求进行 多维度澄清(业务逻辑、外部系统交互、上下文),整合项目背景知识,输出符合需求文档 规范的标准化 Markdown 需求文档,并回写 TAPD。 Use this skill whenever the user mentions 需求澄清, 澄清需求, clarify story, clarify requirement, 需求细化, 需求整理, 需求规范化, 补充需求, 完善需求描述, story clarification, requirement clarification, 需求文档整理, or any workflow involving TAPD story description refinement and standardization.

74

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 process skill: fully concrete MCP orchestration with exact parameters, a DoR validation gate wired into the write-back state decision, feedback loops for failures, and clean one-level reference structure. The only notable issue is mild redundancy around the DoR/v_status rule, plus a minor inconsistency between the description's "规划中" status label and the body's backlog v_status values.

DimensionReasoningScore

Conciseness

The body is dense procedural instruction with no re-teaching of concepts Claude knows (5W1H, BDD details are correctly delegated to references). However, there is minor redundancy: the v_status/DoR rule is restated in §2.4, §2.6, and 产出, and the closing 参考文件 table duplicates the inline reference pointers. Efficient with minor trims possible — anchor 4, not 5.

4 / 5

Actionability

Fully actionable for an MCP-orchestration skill: exact call parameter blocks for stories_get/stories_update (workspace_id, id, with_v_status, v_status, description source), workspace_id priority resolution order, concrete file-naming rules with a 4-row example table, the docs/reqs/ save path with a 5-step flow, and an error-handling table covering all failure modes. Specific examples cover the common cases; not 4 since there are no real gaps in executable guidance.

5 / 5

Workflow Clarity

Clear §1 → §2.1–2.6 → §3 sequence processed per-requirement, with an explicit validation checkpoint (DoR 8-item gate in §2.4), a conditional fail-path (keep v_status: backlog, annotate in summary), a retry-once feedback loop on write-back failure, and an iterate-until-satisfied user-confirmation loop (§2.5). Batch operations have validation, so the workflow-clarity cap does not apply; this matches the validate → fix → only-proceed-when-valid anchor.

5 / 5

Progressive Disclosure

SKILL.md is a process overview pointing to three real, one-level-deep reference files, each clearly signaled inline ("执行前必读") and summarized in a 参考文件 table with purpose and when-to-read columns. Verified all three files exist and the §-cited sections (§一, §二, §四, §五 in clarification-guide.md) match actual headers. Clear overview with well-signaled references — anchor 5.

5 / 5

Total

19

/

20

Passed

Description

96%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 description: it states a complete what (extract → clarify → integrate → generate doc → write back) with named clarification dimensions and an explicit bilingual trigger clause covering synonyms. The only weakness is that a few English trigger terms are not TAPD-qualified, creating slight overlap risk with generic story-refinement skills.

DimensionReasoningScore

Specificity

The description chains five concrete actions: "从 TAPD 提取'规划中'状态的需求", "多维度澄清(业务逻辑、外部系统交互、上下文)", "整合项目背景知识", "输出…标准化 Markdown 需求文档", "并回写 TAPD". Coverage is comprehensive with named clarification dimensions, matching the multiple-specific-concrete-actions anchor rather than the minor-gaps anchor below it.

5 / 5

Completeness

It explicitly answers both questions: the what (extract, multi-dimension clarify, integrate context, output standardized doc, write back to TAPD) and the when via "Use this skill when the user mentions…" with concrete trigger phrases. Matches the anchor-5 example structure; not 4 because the when-clause is explicit, not merely present.

5 / 5

Trigger Term Quality

Extensive natural synonym coverage in both user languages: 需求澄清, 澄清需求, 需求细化, 需求整理, 需求规范化, 补充需求, 完善需求描述, clarify story, clarify requirement, story clarification, requirement clarification, plus "any workflow involving TAPD story description refinement". This matches the comprehensive-synonyms anchor; not 4, since no common variation a user would say is obviously missing.

5 / 5

Distinctiveness Conflict Risk

The TAPD-anchored niche (TAPD 需求澄清, TAPD story description) is mostly distinct, but unqualified English triggers like "clarify story" and "story clarification" could fire for generic (non-TAPD) user-story refinement workflows, giving minor overlap risk with closely related skills — the anchor-4 case rather than clear-niche minimal conflict.

4 / 5

Total

19

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository
TencentBlueKing/bk-bcs
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.