skills.rest
Parachutes87
Parachutes87COMMUNITY
Explore all skills by this author →
WebsiteGitHub

BA-User-Story-Creator

Generate user stories with Given-When-Then acceptance criteria from YAML to Markdown for JIRA-ready documentation.

1|Updated Jan 14, 2026
Search Tags:#project management#collaboration#JIRA#business analysis#user story
One-click install
npx skills add https://github.com/Parachutes87/Rathunas-Skills --skill ba-user-story-creator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: BA-User-Story-Creator
Source: https://github.com/Parachutes87/Rathunas-Skills/tree/main/BA-User-Story-Creator
Command: npx skills add https://github.com/Parachutes87/Rathunas-Skills --skill ba-user-story-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Streamlines the creation of user stories, ensuring they are well-structured and follow best practices, ultimately improving collaboration between analysts and development teams.

Core Features & Use Cases

  • Comprehensive Story Template: Guided structure for writing user stories with proper format.
  • Acceptance Criteria Generation: Automated criteria using Given-When-Then format for clarity.
  • Technical and Business Impact: Document dependencies, impact analysis, and change management strategies.
  • JIRA-Ready Documentation: Direct output tailored for JIRA project management.
  • Use Case: Simplify the process of translating stakeholder requirements into actionable development stories.

Quick Start

Create a user story by following the BA-User-Story-Creator guidance and utilize the provided templates.

Frequently Asked Questions about BA-User-Story-Creator

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

FAQPage Schema
How do I create user stories with Given-When-Then acceptance criteria?▼

Create user stories with Given-When-Then acceptance criteria by using guided templates that automate criteria generation, ensuring proper structure and clarity for business analysis. You simply follow the provided guidance to translate stakeholder requirements into actionable development stories.

What is the best way to document technical impact and dependencies for JIRA user stories?▼

Documenting technical impact and dependencies for JIRA user stories involves outlining change management strategies and impact analysis within a structured template. This approach ensures JIRA-ready documentation directly tailored for project management and collaboration.

Can I use YAML to define user stories for software development?▼

Yes, you can use YAML to define user stories for software development. The creation process relies on YAML for story definition and outputs formatted Markdown, streamlining collaboration between analysts and development teams.

Does automated user story generation work for business analysis in JIRA?▼

Automated user story generation works for business analysis in JIRA by producing direct Markdown output tailored for JIRA project management. It streamlines translating stakeholder requirements into well-structured stories following best practices.

Related Skills

Explore More Software Engineering Skills→
flpbaladaflpbalada
23

theme-epic-story

Structure product work into Theme, Epic, and Story hierarchies.

Community
Basic
blazefluzblazefluz

Work Intake Manager

Convert natural language requests into structured user stories, epics, and bug reports.

Community
Advanced
SanmooSanmoo

jira-assistant

Search, create, update, and transition Jira issues and manage sprints.

Community
Intermediate
haxlyshaxlys

security-requirement-extraction

Converts threat models and business context into actionable security requirements and test plans.

Community
Advanced