generate-stories

Convert functional requirements documents into structured user stories for Azure DevOps.

Updated Dec 29, 2025
One-click install
npx skills add https://github.com/TabTabGo/dev-agents --skill generate-stories-tabtabgo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generate-stories
Source: https://github.com/TabTabGo/dev-agents/tree/main/platforms/claude/.claude/skills/generate-stories
Command: npx skills add https://github.com/TabTabGo/dev-agents --skill generate-stories-tabtabgo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables teams to convert detailed Functional Requirement Documents into structured user stories, facilitating efficient project planning and traceability.

Core Features & Use Cases

  • FRD Parsing and Extraction: Analyzes FRD files to identify actors, functional requirements, acceptance criteria, dependencies, and priorities.
  • User Story Generation: Converts extracted requirements into clear, testable user stories formatted for Agile teams.
  • Azure DevOps Integration: Automates creation of user stories, assigns to sprints or backlog, and links dependencies within Azure DevOps.
  • Use Case: Imagine a product team finishes FRD approval; this Skill can rapidly generate a comprehensive set of user stories for sprint planning, saving hours of manual input.

Quick Start

Load your FRD document, review the generated user stories in the markdown report, and use the integrated Azure DevOps commands to automatically add them to your project backlog with proper sprint and dependency linkages.

Frequently Asked Questions about generate-stories

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

FAQPage Schema
How do I convert a Functional Requirements Document into user stories for Azure DevOps?

To convert a Functional Requirements Document into user stories, load your FRD file to extract actors, functional requirements, and acceptance criteria, then generate formatted stories and push them directly to the Azure DevOps backlog.

What is the best way to automate user story creation from an FRD for Agile sprint planning?

Automating user story creation from an FRD involves parsing the document to identify priorities and dependencies, generating testable stories formatted for Agile teams, and assigning them to sprints via Azure DevOps integration commands.

How do I link dependencies and assign sprints when generating user stories from an FRD?

To link dependencies and assign sprints when generating user stories, use the integrated Azure DevOps commands to automatically map extracted FRD relationships and push the structured stories into the appropriate backlog sprints.

Do I need Azure DevOps MCP connectors to generate user stories from an FRD?

Azure DevOps MCP connectors are required to automatically create user stories, assign them to sprints, and link dependencies within Azure DevOps, though you can still generate stories as a markdown report without direct integration.

Can I review generated user stories before adding them to the Azure DevOps backlog?

You can review generated user stories in a markdown report before adding them to the Azure DevOps backlog, allowing you to verify the extracted actors, acceptance criteria, and dependencies prior to sprint assignment.

What functional requirements are extracted when parsing an FRD for Agile user story generation?

Parsing an FRD for Agile user story generation extracts actors, functional requirements, acceptance criteria, dependencies, and priorities to ensure the resulting stories are comprehensive, testable, and formatted for project management.