bmad-sm

Generate developer-ready user stories from PRD and architecture documents.

2|Updated Apr 21, 2025
One-click install
npx skills add https://github.com/akvo/akvo-rag --skill bmad-sm-akvo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-sm
Source: https://github.com/akvo/akvo-rag/tree/main/.agent/skills/bmad-sm
Command: npx skills add https://github.com/akvo/akvo-rag --skill bmad-sm-akvo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of detailed, developer-ready user stories and specifications from Product Requirement Documents (PRDs) and architecture documentation, streamlining the agile development process.

Core Features & Use Cases

  • User Story Generation: Creates complete user stories including title, user type, functionality, business value, timeline, effort, acceptance criteria (UAC/TAC), technical notes, and definition of done.
  • Sprint Planning & Backlog Grooming: Assists in structuring work, estimating story points, assessing velocity, and refining the product backlog.
  • Epic Decomposition: Breaks down large features into manageable, vertical slices.
  • Story Validation: Ensures stories meet the INVEST criteria and are ready for development.
  • Use Case: A product manager provides PRD and architecture documents for a new feature. Bob (the Scrum Master agent) processes these documents to generate a set of well-defined user stories, ready for the development team to pick up in the next sprint.

Quick Start

Use the bmad-sm skill to create user stories from the provided PRD and architecture documents.

Frequently Asked Questions about bmad-sm

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

FAQPage Schema
How do I generate developer-ready user stories from a PRD?

To generate developer-ready user stories from a PRD, provide the document to the Scrum Master agent. It processes the requirements to output complete stories with acceptance criteria, technical notes, and definition of done.

What is the best way to decompose epics into manageable user stories?

Decomposing epics into manageable user stories involves breaking large features into vertical slices. The Scrum Master agent automates epic decomposition by validating story readiness against INVEST criteria to ensure they are ready for development.

Can I use agile sprint planning automation with architecture documentation?

Yes, agile sprint planning automation works with architecture documentation. The agent processes both PRDs and architecture docs to structure work, estimate story points, assess velocity, and refine the product backlog.

Does backlog grooming require validating stories against INVEST criteria?

Backlog grooming requires validating stories against INVEST criteria to ensure readiness. The Scrum Master agent strictly adheres to agile methodologies by checking INVEST compliance during story generation and backlog refinement.

What is included in complete user stories for agile development?

Complete user stories for agile development include a title, user type, functionality, business value, timeline, effort, acceptance criteria (UAC/TAC), technical notes, and definition of done. The agent generates these specifications automatically.

Why do my product backlog items fail to meet developer-ready specifications?

Product backlog items fail to meet developer-ready specifications when they lack detailed acceptance criteria, technical notes, or INVEST validation. The agent processes PRDs to produce complete, developer-ready specifications.