domains / families / software-engineering / feature-forge

feature-forge

separate

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.

When to use

• Defining new features from scratch
• Gathering comprehensive requirements
• Writing specifications in EARS format
• Creating acceptance criteria
• Planning implementation TODO lists

When not to use

• generating spec without conducting interview
• accepting vague requirements
• skipping security considerations
• forgetting error handling requirements
• writing untestable acceptance criteria
• outputting interview questions as plain text when structured options are available

Skill page

Source