feature-forge

Facilitate requirements workshops and generate EARS-format specification documents.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/Serg28/demosite --skill feature-forge-serg28
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-forge
Source: https://github.com/Serg28/demosite/tree/main/.agents/skills/feature-forge
Command: npx skills add https://github.com/Serg28/demosite --skill feature-forge-serg28

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies the process of defining, documenting, and validating complex feature requirements and specifications, reducing miscommunication and ensuring comprehensive coverage.

Core Features & Use Cases

  • Structured Requirement Collection: Guides requirements specialists through systematic workshops to gather detailed user stories, functional and non-functional specs.
  • Requirement Documentation: Generates clear, unambiguous requirement documents using EARS format, including acceptance criteria, error handling, and implementation tasks.
  • Use Case: When launching a new product feature, use this Skill to facilitate requirements workshops, produce detailed specifications, and align stakeholder understanding effectively.

Quick Start

Use the feature-forge skill to create a complete requirements document for your new login system.

Frequently Asked Questions about feature-forge

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

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

Feature specifications use the EARS format to generate unambiguous requirement documents with acceptance criteria, error handling, and implementation tasks. This ensures requirements are complete, testable, and aligned with business goals.

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

The best way to gather requirements for a new product feature is through structured workshops that elicit detailed user stories, functional specs, and non-functional specs from stakeholders. This guided elicitation reduces miscommunication and ensures comprehensive coverage.

How do I structure a requirements document for a login system?

To structure a requirements document for a login system, use guided templates to define functional and non-functional specifications, acceptance criteria, and implementation tasks. This ensures the feature definition is complete and testable.

Do I need prior documentation experience to define feature requirements?

No prior documentation experience is required to define feature requirements. The system provides structured templates and guided elicitation to help product managers, developers, and stakeholders produce clear specifications.

How does guided elicitation improve requirement documentation?

Guided elicitation improves requirement documentation by systematically leading specialists through workshops to collect detailed user stories and functional specs, ensuring that all generated requirements are complete, testable, and aligned with business goals.

Can I use this approach for non-functional specifications as well as functional specs?

Yes, this approach supports both non-functional specifications and functional specs. The structured requirement collection process explicitly gathers both types during workshops to ensure comprehensive feature definition.