feature-forge

To write testable acceptance criteria from a vague feature idea, run structured PM and Dev elicitation to define users, goals, and scope, then generate Given/When/Then validation rules. The output is a comprehensive specification saved as a markdown file.

EARS format is a structured syntax for writing unambiguous functional requirements. It helps transform feature concepts into clear specifications by systematically defining conditions and system responses, ensuring stakeholder-validated and testable outcomes.

Create a feature specification with non-functional requirements by guiding PM and Dev perspectives through systematic questioning to clarify scope, then documenting EARS functional specs alongside supporting constraints like performance and security.

The best way to document user stories and an implementation checklist is to apply structured requirements gathering to define the feature, producing stakeholder-ready acceptance criteria and a concrete TODO checklist saved directly to your specs directory.

Yes, you can use structured elicitation for cross-domain planning and specification. It applies systematic questioning across PM and Dev perspectives to clarify scope and success metrics, producing comprehensive requirements for cross-domain work.

No external dependencies are required to generate EARS-format specifications. You simply provide a feature concept with desired user outcomes and target platform constraints, and the elicitation process outputs a complete requirements document.