skills.rest
cedricfarinazzo
cedricfarinazzoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

agile-15-retro

Create and publish sprint retrospective pages in Confluence with Jira Roadmap updates.

Updated May 16, 2026
Search Tags:#retrospective#roadmap#jira#confluence#sprint#action-items#retro
One-click install
npx skills add https://github.com/cedricfarinazzo/agile-skills --skill agile-15-retro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agile-15-retro
Source: https://github.com/cedricfarinazzo/agile-skills/tree/main/agile-sprint-close/skills/agile-15-retro
Command: npx skills add https://github.com/cedricfarinazzo/agile-skills --skill agile-15-retro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sprint retrospectives often get siloed, making learnings and improvements hard to track and link to the roadmap.

Core Features & Use Cases

  • Automatically create and publish a Retro page under Retrospectives
  • Import and reflect closeout findings, cross-linked to the sprint closeout
  • Update the Roadmap iteration status and surface next steps to the team

Quick Start

Run the agile-15-retro skill after sprint closure to publish the Retro page and update the Roadmap

Frequently Asked Questions about agile-15-retro

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

FAQPage Schema
How do I automate sprint retrospective creation and roadmap updates in Jira and Confluence?▼

Automating sprint retrospectives involves reading the sprint closeout, generating a cross-linked Retro page under Retrospectives, and updating the Roadmap iteration status in Confluence and Jira.

What is the best way to track retrospective action items with owners and due dates?▼

The best way to track retrospective action items is to compile defined tasks with assigned owners and specific due dates directly within the published Retro page, ensuring accountability for the next sprint cycle.

Does this retrospective automation require an existing Retrospectives folder in Confluence?▼

Yes, the retrospective automation requires an existing Retrospectives folder in Confluence to target end-of-sprint cycles and automatically publish the Retro page and update the Roadmap.

Can I link my sprint closeout findings directly to the newly created retrospective page?▼

Yes, you can link sprint closeout findings directly to the retrospective page. The automation imports closeout findings and automatically cross-links the Retro page back to the sprint closeout.

When do I need to run retrospective automation for my sprint team?▼

You need to run retrospective automation after sprint closure. It targets sprint teams using Confluence and Jira to publish the Retro page and update the Roadmap iteration during end-of-sprint cycles.

Related Skills

Explore More Product & Management Skills→
cedricfarinazzocedricfarinazzo

agile-9-sprint-planning

Scan Jira backlog and sprint state to generate a dependency-ordered sprint proposal.

Community
Intermediate
nroze22nroze22
1

meeting-agent

Extract action items, owners, due dates, and generate Jira tickets from meeting transcripts.

Community
Advanced
cedricfarinazzocedricfarinazzo

agile-5-roadmap

Create Confluence Roadmap index and MVP/Iteration child pages.

Community
Advanced
cfardevcfardev

cu-edit

Modify use case markdown files and synchronize roadmap status.

Community
Intermediate