harness-product-spec

To generate user stories with acceptance criteria from GitHub issues, provide the issue text to the Skill. It analyzes feature descriptions to produce structured PRDs with traceable requirements, EARS-style acceptance criteria, and Given-When-Then scenarios.

The best way to turn feature requests into traceable product specifications is automating conversion using structured PRD generation. It maps requirements directly to user stories and ensures testable EARS acceptance criteria, aligning issues with implementation.

EARS syntax for acceptance criteria in a PRD works by structuring conditions using predefined patterns to make requirements unambiguous and testable. The Skill applies this syntax to produce Given-When-Then scenarios that ensure alignment between issues and implementation.

Yes, you can use inline text to generate a product spec. The Skill accepts inline feature descriptions as input, analyzing the provided text to output a complete PRD, user stories, and traceable acceptance criteria without requiring a GitHub issue.

To map requirements to user stories and Given-When-Then scenarios, the Skill processes feature requests and outputs a structured PRD. It ensures traceability by linking each requirement directly to its corresponding user story and testable scenarios.