Verified:GitHub

feature-forge

Convert feature concepts into EARS requirements specifications with acceptance criteria.

Updated Aug 23, 2026

Search Tags:#requirements #acceptance criteria #feature specification #user stories #product planning #non-functional requirements #ears format

Ready to run

npx skills add https://github.com/jsdfhasuh/emosonic --skill feature-forge-jsdfhasuh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-forge
Source: https://github.com/jsdfhasuh/emosonic/tree/main/.agents/skills/feature-forge
Command: npx skills add https://github.com/jsdfhasuh/emosonic --skill feature-forge-jsdfhasuh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you transform a vague feature idea into a complete, unambiguous specification with clear user value, functional and non-functional requirements, and verifiable acceptance criteria.

Core Features & Use Cases

Structured requirements discovery: Guides PM and Dev perspectives through systematic questioning to clarify users, goals, scope, and success metrics.
EARS-based functional specs: Produces functional requirements using EARS syntax plus supporting non-functional requirements like performance and security.
Stakeholder-ready validation and planning: Generates acceptance criteria in Given/When/Then form and an implementation TODO checklist to support delivery planning.

Quick Start

Use the feature-forge skill to write an EARS-format specification for your new music-player feature by describing the desired user outcome and target platform constraints in a single prompt.

Frequently Asked Questions about feature-forge

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

FAQPage Schema

How do I write testable acceptance criteria from a vague feature idea?▼

To write testable acceptance criteria from a vague feature idea, run structured PM and Dev elicitation to define users, goals, and scope, then generate Given/When/Then validation rules. The output is a comprehensive specification saved as a markdown file.

What is EARS format for functional requirements?▼

EARS format is a structured syntax for writing unambiguous functional requirements. It helps transform feature concepts into clear specifications by systematically defining conditions and system responses, ensuring stakeholder-validated and testable outcomes.

How to create a feature specification with non-functional requirements?▼

Create a feature specification with non-functional requirements by guiding PM and Dev perspectives through systematic questioning to clarify scope, then documenting EARS functional specs alongside supporting constraints like performance and security.

What's the best way to document user stories and an implementation checklist?▼

The best way to document user stories and an implementation checklist is to apply structured requirements gathering to define the feature, producing stakeholder-ready acceptance criteria and a concrete TODO checklist saved directly to your specs directory.

Can I use structured elicitation for cross-domain planning and specification?▼

Yes, you can use structured elicitation for cross-domain planning and specification. It applies systematic questioning across PM and Dev perspectives to clarify scope and success metrics, producing comprehensive requirements for cross-domain work.

Do I need external dependencies to generate EARS-format specifications?▼

No external dependencies are required to generate EARS-format specifications. You simply provide a feature concept with desired user outcomes and target platform constraints, and the elicitation process outputs a complete requirements document.