ba-user-story-light

Generate concise User Stories with Given-When-Then acceptance criteria from UI screenshots or FE code.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/clovernguyen1010-ship-it/Clover_Nguyen --skill ba-user-story-light-clovernguyen1010-ship-it
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ba-user-story-light
Source: https://github.com/clovernguyen1010-ship-it/Clover_Nguyen/tree/main/.agent/skills/ba-user-story-light
Command: npx skills add https://github.com/clovernguyen1010-ship-it/Clover_Nguyen --skill ba-user-story-light-clovernguyen1010-ship-it

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables rapid creation of concise User Stories for simple features by extracting requirements from screenshots or FE code and by analyzing associated API endpoints to derive acceptance criteria.

Core Features & Use Cases

  • Automated generation of lightweight User Stories from UI/design inputs or frontend code references.
  • API analysis to outline necessary commands/queries and to shape acceptance criteria.
  • Scenario-based outputs (Given-When-Then) ready for dev/QA validation.

Quick Start

Provide a UI screenshot or FE code snippet and the system will generate a lean User Story with acceptance criteria.

Frequently Asked Questions about ba-user-story-light

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate user stories from UI screenshots or frontend code?

To generate user stories from UI screenshots or frontend code, provide the visual input or code snippet to the system. It automatically analyzes frontend routes and API interactions to output lean user stories with ready-to-use acceptance criteria.

Can I create Given-When-Then acceptance scenarios from frontend API analysis?

Yes, you can create Given-When-Then acceptance scenarios from frontend API analysis. The system evaluates API endpoints to outline necessary commands and queries, mapping them directly into scenario-based outputs for dev and QA validation.

What is the best way to write acceptance criteria for simple features with few screens?

The best way to write acceptance criteria for simple features with few screens is to automate extraction from design inputs. This tool targets lightweight features, analyzing UI and API endpoints to produce ready-to-use Given-When-Then validation scenarios.

Does automated user story generation work for complex frontend routes and API interactions?

Automated user story generation works best for simple features with few screens rather than complex frontend routes. It satisfies end-to-end workflow requirements by capturing inputs and mapping API interactions into concise acceptance criteria for development.

How do I extract business analysis requirements from a UI screenshot for QA testing?

To extract business analysis requirements from a UI screenshot for QA testing, input the design file into the system. It analyzes the frontend interface and associated APIs to derive scenario-based acceptance criteria ready for validation.