CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

requirement-convergence

Separates the outcome a change must produce from the requirements proposed to reach it, records what the user excluded, and bands cost from decision-relevant repository evidence. Use when a requirement enters a workflow, before design begins.

Quality

81%

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

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 tight, well-structured instruction skill: field definitions with pass conditions, a sequenced hearing protocol with per-step validation evidence and a re-ask loop, a defined confirmation surface, and clean one-level-deep progressive disclosure into a real reference file. The only notable gap is the absence of a worked example showing a filled-in convergence record or rendered Scope Confirmation.

DimensionReasoningScore

Conciseness

The body is dense and table-driven, assumes Claude's competence, and spends no tokens on known concepts. A few abstract justification passages ('Step 2's evidence is what keeps the hearing reviewable...') could be trimmed, matching anchor 4 rather than 5.

4 / 5

Actionability

Concrete, executable guidance throughout: per-field pass conditions, a 4-step hearing protocol with completion evidence per step, a five-section Scope Confirmation shape, and a storage table naming carriers and writers. Held at 4 rather than 5 because no worked example of a convergence record or a rendered Scope Confirmation is provided.

4 / 5

Workflow Clarity

The Hearing Protocol is a clearly sequenced 4-step process with explicit completion-evidence checkpoints, a re-ask-once feedback loop in Step 3 for values failing pass conditions, and a closing Quality Checklist. This matches anchor 5 (explicit validation, feedback loops, checklist); checkpoints are explicit, not implicit, so 4 undersells it.

5 / 5

Progressive Disclosure

The body stays an overview and correctly splits judgment rules into references/criteria.md (a real file, one level deep), signaled both inline ('Judgment rules per field') and in a References section with a content description. Clear split and easy navigation match anchor 5.

5 / 5

Total

18

/

20

Passed

Description

67%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 well-constructed description with clear third-person actions, an explicit 'Use when' clause, and a mostly distinct niche. Its main weakness is trigger-term breadth: the activation phrasing is procedural and narrow rather than covering the natural phrases a user would say when bringing a rough request for convergence.

Suggestions

Broaden the 'Use when' clause with concrete trigger phrases users would naturally say, e.g. 'Use when a requirement or feature request enters a workflow, when the user asks to scope, gather, or refine requirements, or before design begins.'

Name the concrete artifact the skill produces (e.g. '...and produces a convergence record of outcome, requirements, nonGoals, and cost band') so the 'what' is anchored to a tangible output.

DimensionReasoningScore

Specificity

Names three concrete actions ('Separates the outcome a change must produce from the requirements proposed to reach it, records what the user excluded, and bands cost from decision-relevant repository evidence') covering the skill's full job. Not 5 because the actions stay at a domain-abstract level without naming the concrete artifacts produced.

4 / 5

Completeness

Both parts are explicit: a clear 'what' (the three actions) and an explicit 'Use when...' clause. Not 5 because the 'when' lacks concrete trigger phrases; not 3 because the trigger is stated, not merely implied.

4 / 5

Trigger Term Quality

'Use when a requirement enters a workflow, before design begins' supplies relevant keywords (requirement, workflow, design) but misses natural variations users would say, such as 'requirements gathering', 'scoping', or 'refine requirements'. Fits anchor 3 (some relevant keywords, missing common variations) better than 4, whose keyword coverage is broad.

3 / 5

Distinctiveness Conflict Risk

The outcome/requirements/nonGoals/cost convergence framing is a distinct niche with a clear pre-design trigger. Minor overlap risk remains with adjacent planning or scoping skills that also trigger on 'requirement' or 'design', keeping it below anchor 5.

4 / 5

Total

15

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

shinpr/claude-code-workflows

Path

dev-workflows-frontend/skills/requirement-convergence/SKILL.md

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.