CtrlK
BlogDocsLog inGet started
Tessl Logo

feature-spec

Creates a complete product feature specification with acceptance criteria, scope, dependencies, and risks. Delegates to the Prometeo (PM) agent.

59

Quality

68%

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 ./plugins/agent-triforce/skills/feature-spec/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 content is a lean, well-structured instruction skill with concrete commands, a clear sequenced workflow, and named checkpoints. Its main weakness is the absence of an explicit error-recovery loop around its validation checklists.

DimensionReasoningScore

Conciseness

The body is efficiently organized into short, purposeful sections that assume Claude's competence (e.g. references 'SIGN IN checklist' without explaining it); the only minor over-explanation is the intro line repeating the frontmatter description.

4 / 5

Actionability

Provides concrete usage commands ('/feature-spec user authentication with JWT tokens'), an explicit output path ('docs/specs/{feature-name}.md'), and a worked example with the spec's structure, giving mostly executable guidance with only minor gaps.

4 / 5

Workflow Clarity

The six-step 'What This Skill Does' sequence is clearly ordered with named checkpoints (SIGN IN, Spec Completion/TIME OUT, SIGN OUT), but no explicit error-recovery or feedback loop is described when a checklist fails, leaving a minor validation gap.

4 / 5

Progressive Disclosure

The skill is self-contained (no references/, scripts/, or assets/ bundle files exist) and under 50 lines with well-organized section headers, satisfying the simple-skill exception for progressive disclosure.

5 / 5

Total

17

/

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.

The description clearly states what the skill produces and lists concrete spec components, but omits any 'Use when...' trigger guidance, leaving the 'when' question unanswered. It is specific and reasonably distinct but would benefit from explicit trigger phrases.

Suggestions

Add a 'Use when...' clause naming natural trigger phrases, e.g. 'Use when defining a new feature, writing user stories, or planning product work that needs a structured spec.'

Include common synonyms users would actually say, such as 'feature spec', 'user stories', 'product requirements', or 'PRD'.

Consider mentioning the output location (docs/specs/) in the description to further sharpen distinctiveness.

DimensionReasoningScore

Specificity

Names the domain and lists several concrete deliverable components ('acceptance criteria, scope, dependencies, and risks'), giving specific substance rather than vague language, though these are output components rather than multiple distinct actions.

4 / 5

Completeness

Has a clear 'what' (creates a complete product feature specification with named components) but no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Contains relevant keywords like 'feature specification', 'acceptance criteria', and 'risks', but misses common natural variations a user might say ('feature spec', 'user stories', 'product requirements') and has no trigger phrasing.

3 / 5

Distinctiveness Conflict Risk

The product-feature-specification niche and explicit delegation to the 'Prometeo (PM) agent' make it mostly distinct from other skills, with only minor overlap risk against general planning or documentation skills.

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.

Validation15 / 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
davepoon/buildwithclaude
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.