Skip to content

Agent · SM (retired)

The SM (scrum master) agent is retired. Nothing it did went away — its duties moved into skills you invoke directly, without an agent persona in between.

Where each duty went

Old SM commandReplacementNotes
[SP] Sprint Planningskill:e11-sprint-planningStill owns the sprint-status.yaml schema
[SS] Sprint Statusskill:e11-sprint-statusReads the board, routes to the next workflow
[CS] Create Storyskill:e11-create-storyStory preparation with full implementation context
[VS] Validate Storyskill:e11-create-story (validate)Folded into the story skill
[ER] Epic Retrospectiveskill:e11-retrospectiveNow runs on the multi-perspective roster
[CC] Course Correctionskill:e11-correct-courseAlso reachable from the PM menu ([CC])

Why

Agents-as-personas made sense when they compiled to standalone files. Today every workflow is a first-class skill — a story doesn't need a scrum master to introduce it. The PM agent absorbed the planning-side stewardship (epics, readiness, course correction); the sprint/story mechanics are direct skill invocations, and the Dev agent drives the implementation side.

If an older install had a sm.customize.yaml, the upgrade reports it as unmappable — see Upgrading Foundry.

See also

Phase 4 — Implementation (the full story cycle with the replacement skills) · Agent quick-reference.

Proprietary to Engineering11 LLC.