CtrlK
BlogDocsLog inGet started
Tessl Logo

feature-forge

Conducts structured requirements workshops to produce feature specifications, user stories, EARS-format functional requirements, acceptance criteria, and implementation checklists. Use when defining new features, gathering requirements, or writing specifications. Invoke for feature definition, requirements gathering, user stories, EARS format specs, PRDs, acceptance criteria, or requirement matrices.

71

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Failed to scan

The risk profile of this skill

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.

A well-structured, mostly lean skill body with excellent progressive disclosure via a verified reference table and concrete actionable templates. The main gaps are minor redundancy with the frontmatter and the absence of an explicit validation feedback loop in the workflow.

Suggestions

Remove or compress the 'When to Use This Skill' section since its triggers already appear verbatim in the frontmatter description, reclaiming tokens without losing information.

Add an explicit feedback loop to the Validate step (e.g., 'If the stakeholder rejects criteria, revise requirements and re-validate before proceeding to Plan') to strengthen workflow clarity.

Tighten the MUST DO / MUST NOT DO lists, which partially restate the Core Workflow steps, by focusing them only on constraints not already implied by the workflow.

DimensionReasoningScore

Conciseness

Lean and efficient with no over-explanation of known concepts and justified inline examples, but the 'When to Use This Skill' section largely duplicates the trigger phrases already in the frontmatter description and could be trimmed.

4 / 5

Actionability

Provides concrete, executable guidance—specific tool use (AskUserQuestions, Task subagents), a 6-part output structure, fill-in EARS and Given/When/Then templates, and a save path—with only minor high-level gaps in the workflow steps that references fill.

4 / 5

Workflow Clarity

The 5-step Core Workflow (Discover→Interview→Document→Validate→Plan) is clearly sequenced with a Validate checkpoint and clarification constraints, but it lacks an explicit validate→fix→retry feedback loop for error recovery.

4 / 5

Progressive Disclosure

Clear overview with a well-signaled, one-level-deep reference table; all 5 referenced files (ears-syntax, interview-questions, specification-template, acceptance-criteria, pre-discovery-subagents) exist, and inline content is kept minimal with a 'Load When' column easing navigation.

5 / 5

Total

17

/

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, third-person description that clearly states concrete deliverables and provides explicit, comprehensive trigger phrases covering both 'what' and 'when'. Its only weakness is minor overlap risk with the related spec-miner skill.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and outputs ('produce feature specifications, user stories, EARS-format functional requirements, acceptance criteria, and implementation checklists') with comprehensive coverage, matching the anchor for multiple specific concrete actions.

5 / 5

Completeness

Explicitly answers both what ('Conducts structured requirements workshops to produce...') and when ('Use when defining new features, gathering requirements, or writing specifications') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger terms with synonyms ('defining new features'/'feature definition', 'gathering requirements'/'requirements gathering', 'user stories', 'EARS format specs', 'PRDs', 'acceptance criteria', 'requirement matrices') that users would naturally say.

5 / 5

Distinctiveness Conflict Risk

Clear requirements/spec niche with distinct EARS/PRD triggers, but the noted related skill 'spec-miner' creates minor overlap risk with closely related spec skills, keeping it just below 5.

4 / 5

Total

19

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
jeffallan/claude-skills
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.