Capture Sprint lessons and append validated improvements to improvements.json.
npx skills add https://github.com/sohei56/maul-team --skill retrospective-sohei56
Please help me install this Agent Skill. Skill: retrospective Source: https://github.com/sohei56/maul-team/tree/main/skills/retrospective Command: npx skills add https://github.com/sohei56/maul-team --skill retrospective-sohei56
This Skill prevents recurring Sprint problems from being forgotten by guiding a structured retrospective, recording actionable improvements, and ensuring the Sprint reaches a valid completion state.
Run the retrospective Skill after Sprint review to record improvements, complete the Sprint, and determine the appropriate next workflow phase.
High-intent search queries and answers about installing and using this skill.
To convert sprint retrospective lessons into actionable improvements, this Skill guides a structured reflection across process, communication, tooling, and code quality, then appends validated entries to improvements.json with full Sprint context.
The best way to track agile improvement actions after a sprint review is appending validated entries to an improvements.json file, preserving auditability and decision links while keeping the improvement backlog manageable through periodic consolidation.
Yes, you need Scrum state files and sanctioned state-management scripts to run this retrospective Skill, as they validate updates, preserve auditability, and safely advance the workflow to a valid Sprint completion state.
Yes, you can automate sprint completion and backlog consolidation for product owners by periodically reviewing active improvements, archiving obsolete items, updating Sprint status, and coordinating continuation decisions in human or agent-driven modes.
Recurring Sprint problems get forgotten without structured improvement tracking because actionable improvements are not recorded, validated, or consolidated, causing the team to lose auditability and repeat the same process failures across future Sprints.
A structured retrospective handles workflow completion by updating the Sprint status and coordinating the appropriate continuation decision, which either prepares the next Sprint or closes the product workflow based on human or product-owner agent inputs.
JingyiWngConduct post-epic retrospectives from story files and sprint-status.yaml.
diegosanchespereira1Summarize sprint status and recommend the next BMad workflow action.
eternnoirManage sprint and iteration lifecycles for Agile teams.
shishiGuide teams through a five-phase Sprint Retrospective and record actions in scrum.ts.
