skills.rest
thesaifalitai
thesaifalitaiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

feature-forge

Define feature specifications with EARS-format requirements and Given/When/Then acceptance criteria.

8|1|Updated Feb 27, 2026
Search Tags:#requirements#acceptance criteria#user stories#feature definition#ears#implementation checklist
One-click install
npx skills add https://github.com/thesaifalitai/claude-setup --skill feature-forge-thesaifalitai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-forge
Source: https://github.com/thesaifalitai/claude-setup/tree/main/skills/feature-forge
Command: npx skills add https://github.com/thesaifalitai/claude-setup --skill feature-forge-thesaifalitai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Feature Forge removes ambiguity in product feature definition by guiding structured discovery, producing formal EARS-format requirements, and generating testable acceptance criteria and implementation checklists to prevent rework and misaligned expectations.

Core Features & Use Cases

  • Structured Discovery: Runs a guided PM and developer interview sequence using the AskUserQuestions tool to elicit goals, users, priorities, and edge cases.
  • Formal Specification: Produces functional requirements in EARS format, non-functional requirements, and an error-handling table.
  • Validation & Planning: Creates Given/When/Then acceptance criteria and an implementation TODO checklist to drive development and QA.
  • Use Case: Run during a feature planning workshop to convert stakeholder goals into a prioritized, developer-ready spec and test plan.

Quick Start

Run the feature-forge skill and answer the guided PM and developer interview questions to generate an EARS-format specification, acceptance criteria, and an implementation TODO checklist.

Frequently Asked Questions about feature-forge

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

FAQPage Schema
How do I write EARS-format requirements from user stories?▼

To write EARS-format requirements, guide a structured PM and developer interview to elicit goals, users, and edge cases, then convert stakeholder ideas into formal functional specifications with non-functional constraints and an error-handling table.

What is the best way to create testable acceptance criteria for feature definition?▼

The best way to create testable acceptance criteria is to process feature definitions through a structured discovery phase, generating Given/When/Then statements alongside an implementation TODO checklist to drive development and QA while preventing rework.

Can I use structured discovery to generate an implementation checklist for full-stack projects?▼

Yes, structured discovery supports web and mobile full-stack projects by running an interactive requirements interview that produces a prioritized, developer-ready spec and a direct implementation TODO checklist for the development team.

How does structured discovery prevent ambiguity in product planning workshops?▼

Structured discovery prevents ambiguity in product planning workshops by prompting for specific PM and developer inputs, mapping stakeholder goals to formal EARS specifications, and validating expected behavior with Given/When/Then acceptance criteria.

Do I need developer inputs to define non-functional requirements and error-handling tables?▼

Yes, developer inputs are explicitly prompted during the requirements interview to accurately define non-functional constraints and populate an error-handling table, ensuring the feature specification is technically feasible and testable.

Related Skills

Explore More Product & Management Skills→
beel-collabbeel-collab
1

prd

Generate structured PRDs with executive summaries, user stories, and technical specifications.

Community
Basic
Pact-Community-OrganizationPact-Community-Organization
1

acceptance-criteria

Generate and validate Given/When/Then acceptance criteria for Pact 5 features.

Official
Intermediate
windyskywindysky

moai-workflow-spec

Orchestrate SPEC workflows with EARS format and Plan-Run-Sync lifecycle.

Community
Basic
mtsatryanmtsatryan
1

requirements-analyst

Document stakeholder requirements into structured user stories and acceptance criteria.

Community
Advanced