What is the primary purpose of the accepting-stories skill?

It provides a structured framework for Product Owners to verify that specific user stories meet all defined acceptance criteria before they are marked as complete.

What happens if a story fails the acceptance check?

The skill guides the user to document the specific failure, identify required fixes, and update the story status to 'Needs Revision' to alert the development team.

Does this skill perform automated unit testing?

No, it is designed for manual or guided acceptance testing where a reviewer verifies functionality against 'Given/When/Then' scenarios within the implementation.

Where does the skill store the testing results?

Results are recorded directly in the project's story documentation files (typically .story.md files), maintaining a permanent log of the review process.

Story-Driven Acceptance Testing

Name: Story-Driven Acceptance Testing
Author: kecbigmt

bykecbigmt

Seguridad y Pruebas

Guides Product Owners through systematic acceptance testing to verify user stories against defined criteria before final approval.

Acerca de

The Story-Driven Acceptance Testing skill automates the rigorous process of User Acceptance Testing (UAT) within the Claude Code environment. By guiding Product Owners through a structured review of acceptance criteria, it ensures that every feature implementation aligns perfectly with project requirements. The skill facilitates locating story documentation, executing Given/When/Then test scenarios, and formally documenting pass/fail results directly in the project logs, bridging the gap between development completion and product sign-off.

Características Principales

Systematic logging of Pass, Fail, and Blocked statuses
Automated discovery of pending story documentation via CLI
0 GitHub stars
Structured Given/When/Then verification framework
Standardized status reporting for 'Accepted' or 'Needs Revision' states
Detailed revision requirement tracking for failed criteria

Casos de Uso

Verifying complex feature requirements using structured preconditions and actions
Standardizing the UAT process across a distributed development team
Conducting formal Product Owner reviews before marking stories as Done

Acerca de

Características Principales

Systematic logging of Pass, Fail, and Blocked statuses
Automated discovery of pending story documentation via CLI
0 GitHub stars
Structured Given/When/Then verification framework
Standardized status reporting for 'Accepted' or 'Needs Revision' states
Detailed revision requirement tracking for failed criteria

Casos de Uso

Verifying complex feature requirements using structured preconditions and actions
Standardizing the UAT process across a distributed development team
Conducting formal Product Owner reviews before marking stories as Done