Where are the testing logs stored?

The logs are appended directly to the relevant story files located in your project's 'docs/stories' directory, ensuring that documentation stays in sync with the code state.

Is manual testing required for every story in this workflow?

No, manual testing is an optional step. It is recommended for high-risk features or UI/UX validation where a Product Owner wants human verification beyond the standard AI-automated checks.

Does this skill replace automated unit or integration testing?

No, it complements them. The AI verification phase provides technical rigor, while this skill focuses on stakeholder confidence and subjective validation that automation might miss.

How does the skill handle failed tests?

If a criterion fails, the skill prompts for details on the expected vs. observed behavior and automatically updates the story log to 'Needs Revision' status, moving the task back to the implementation phase.

Story-Driven Acceptance Testing

Name: Story-Driven Acceptance Testing
Author: kecbigmt

bykecbigmt

0•

Security & Testing

Guides Product Owners through manual verification steps to validate features before they are merged into production.

The Story-Driven Acceptance Testing skill facilitates a structured hand-off between AI-driven development and human stakeholder verification. By automating the retrieval of story requirements and providing step-by-step instructions for manual testing, it ensures that Product Owners can validate UI/UX and high-risk features with confidence. This skill bridges the gap between objective AI verification and subjective human approval, maintaining a rigorous and standardized record of the acceptance status directly within the project's markdown documentation.

Key Features

01Standardized Acceptance Checks log formatting for audit trails

02Clear differentiation between AI-verified rigor and human-accepted validation

03Automated retrieval of specific story criteria from project documentation

040 GitHub stars

05Interactive Pass/Fail/Blocked feedback loops using AskUserQuestion

06Guided step-by-step manual testing instructions for stakeholders

Use Cases

01Validating UI/UX changes that require human visual confirmation before deployment

02Facilitating formal sign-off from Product Owners for high-risk business logic

03Maintaining a persistent history of manual testing results in story-driven workflows

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add kecbigmt/cc-plugins acceptance-testing

For use in Claude.ai and ChatGPT

Download Skill