skills.rest
Nealsch
NealschCOMMUNITY
Explore all skills by this author →
GitHub

Forge-Retrospective-Facilitation

Facilitates blame-free retrospectives that convert findings into tracked improvement actions.

Updated Jul 18, 2026
Search Tags:#retrospective#agile#continuous improvement#process improvement#sdlc#facilitation#action tracking
One-click install
npx skills add https://github.com/Nealsch/ForgeOS --skill forge-retrospective-facilitation-nealsch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Forge-Retrospective-Facilitation
Source: https://github.com/Nealsch/ForgeOS/tree/main/Framework/05-Skills/01-Product/Forge-Retrospective-Facilitation
Command: npx skills add https://github.com/Nealsch/ForgeOS --skill forge-retrospective-facilitation-nealsch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often finish iterations and releases without structured reflection, so recurring friction, process failures, and collaboration issues between humans and AI agents go unaddressed and repeat indefinitely. ## Core Features & Use Cases - Structured Retrospective Facilitation: Runs blame-free retrospectives at iteration, release, and project milestones using a six-step method from safety-setting through recording. - Action Conversion and Tracking: Converts observations into themes, causes, and a small set of owned improvement actions with success signals, then verifies closure of prior actions at the next retrospective. - Use Case: After a release where human-AI session handoffs repeatedly caused friction, use this Skill to elicit findings from session records and decision logs, identify root causes, assign owned improvement actions, and route process changes into roadmap planning. ## Quick Start Facilitate a retrospective for the just-completed iteration using the session handoffs and decision logs as evidence, and produce a retrospective record with owned improvement actions.

Frequently Asked Questions about Forge-Retrospective-Facilitation

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

FAQPage Schema
How do I run a retrospective at the end of an iteration?▼

Run a short-form retrospective at each iteration end: set a blame-free contract, gather observations from the period, cluster them into themes and causes, decide a few owned actions, verify closure of prior actions, and record the results. Releases use the full form.

How to turn retrospective findings into improvement actions?▼

Drive each finding from symptom to plausible cause using evidence from iteration records, then select a small number of high-leverage actions. Each action gets an owner, a first step, and a success signal, and closure is verified at the next retrospective.

Can retrospectives cover human-AI collaboration issues?▼

Yes, session handoffs, agent behaviour, and workflow friction between humans and AI agents are legitimate retrospective material. Session handoff records serve as primary evidence for diagnosing collaboration friction.

When should I not use a retrospective facilitation process?▼

Do not use it to evaluate delivered product value, perform root-cause analysis of a specific production incident, or redesign the roadmap. Those belong to product evaluation, incident analysis, and roadmap planning respectively, though their outputs feed the retrospective.

What happens to improvement actions that stall?▼

Stalled actions are explicitly investigated at the next retrospective rather than silently dropped. The closure-verification step ensures prior actions are either confirmed complete or examined for why they did not progress.

Related Skills

Explore More Product & Management Skills→
KibertumKibertum
16

end

Archive metrics, decisions, and handoff data to the project database.

Official
Advanced
kirillshilinkirillshilin

pm-roadmap-management

Plan and prioritize product roadmaps using RICE, MoSCoW, and ICE frameworks with dependency mapping and capacity planning.

Community
Intermediate
Sharper-FlowSharper-Flow
4

adv-slop-detection

Detect and categorize AI-generated code quality issues via AST analysis and regex patterns.

Official
Advanced
yun520-1yun520-1
38

superpowers-systematic-debugging

Guides users through a four-phase debugging process to identify root causes of technical issues.

Community
Advanced