CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

spec-workflow

Use when medium-to-large changes need explicit requirements, technical design, and task planning before implementation, especially for multi-module work, unclear acceptance criteria, or architecture-heavy requests.

Quality

72%

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 ./config/source/skills/spec-workflow/SKILL.md
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.

The body is a well-structured, actionable instruction skill: concrete artifact paths, a complete EARS pattern with example, a task template, and explicit phase-gate confirmations. Its main weaknesses are redundant trigger sections that repeat the use/skip decision four times and the absence of validation or example structure for the design phase.

Suggestions

Merge "Use this first when", "When to use this skill", and "Decision rule" into a single activation section to remove the repeated use/skip criteria and cut tokens.

Add a brief example structure or content checklist for design.md so Phase 2 guidance is as concrete as the EARS requirements example.

Include a validation checkpoint for each phase (e.g., verify every task links back to a requirement before asking for confirmation) to add a feedback loop to the phase gates.

DimensionReasoningScore

Conciseness

The body uses tight bullet lists and explains nothing Claude already knows, but the use/skip criteria are restated across four overlapping sections ("Use this first when", "When to use this skill", "Decision rule", plus "Common mistakes" and "Minimal checklist"). This repetition goes beyond the minor-trimming level of the efficient anchor.

3 / 5

Actionability

Gives concrete executable guidance: exact artifact paths ("specs/<spec_name>/requirements.md"), a complete EARS pattern with a filled-in example, and a copy-ready task template. It falls short of fully-executable because Phase 2 and Phase 4 guidance stays high-level with no example structure for design.md content.

4 / 5

Workflow Clarity

Four phases are clearly sequenced with explicit confirmation checkpoints ("Only start implementation after the user confirms the task plan", "Require confirmation between requirements, design, and task breakdown"). It misses the top anchor because there is no quality-gate validation of the artifacts themselves or feedback loop for revising a rejected spec.

4 / 5

Progressive Disclosure

A single self-contained file with well-organized sections and no bundle files to split out; all content appropriately lives at this level. The sibling-skill references ("../ui-design/SKILL.md", "../postgresql-development-cloudbase/SKILL.md") are clearly signaled one level deep under "Then also read".

5 / 5

Total

16

/

20

Passed

Description

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

The description has a strong, explicit trigger clause covering when to use the skill and a reasonably distinct niche, but it never states what the skill actually does or produces. Framing the outputs as actions (e.g., creating requirements/design/tasks spec documents) would close the completeness and specificity gaps.

Suggestions

State the skill's concrete outputs as actions, e.g., "Creates requirements.md, design.md, and tasks.md spec documents with EARS-style acceptance criteria..." before the Use-when clause.

Add natural trigger synonyms users would say, such as "spec", "specification", "new feature", or "planning a feature", to broaden keyword coverage.

Narrow the architecture trigger (e.g., "architecture-heavy changes needing a written design") to reduce overlap risk with dedicated design/architecture skills.

DimensionReasoningScore

Specificity

Names the domain and its artifacts ("explicit requirements, technical design, and task planning") but frames them as things changes "need" rather than concrete actions the skill performs. It sits between the domain-plus-1-2-actions anchor and the several-specific-actions anchor, lacking action verbs like "Create requirements documents".

3 / 5

Completeness

The "when" is explicit and specific ("Use when medium-to-large changes need... especially for multi-module work, unclear acceptance criteria, or architecture-heavy requests"), but the "what" is only implied — the skill's outputs are named as needs, not as actions it takes. This matches the both-present-but-what-could-be-more-explicit anchor rather than the clearly-explicit-both anchor.

4 / 5

Trigger Term Quality

Includes relevant terms ("requirements", "technical design", "task planning", "multi-module", "acceptance criteria", "architecture") but misses natural synonyms users would actually say such as "spec", "specification", "new feature", or "design doc". Coverage is meaningful yet incomplete against the comprehensive-synonyms anchor.

3 / 5

Distinctiveness Conflict Risk

Spec-driven requirements/design/task planning carves a mostly distinct niche with concrete triggers, though "architecture-heavy requests" could overlap with a dedicated architecture or design skill. It fits the mostly-distinct-with-minor-overlap anchor rather than the minimal-conflict anchor.

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

TencentCloudBase/CloudBase-AI-Toolkit

Path

config/source/skills/spec-workflow/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.