bmad-agent-sm

Convert sprint goals and story requests into structured sprint plans and developer-ready stories.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves sprint planning confusion by converting vague requests into crisp, actionable agile work items with clear scope and sequencing.

Core Features & Use Cases

  • Sprint planning orchestration: Turns sprint goals into an ordered sprint plan that the dev agent can follow for implementation.
  • Story preparation with implementation-ready context: Produces user stories that include the required details so developers can start without clarification churn.
  • Agile ceremony guidance and course correction: Supports epic review/retrospective alignment and determines next steps when changes are needed mid-implementation.

Use case example: When a user asks for sprint planning or story creation for upcoming development, the scrum master flow produces a sprint plan and developer-ready stories that reduce ambiguity and rework.

Quick Start

Ask to talk to Bob and request sprint planning for your next iteration.

Frequently Asked Questions about bmad-agent-sm

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

FAQPage Schema
How do I convert vague sprint goals into structured sprint plans?

Sprint planning converts vague goals into structured sprint plans by applying checklist-driven outputs to sequence ordered development tasks and developer-ready stories for agile execution.

How do I create user stories that are ready for immediate development?

Story preparation produces implementation-ready user stories by injecting required technical context and scope details, reducing clarification churn so developers can start coding immediately.

What is the best way to handle scope changes during an active sprint?

Handling scope changes during a sprint requires agile ceremony guidance and corrective course actions that determine next steps and realign epic reviews when implementation shifts occur.

Can I run an epic retrospective alignment without losing project context?

Epic retrospective alignment loads available project context and applies structured review workflows to maintain scope continuity and document corrective course actions.

Does this scrum master workflow support backlog management and agile ceremonies?

The scrum master workflow supports backlog management and agile ceremonies by routing requests to registered sub-skills for sprint planning, story creation, and retrospective alignment.

Why do my sprint planning sessions result in developer ambiguity and rework?

Sprint planning ambiguity occurs when story requests lack structured technical context, which this workflow resolves by enforcing crisp outputs and developer-ready story details.