Run Better Sprint Retrospectives
Sprint teams need structured reflection to turn issues into practical improvements. This skill guides Claude, Codex, or Claude Code through retrospective formats, action items, and follow-up practices.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "sprint-retrospective" from https://skillstore.io/skills/supercent-io-sprint-retrospective.md and its manifest at https://skillstore.io/api/skills/supercent-io-sprint-retrospective/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Using "sprint-retrospective". A scrum master asks for a basic retrospective after a sprint with missed documentation work.
Expected outcome:
The skill returns a Start-Stop-Continue agenda with documentation themes, two action items, owners, and a next-retro follow-up check.
Using "sprint-retrospective". An engineering manager provides notes about deployment issues, delayed reviews, and strong teamwork.
Expected outcome:
The skill groups the notes into Mad, Sad, and Glad themes, then proposes a release checklist and review-time reservation.
Using "sprint-retrospective". A product team lead wants a milestone retrospective after a major release.
Expected outcome:
The skill creates a 4Ls structure with prompts for delivery learning, process gaps, and practical improvements for the next release.
All static findings were adjudicated as false positives. The flagged backticks are Markdown fences or inline tags, and the hardcoded URLs are passive references with no network request or data transfer behavior.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
https://skillstore.io/skills/supercent-io-sprint-retrospective/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/supercent-io-sprint-retrospective?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/supercent-io-sprint-retrospective?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/supercent-io-sprint-retrospective/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/supercent-io-sprint-retrospective.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>supercent-io. (2026). sprint-retrospective security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/supercent-io-sprint-retrospective/audits/4@techreport{supercent-io-supercent-io-sprint-retrospective-2026,
author = {supercent-io},
title = {sprint-retrospective security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/supercent-io-sprint-retrospective/audits/4},
note = {Author version unspecified}
}cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "sprint-retrospective security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "supercent-io"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/supercent-io-sprint-retrospective/audits/4"
identifiers:
- type: other
value: "skillstore:supercent-io-sprint-retrospective:audit:4"
description: "Skillstore immutable audit report identifier"
Create a focused retrospective agenda, format, and action item structure for a completed sprint.
Group team comments into themes and convert them into clear process changes.
Capture lessons from a delivery milestone and identify practical follow-up work.
Create a Start-Stop-Continue retrospective for Sprint 14. We completed 21 points, missed one story, and found two bugs. Include two action items.
Turn these team notes into a Mad-Sad-Glad retrospective. Group repeated themes, remove blame, and create action items with owners.
Design a 60-minute 4Ls retrospective for a cross-functional team. Include time boxes, prompts, voting guidance, and follow-up steps.
Analyze this sprint data and feedback. Identify systemic issues, choose the best retrospective format, and propose a two-sprint improvement plan.
Author
supercent-ioLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Repository
https://github.com/supercent-io/skills-template/tree/main/.agent-skills/sprint-retrospective/Ref
36e07d5e13068e5be64447e8f20b427cf2cbd21a
Maintenance freshness
7/18/2026
Usage
5 downloads · 144 views
File structure
📄 SKILL.md
Improve Lightweight Model Accuracy
Lightweight models can miss context when questions arrive after important information. This skill repeats suitable prompts with guardrails to improve accuracy on selected tasks.
Design Better REST and GraphQL APIs
API teams need consistent contracts before implementation starts. This skill guides resource design, request formats, errors, versioning, and documentation.
Refactor Code Safely
Complex code slows changes and raises regression risk. This skill guides behavior-preserving refactors with tests, extraction patterns, and validation steps.
Create User Guides and Tutorials
Documentation teams need clear product help that users can follow without support. This skill structures onboarding guides, how-to articles, tutorials, and FAQs for end users.
Debug Code Issues Systematically
Bugs waste engineering time when symptoms hide the real cause. This skill guides structured reproduction, isolation, root cause analysis, fixes, and regression prevention.
Plan Agile Tasks and User Stories
Teams often receive broad feature requests without clear tasks, priorities, or acceptance criteria. This skill turns feature ideas into user stories, sprint backlog items, dependencies, and Definition of Done checks.
Plan Agile Sprints With Clear Capacity
by shubhamsaboo
Sprint planning often stalls when scope, estimates, and capacity are unclear. This skill guides Claude, Codex, and Claude Code to create sprint goals, backlog tables, risks, and done criteria.
Plan Focused, Achievable Sprints
by C0ntr0lledCha0s
Teams often overcommit because backlog priority, capacity, and dependencies are considered separately. This skill combines them into a structured sprint plan with measurable goals.
Create Sprint Reports
by Emz1998
Teams need clear sprint summaries for planning, reviews, and stakeholder updates. This skill helps route sprint report requests to a focused reporting workflow.
Run Agile Ceremonies
by 89jobrien
Agile teams need concise ceremonies that keep work visible and action items clear. This skill provides standup, retrospective, sprint progress, and team health formats for Claude, Codex, and Claude Code.
Create Agile Stories and Sprint Plans
by alirezarezvani
Product teams often lose time turning ideas into clear, testable backlog items. This skill helps create user stories, acceptance criteria, estimates, and capacity-based sprint plans.
Plan Agile Releases with Sprint Roadmaps
by Emz1998
Release planning often breaks down when timelines, tasks, and dependencies are scattered. This skill turns project context into sprint schedules, task codes, milestones, and roadmap views.