Convert feature descriptions into INVEST-compliant user stories with Gherkin specs and test matrices.
npx skills add https://github.com/benjaminfauchald/Tracklister --skill story
Please help me install this Agent Skill. Skill: story Source: https://github.com/benjaminfauchald/Tracklister/tree/main/.claude/skills/story Command: npx skills add https://github.com/benjaminfauchald/Tracklister --skill story
Writing comprehensive user stories and the associated artifacts from vague feature ideas is error-prone and time-consuming, leading to misaligned expectations and rework.
Provide a feature description; the tool will generate a complete user story package, including a GitHub issue.
High-intent search queries and answers about installing and using this skill.
Generate user stories and acceptance criteria by providing a feature description to automatically produce an end-to-end package. The output includes INVEST-compliant narratives, Gherkin specs, test matrices, and Definition of Done across product, engineering, and QA perspectives.
Write Gherkin specs and test matrices for GitHub issues by converting feature requirements into structured test artifacts. This process automatically generates docs-ready outputs suitable for issue tracking and CI integration, ensuring robust validation coverage.
The best way to create INVEST-compliant user stories is to process feature descriptions through an automated narrative generator. This ensures stories meet Independent, Negotiable, Valuable, Estimable, Small, and Testable criteria while aligning product, engineering, and QA perspectives.
Yes, Gherkin specs can be used for CI integration and docs generation. The feature conversion process produces files suitable for docs/stories directories and continuous integration pipelines, streamlining both automated testing and documentation workflows.
Generating user stories automatically includes a Definition of Done (DoD) within the output package. The conversion process produces DoD alongside Gherkin specs and test matrices to ensure complete acceptance criteria and validation standards.
Writing user stories from vague feature ideas leads to rework due to error-prone manual processes and misaligned expectations. Automating the generation of comprehensive story packages with acceptance criteria ensures alignment and reduces development iterations.
ReScienceLabCreate an isolated git worktree for a feature branch with automatic project setup.
kentojeGenerate OpenProse workflow code from plain English descriptions.
semicolon-devteamValidate test cases against issue acceptance criteria and generate verification reports.
MrAlexisCordGenerate user stories with INVEST criteria and BDD acceptance criteria.
