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.
99
100%
Does it follow best practices?
Impact
98%
1.84xAverage score across 6 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels across all dimensions. It uses third person voice correctly, provides specific concrete outputs, includes comprehensive trigger terms that users would naturally use, and clearly distinguishes itself from other skills through domain-specific terminology like EARS format and requirements matrices.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete outputs: 'feature specifications, user stories, EARS-format functional requirements, acceptance criteria, and implementation checklists' - these are all distinct, concrete deliverables. | 3 / 3 |
Completeness | Clearly answers both what ('Conducts structured requirements workshops to produce...') AND when ('Use when defining new features, gathering requirements, or writing specifications. Invoke for...') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'feature definition', 'requirements gathering', 'user stories', 'EARS format specs', 'PRDs', 'acceptance criteria', 'requirement matrices' - these match how users naturally describe requirements work. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on requirements engineering with distinct terminology like 'EARS-format', 'requirements workshops', 'PRDs', and 'requirement matrices' that wouldn't overlap with general documentation or coding skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that demonstrates excellent structure and actionability. It efficiently defines a requirements workshop process with clear workflows, appropriate tool usage, concrete examples, and well-organized progressive disclosure through reference files. The dual PM/Dev perspective framing and explicit constraints make the skill immediately usable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, avoiding explanations of concepts Claude already knows. Every section serves a purpose with no padding or unnecessary context about what requirements gathering is. | 3 / 3 |
Actionability | Provides concrete guidance with specific tool usage (AskUserQuestions), inline EARS format examples, acceptance criteria examples, and clear output file naming convention. The workflow steps are specific and executable. | 3 / 3 |
Workflow Clarity | Clear 5-step workflow (Discover → Interview → Document → Validate → Plan) with explicit tool usage at each step. The MUST DO/MUST NOT DO constraints provide validation checkpoints, and the reference table guides when to load additional context. | 3 / 3 |
Progressive Disclosure | Excellent structure with a clear reference table pointing to one-level-deep files for detailed guidance. Inline examples provide quick reference while full documentation is appropriately externalized to reference files. | 3 / 3 |
Total | 12 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jeffallan/claude-skills
- Commit
5b76101
- 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.