Automate end-of-sprint closure by validating PR merges, cleaning branches, and updating Supabase statuses.
npx skills add https://github.com/5hdaniel/Mad --skill sprint-wrapup
Please help me install this Agent Skill. Skill: sprint-wrapup Source: https://github.com/5hdaniel/Mad/tree/main/.claude/skills/sprint-wrapup Command: npx skills add https://github.com/5hdaniel/Mad --skill sprint-wrapup
This Skill automates sprint closure by verifying merges, cleaning branches, recording backlog items, updating statuses, and generating a retrospective summary.
Run the sprint-wrapup workflow for the active sprint and review the generated retrospective summary.
High-intent search queries and answers about installing and using this skill.
Automating sprint closure involves verifying all PR merges for the sprint, cleaning lingering branches, and updating task statuses in Supabase PM tables. The workflow ensures data integrity by validating merges before marking the sprint as completed.
Yes, you can record backlog items into Supabase during end-of-sprint wrap-up by ingesting bugs, follow-ups, and tech debt into the pm_backlog_items table with proper categorization and priorities.
Generating a sprint retrospective automatically requires validating PR merges and updating sprint statuses in Supabase. The process produces a concise summary documenting delivered work, lessons learned, and next-step items.
Yes, sprint wrap-up works specifically with Git-based PRs and Supabase PM tables. It uses SQL and PM API interactions to verify merges, clean worktrees, update pm_sprints and pm_tasks tables, and enforce an auditable trail of sprint activities.
Sprint closure requires cleaning branches and worktrees to maintain a clean repository after development. This ensures lingering open items are closed and the repository remains uncluttered before the sprint status is marked as completed in the project management system.
You should not use automated sprint wrap-up until development work is complete, reviewed, and deployed. Running the workflow earlier risks skipping the verification of open PR merges and failing to capture unfinished backlog items properly.
morris-ySync Linear tickets, finalize commits, and generate postmortems after PR merges.
dnkrowGenerate sprint or milestone retrospectives from git history and plan files.
k97Verify tests before merging or cleaning up git development branches.
lorenzogmGenerate sprint status files from epic files with Python scripts.
