aidlc-user-stories

Converts requirements from MD files into INVEST-compliant user stories with acceptance criteria.

2|Updated Mar 10, 2026

Search Tags:#product management #agile #requirements analysis #user stories #pre-planning #invest criteria

Ready to run

npx skills add https://github.com/bluejayA/devflow-aidlc-like --skill aidlc-user-stories

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aidlc-user-stories
Source: https://github.com/bluejayA/devflow-aidlc-like/tree/main/skills/aidlc-user-stories
Command: npx skills add https://github.com/bluejayA/devflow-aidlc-like --skill aidlc-user-stories

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the conversion of raw requirements into well-defined user stories that adhere to the INVEST criteria, streamlining the initial planning phase of software development.

Core Features & Use Cases

Automated User Story Generation: Transforms functional and non-functional requirements into actionable user stories.
INVEST Criteria Validation: Ensures generated stories are Independent, Negotiable, Valuable, Estimable, Small, and Testable.
Actor Identification: Automatically identifies and categorizes different user types or systems involved in the requirements.
Use Case: After defining project requirements in requirements.md, use this Skill to generate a comprehensive list of user stories for the development backlog, complete with acceptance criteria and priority.

Quick Start

Use the aidlc-user-stories skill to convert the requirements in devflow-docs/inception/requirements.md into user stories.

Frequently Asked Questions about aidlc-user-stories

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

FAQPage Schema

How do I convert raw requirements into INVEST-compliant user stories?▼

To convert requirements into user stories, process functional and non-functional requirements from a specified markdown file to generate structured stories that meet INVEST criteria, complete with identified actors and acceptance criteria.

What is the INVEST criteria for user stories in agile pre-planning?▼

INVEST criteria for user stories ensures each artifact is Independent, Negotiable, Valuable, Estimable, Small, and Testable, providing a validation framework to streamline the initial planning phase of software development.

How do I generate acceptance criteria and identify actors from a requirements file?▼

Generating acceptance criteria and identifying actors involves processing your requirements markdown file to automatically categorize user types or systems and produce a structured user story artifact for the backlog.

Does this user story generation work with non-functional requirements?▼

Yes, user story generation processes both functional and non-functional requirements, transforming them into actionable user stories that pass INVEST validation and include structured acceptance criteria.

What is the best way to automate user story creation for an agile backlog?▼

Automating user story creation involves running a conversion process on a requirements markdown file to output a comprehensive, prioritized backlog list of INVEST-compliant stories with acceptance criteria.

Do I need a specific markdown format to generate agile user stories?▼

You need to provide requirements in a markdown file, such as devflow-docs/inception/requirements.md, which the conversion process reads to extract functional and non-functional requirements for user story generation.