skills.rest
aws-samples
aws-samplesOFFICIAL
Explore all skills by this author →
WebsiteGitHub

user-stories

Generate user stories in As-a/I-want/So-that format with acceptance criteria linked to REQ-IDs.

18|4|Updated Apr 29, 2026
Search Tags:#acceptance criteria#user story#change impact analysis#software development process#As-a/I-want/So-that
One-click install
npx skills add https://github.com/aws-samples/sample-oh-my-aidlcops --skill user-stories-aws-samples
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: user-stories
Source: https://github.com/aws-samples/sample-oh-my-aidlcops/tree/main/plugins/aidlc/skills/inception/user-stories
Command: npx skills add https://github.com/aws-samples/sample-oh-my-aidlcops --skill user-stories-aws-samples

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of user stories for changes that affect the user interface, significantly reducing the time spent on manual story writing and ensuring consistency across the team.

Core Features & Use Cases

  • Conditional Story Generation: Generates user stories in As-a/I-want/So-that format only when changes are user-facing.
  • Skipping Non-User-Facing Changes: Skips story generation for internal refactor work or pure infrastructure changes.
  • Acceptance Criteria Linking: Provides acceptance criteria linked back to REQ-IDs for traceability.

Quick Start

Generate a user story for the feature with the slug 'feature-slug'.

Frequently Asked Questions about user-stories

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

FAQPage Schema
How do I generate user stories in As-a/I-want/So-that format for user-facing changes?▼

To generate user stories in As-a/I-want/So-that format, you need a requirements file and persona definitions. The Skill then automatically creates stories for changes that affect user-facing features based on those inputs.

Do I need to manually write acceptance criteria for each user story?▼

No, you do not need to manually write acceptance criteria. The Skill automates this process and links the generated acceptance criteria directly back to your original REQ-IDs for full traceability.

Will user story generation trigger for internal refactoring or infrastructure changes?▼

No, user story generation will not trigger for internal refactoring or infrastructure changes. The Skill is designed to skip non-user-facing changes and only processes updates that affect the user interface.

What inputs are required to automate user story creation for the software development process?▼

Automating user story creation requires the presence of a requirements file and persona definitions. These inputs allow the system to conditionally generate stories for user-facing changes.

How does change impact analysis relate to generating user stories?▼

Change impact analysis determines whether a code change affects user-facing features. If the change is user-facing, the Skill generates a user story; otherwise, it skips generation to save time.

Related Skills

Explore More Product & Management Skills→
wfukatsuwfukatsu
12

generate-persona

Generate job-to-be-done personas with job stories and persona cards.

Community
Intermediate
product-on-purposeproduct-on-purpose
527

deliver-user-stories

Generate user stories and Given/When/Then acceptance criteria from product requirements.

Official
Basic
RailsEventStoreRailsEventStore
504

new-feature

Plan new user-facing features via impact analysis and test planning in Rails event-sourced applications.

Official
Advanced
abhilash-nandkumarabhilash-nandkumar

user-story-fundamentals

Capture user requirements into structured user stories with acceptance criteria.

Community
Intermediate