Verified:GitHub

feature-forge

Creates feature specifications, user stories, and EARS-format functional requirements via guided workshops.

2|Updated Jun 29, 2026

Search Tags:#project management #acceptance criteria #feature management #specification generation #requirements workshops

Ready to run

npx skills add https://github.com/Axel-DaMage/opencode-config --skill feature-forge-axel-damage

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-forge
Source: https://github.com/Axel-DaMage/opencode-config/tree/main/skills/feature-forge
Command: npx skills add https://github.com/Axel-DaMage/opencode-config --skill feature-forge-axel-damage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires AskUserQuestions, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

The feature-forge Skill unit helps in managing feature development by providing structured requirements workshops, generating specifications, and planning implementations, thereby enhancing the clarity and effectiveness of feature development processes.

Core Features & Use Cases

Structured Requirements Workshops: Guides through structured workshops for producing comprehensive feature specifications.
Feature Definition: Aids in defining new features and gathering detailed requirements.
User Story and Specification Generation: Automatically generates user stories, EARS-format functional requirements, and implementation checklists.
Acceptance Criteria: Ensures all acceptance criteria are considered and actionable.
Use Case: Perfect for project managers or product owners who need to outline and communicate feature specifications to teams.

Quick Start

Initiate a feature-definition workshop by invoking 'feature-forge run workshop'.

Frequently Asked Questions about feature-forge

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

FAQPage Schema

How do I generate user stories and functional requirements for feature specifications?▼

Feature specifications are generated by running a structured requirements workshop that captures stakeholder input and outputs user stories alongside EARS-format functional requirements. This approach ensures all acceptance criteria are actionable and thoroughly documented.

What is the EARS format and when is it needed for feature management?▼

The EARS format is a structured syntax for writing unambiguous functional requirements, essential when defining feature specifications and acceptance criteria. It ensures requirements are actionable and clearly communicated to development teams during feature management.

How do I run a requirements workshop to define new product features?▼

Run a requirements workshop by invoking the feature-forge Skill to guide stakeholders through structured feature definition. The workshop process captures detailed requirements and automatically generates implementation checklists and related feature documentation.

Can I use this structured approach for feature definition if I only have high-level ideas?▼

Yes, structured feature definition workshops are designed to transform high-level ideas into detailed specifications. The process uses interactive questioning to gather context and produces comprehensive user stories and actionable acceptance criteria from initial concepts.

What is the best way to ensure acceptance criteria are actionable for development teams?▼

The best way to ensure actionable acceptance criteria is to use structured specification generation applying the EARS format. This standardizes functional requirement syntax, making feature specifications clear, verifiable, and directly implementable by development teams.

Do I need specific tools or prerequisites to facilitate feature specification generation?▼

Facilitating feature specification generation requires an environment supporting the AskUserQuestions tool for interactive workshops. Knowledge of EARS format syntax is also necessary to properly structure and validate the generated functional requirements.