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.

1.84x

Quality

100%

Does it follow best practices?

Impact

98%

1.84x

Average score across 6 eval scenarios

Securityby

Passed

No known issues

Evaluation results

100%

66%

Subscription Plan Management Feature

Feature spec document completeness

Criteria

Without context

With context

Correct save path

100%

Overview section present

100%

EARS functional requirements

100%

Multiple EARS pattern types

100%

Non-functional requirements

100%

Given/When/Then acceptance criteria

100%

Error handling table

66%

100%

Implementation TODO checklist

100%

Out of scope section

100%

Requirement IDs present

37%

100%

Security considerations

100%

92%

Feature Discovery Planning: Real-Time Collaboration Annotations

Requirements interview question design

Criteria

Without context

With context

PM Hat questions present

100%

Dev Hat questions present

100%

Perspectives clearly separated

50%

Structured choices identified

100%

Open-ended questions identified

100%

Structured vs open-ended rationale

100%

Interview phases present

100%

70%

Priority question included

100%

45%

Enterprise SSO Integration Feature

Multi-domain pre-discovery and EARS format

Criteria

Without context

With context

Readiness notes present

100%

Multi-domain tracks identified

100%

Track purpose documented

100%

Spec saved at correct path

100%

EARS functional requirements

16%

100%

EARS conditional pattern used

100%

Non-functional requirements section

37%

100%

Given/When/Then acceptance criteria

100%

Error handling table

100%

Implementation TODO checklist

12%

100%

Security requirements explicit

100%

Requirement IDs present

100%

82%

Audit Logging Feature Specification

EARS full pattern variety

Criteria

Without context

With context

Ubiquitous EARS pattern

100%

State-Driven EARS pattern

100%

Optional EARS pattern

100%

Event-Driven EARS pattern

100%

Requirement identifiers

100%

Non-functional requirements

100%

Given/When/Then acceptance criteria

100%

Error handling table

37%

100%

Implementation TODO checklist

50%

100%

Correct save path

100%

Overview section

57%

100%

54%

Document Upload Feature Specification

Acceptance criteria scenario coverage

Criteria

Without context

With context

Happy path AC present

50%

100%

Error case AC present

58%

100%

Edge case AC present

50%

100%

Authorization AC present

50%

100%

AC count

100%

AC testability

80%

100%

EARS functional requirements

100%

Non-functional requirements

100%

Error handling table

37%

100%

Implementation TODO checklist

100%

Security requirements addressed

100%

Correct save path

100%

17%

Real-Time Analytics Dashboard Feature Specification

NFR quantification and ambiguity documentation

Criteria

Without context

With context

Response time quantified

100%

Concurrent user count specified

100%

Throughput or availability quantified

100%

Data retention period specified

100%

Open questions section present

100%

Assumptions documented

100%

EARS functional requirements

25%

100%

Security requirements explicit

100%

Given/When/Then acceptance criteria

100%

Error handling table

28%

100%

Correct save path

100%

Repository: jeffallan/claude-skills
Commit: 5b76101

Evaluated: 27 days ago
Agent: Claude Code
Model: Claude Sonnet 4.6

Table of Contents

Subscription Plan Management Feature Feature Discovery Planning: Real-Time Collaboration Annotations Enterprise SSO Integration Feature Audit Logging Feature Specification Document Upload Feature Specification Real-Time Analytics Dashboard Feature Specification

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.