skills.rest
stephanj
stephanjCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

feature-forge

Define EARS-format feature specifications and testable acceptance criteria from stakeholder interviews.

9|2|Updated Jan 29, 2026
Search Tags:#planning#specification#requirements#ears#product-management#user-stories
One-click install
npx skills add https://github.com/stephanj/claude-code-collections --skill feature-forge-stephanj
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-forge
Source: https://github.com/stephanj/claude-code-collections/tree/main/skills/feature-forge
Command: npx skills add https://github.com/stephanj/claude-code-collections --skill feature-forge-stephanj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the ambiguity and lack of technical rigor often found in early-stage feature definitions, ensuring that requirements are testable, secure, and aligned with business goals.

Core Features & Use Cases

  • Structured Elicitation: Uses specialized questioning patterns to gather requirements from both PM and Dev perspectives.
  • Standardized Documentation: Automatically generates specifications using the EARS (Easy Approach to Requirements Syntax) format.
  • Use Case: When planning a new user authentication module, use this skill to conduct a discovery workshop, define acceptance criteria in Given-When-Then format, and generate a comprehensive implementation checklist.

Quick Start

Invoke the feature-forge skill to begin a requirements gathering session for the new user export feature.

Frequently Asked Questions about feature-forge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write structured feature specifications using the EARS format?▼

Structured feature specifications using the EARS format are defined by conducting stakeholder interviews and technical analysis to generate testable functional requirements, non-functional constraints, and acceptance criteria.

What is the best way to gather product requirements for a new software feature?▼

The best way to gather product requirements is through structured elicitation that uses specialized questioning patterns to capture both product management and development perspectives, ensuring technical rigor and business alignment.

How do I define testable acceptance criteria for user stories?▼

Testable acceptance criteria for user stories are defined using the Given-When-Then format, derived directly from comprehensive feature specifications and EARS-format functional requirements.

Can I use structured requirements gathering for early-stage technical planning?▼

Yes, structured requirements gathering applies directly to the technical planning phase of software development, resolving early-stage feature ambiguity by producing comprehensive implementation checklists.

Why does my feature definition lack technical rigor and testable constraints?▼

Feature definitions lack technical rigor when they miss standardized documentation, which is solved by applying structured analysis to generate EARS-format functional requirements and non-functional constraints.

Related Skills

Explore More Product & Management Skills→
unclecatvnunclecatvn
120

brainstorming

Clarifies user goals and constraints to transform ideas into concrete design concepts.

Community
Advanced
enigmaicon-engenigmaicon-eng
1

feature-forge

Conduct structured requirements workshops to produce EARS specifications and Given/When/Then criteria.

Community
Intermediate
taewook486taewook486

moai-workflow-spec

Orchestrate SPEC workflow management with EARS requirements and Plan-Run-Sync integration.

Community
Advanced
shalevaminshalevamin

feature-forge

Conduct structured requirements workshops to produce feature specifications with user stories and EARS-format requirements.

Community
Advanced