CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

speckit-converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

Quality

71%

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 ./tools/factory/.claude/skills/speckit-converge/SKILL.md

The canonical home for this skill is speckit-converge in RihardsJ/software-factory

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 highly actionable, well-sequenced procedural skill with concrete commands, templates, and strong safety constraints (append-only, byte-for-byte unchanged when converged). Its main weaknesses are the near-verbatim duplication of the extension-hooks protocol and the absence of any progressive disclosure into reference files.

Suggestions

Extract the extension-hooks protocol (parsing rules, enabled/condition handling, optional vs. mandatory output blocks) into a single shared section or a references/hooks.md file and point both the pre-execution check and Step 9 at it, removing ~70 lines of duplication.

Move the hook output templates and the findings-table example into a reference file so SKILL.md stays a lean overview with one-level-deep references.

Add a post-append verification step (e.g. re-read tasks.md to confirm the new phase section and zero-padded IDs are correctly formatted) to close the workflow's only validation gap.

DimensionReasoningScore

Conciseness

Most of the body is necessary procedural detail rather than explanation of known concepts, but the extension-hooks protocol is repeated nearly verbatim in 'Pre-Execution Checks' and 'Step 9' (~70 of ~275 lines), plus duplicated boilerplate blocks for optional/mandatory hook output. Not a 2 because the verbosity is redundancy of needed instructions, not padding or basic-concept explanation, and it could be tightened rather than rewritten.

3 / 5

Actionability

The guidance is fully executable for an instruction-only skill: an exact script invocation ('.specify/scripts/bash/check-prerequisites.sh --json --require-spec --require-tasks --include-tasks'), a concrete ID scheme ('T{M+1:03d}'), a copy-paste checklist line format ('- [ ] T042 <imperative description> per <source-ref> (<gap-type>)'), exact findings-table schema, and exact output text for the converged branch. Specific examples cover the common cases.

5 / 5

Workflow Clarity

Nine numbered steps are clearly sequenced with explicit checkpoints: prerequisite script validation with JSON parsing, STOP-with-actionable-message on missing artifacts, an in-session findings summary required before any write, and a converged branch that guarantees tasks.md stays byte-for-byte unchanged. Not a 5 because there is no post-append verification step (e.g. re-reading tasks.md to confirm the appended section) and 'keyword search for the concepts' in Step 3 leaves the search method implicit.

4 / 5

Progressive Disclosure

Sections are well-organized with clear headers, but the skill is a ~275-line monolith with no bundle files or references at all; the duplicated extension-hooks protocol and detailed hook output templates clearly belong in a one-level-deep reference file. Not a 4 because content that should be separate is fully inlined and there are no signaled references to offset that.

3 / 5

Total

15

/

20

Passed

Description

58%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 specific, action-oriented description with a clear purpose and concrete file target, but it entirely lacks 'when to use' trigger guidance. Adding an explicit 'Use when...' clause with natural trigger terms would materially improve discoverability.

Suggestions

Add an explicit trigger clause, e.g. 'Use after /speckit-implement completes, when the implementation may not fully satisfy the spec, plan, or tasks.'

Include natural user phrasings/synonyms such as 'converge', 'implementation gaps', 'unfinished requirements', or 'verify spec coverage' so the skill triggers on how users actually ask for it.

Briefly name the assessment outputs (gap findings by severity, appended convergence tasks) to sharpen the 'what' beyond the two current verbs.

DimensionReasoningScore

Specificity

The description states two concrete actions with named artifacts — 'Assess the current codebase against the feature's spec, plan, and tasks' and 'append any remaining unbuilt work as new tasks to tasks.md' — which goes beyond the 1-2 generic actions of anchor 3. It is not a 5 because coverage stops at two verbs and does not enumerate what the assessment produces (findings, severity, task format).

4 / 5

Completeness

The 'what' is clear (assess codebase against artifacts, append remaining work to tasks.md), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 2 because the 'what' half is specific and unambiguous.

3 / 5

Trigger Term Quality

Terms like 'spec', 'plan', 'tasks', and 'tasks.md' are relevant keywords a spec-kit user might say, but the description omits natural variations and synonyms such as 'converge', 'implementation gaps', or 'unfinished requirements'. Not a 4 because common phrasings users would actually use to invoke this skill are missing.

3 / 5

Distinctiveness Conflict Risk

The spec/plan/tasks convergence niche with a concrete tasks.md append contract is mostly distinct, with only minor overlap risk against sibling spec-kit skills (e.g. speckit-implement, speckit-tasks) that also reference tasks.md. Not a 5 because those closely related siblings share the same triggering vocabulary.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

RihardsJ/software-factory

Path

tools/factory/.claude/skills/speckit-converge/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.