feature-forge

Name: feature-forge
Availability: InStock
Author: enigmaicon-eng

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

1|Updated May 16, 2026

Search Tags:#implementation planning #requirements #acceptance criteria #feature specification #user stories #workshop facilitation #ears format

Ready to run

npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill feature-forge-enigmaicon-eng

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-forge
Source: https://github.com/enigmaicon-eng/AI-Enterprise-OS/tree/main/examples/claude-skills/skills/feature-forge
Command: npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill feature-forge-enigmaicon-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It removes the ambiguity and rework that happen when new features are scoped informally, so teams can align on clear requirements, acceptance criteria, and implementation tasks before building.

Core Features & Use Cases

Structured Requirements Workshops: Runs a PM (value) + Dev (feasibility/security/edge cases) discovery flow to clarify goals, users, scope, and constraints.
EARS-Format Functional Specs: Produces functional requirements in an unambiguous EARS pattern and ensures non-functional requirements are included.
Validation & Planning: Converts stakeholder feedback into testable Given/When/Then acceptance criteria and an implementation TODO checklist.

What problem does it solve?

Use this skill when you need to define a feature end-to-end—especially when requirements must be precise, testable, and ready for implementation.

Quick Start

Request a complete feature specification with EARS functional requirements, Given/When/Then acceptance criteria, error handling, and an implementation checklist for the feature you want to ship.

Frequently Asked Questions about feature-forge

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

FAQPage Schema

How do I turn feature ideas into testable user stories and acceptance criteria?▼

To turn feature ideas into testable user stories, you run a structured requirements workshop that produces user stories alongside Given/When/Then acceptance criteria. This aligns PM and engineering teams on clear scope before implementation begins.

What is the EARS format for writing functional requirements?▼

The EARS format is an unambiguous pattern for writing functional requirements to remove scope ambiguity. It structures conditions and system responses so that PM and dev teams share a single, precise interpretation of feature behavior.

How do I gather non-functional and security requirements during feature planning?▼

You gather non-functional and security requirements by running a PM plus Dev discovery flow that explicitly targets feasibility, edge cases, and constraints. This structured elicitation ensures non-functional considerations are documented alongside core feature specifications.

What is the best way to facilitate stakeholder requirements workshops for new product capabilities?▼

The best way to facilitate stakeholder requirements workshops is using a structured PM and Dev discovery flow to clarify goals, users, scope, and constraints. This process converts raw stakeholder feedback into validation-first outputs like implementation checklists.

Can I generate an implementation checklist directly from feature specifications?▼

Yes, you can generate an implementation checklist directly from feature specifications. By validating stakeholder feedback into EARS-format requirements and acceptance criteria first, the workflow outputs a concrete TODO checklist ready for development.

When do I need structured requirements elicitation before building a new feature?▼

You need structured requirements elicitation when a feature spans both PM and engineering concerns and requires precise, testable outputs. It removes the ambiguity and rework that happen when new capabilities are scoped informally without non-functional considerations.