bmad-agent-sm

Generate prioritized sprint plans and implementation-ready user stories with acceptance criteria.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/amitmishra-byldd/Bmad-Note-Maker --skill bmad-agent-sm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-agent-sm
Source: https://github.com/amitmishra-byldd/Bmad-Note-Maker/tree/main/_bmad/bmm/4-implementation/bmad-agent-sm
Command: npx skills add https://github.com/amitmishra-byldd/Bmad-Note-Maker --skill bmad-agent-sm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often ship vague or incomplete user stories and lack a consistent sprint plan, causing wasted implementation time and misaligned expectations. This Skill provides a technical Scrum Master persona that enforces clarity, drives checklist-driven preparation, and ensures every story is implementation-ready.

Core Features & Use Cases

  • Sprint planning (SP): Generate or update a prioritized sprint plan that sequences tasks for developer agents.
  • Story preparation (CS): Produce implementation-ready user stories with acceptance criteria, context, and clear tasks for developers.
  • Retrospective & correction (ER / CC): Run party-mode reviews across an epic and recommend corrective action when mid-sprint changes are needed.
  • Activation workflow: On activation, load config via bmad-init (store {user_name} and {communication_language}), optionally load project-context.md as a foundation, greet the user in their language, present capabilities, and then STOP and WAIT for user input to select a capability.

Quick Start

Ask Bob to prepare a prioritized two-week sprint plan and produce implementation-ready stories with acceptance criteria for the highest-priority epic.

Frequently Asked Questions about bmad-agent-sm

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

FAQPage Schema
How do I prepare implementation-ready user stories for development teams?▼

Implementation-ready user stories are prepared by applying checklist-driven preparation that enforces clarity, producing actionable stories with explicit acceptance criteria, context, and clear tasks for developers.

What is the best way to generate a prioritized sprint plan for developer agents?▼

The best way to generate a prioritized sprint plan is to sequence tasks for developer agents during sprint planning, ensuring every story is implementation-ready and aligned with epic goals.

Can I run mid-sprint course corrections and retrospectives across an epic?▼

Yes, you can run party-mode reviews across an epic to recommend corrective actions, enabling mid-sprint course corrections when changes are needed during the sprint.

Do I need project configuration variables to start sprint planning?▼

Yes, sprint planning requires project configuration variables such as {user_name} and {communication_language}, and optionally uses project-context.md as a foundational reference.

How does a technical Scrum Master persona help with backlog management?▼

A technical Scrum Master persona helps with backlog management by enforcing story clarity and driving checklist-driven preparation, which prevents wasted implementation time caused by vague or incomplete user stories.

Why do vague user stories cause wasted implementation time?▼

Vague user stories cause wasted implementation time and misaligned expectations because development teams lack the clear acceptance criteria and context needed to execute tasks efficiently.