feature-forge

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

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/shalevamin/The-_Ultimate_agents --skill feature-forge-shalevamin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-forge
Source: https://github.com/shalevamin/The-_Ultimate_agents/tree/main/.claude/skills/feature-forge
Command: npx skills add https://github.com/shalevamin/The-_Ultimate_agents --skill feature-forge-shalevamin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of defining new features by systematically gathering requirements, producing detailed specifications, and ensuring all aspects from user value to technical implementation are considered.

Core Features & Use Cases

  • Structured Requirements Gathering: Conducts workshops using PM and Dev perspectives.
  • Specification Generation: Produces EARS-format functional requirements, user stories, acceptance criteria, and implementation checklists.
  • Use Case: When starting a new software project or adding a significant feature, use this Skill to ensure a clear, comprehensive, and actionable specification document is created before development begins.

Quick Start

Use the feature-forge skill to define a new user authentication 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 functional requirements using the EARS syntax for a new feature?

Functional requirements using EARS syntax are generated by running structured requirements workshops. These workshops elicit system behaviors through dual PM and Dev perspectives, translating them into precise EARS-format statements for your feature specification.

What is the best way to gather user stories and acceptance criteria before development begins?

Gathering user stories and acceptance criteria is best achieved through structured requirements elicitation. This process uses targeted interview strategies to capture both user value and technical constraints, ensuring a comprehensive and actionable specification document.

How do I create a comprehensive feature specification that includes implementation checklists?

Creating a comprehensive feature specification with implementation checklists requires systematically gathering requirements from dual PM and Dev perspectives. This approach ensures all technical implementation aspects and user stories are thoroughly documented before development starts.

Can I use a structured requirements workshop to define feature definitions for large software projects?

Structured requirements workshops are designed for defining feature definitions in large software projects. By employing targeted elicitation tools, they systematically produce detailed specifications including user stories, functional requirements, and acceptance criteria.

When do I need to use EARS format for requirements specification?

EARS format for requirements specification is needed when defining new features that require precise, unambiguous behavioral descriptions. It ensures functional requirements are clearly structured, reducing implementation ambiguity for development teams.