skills.rest
masa-codehub
masa-codehubCOMMUNITY
Explore all skills by this author →
GitHub

conducting-retrospectives

Guide YWT or KPT retrospectives to produce documented improvement actions.

Updated Aug 18, 2025
Search Tags:#retrospective#root-cause-analysis#process-improvement#ywt#kpt#action-planning
One-click install
npx skills add https://github.com/masa-codehub/gemini_agent --skill conducting-retrospectives
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: conducting-retrospectives
Source: https://github.com/masa-codehub/gemini_agent/tree/main/.gemini/skills/conducting-retrospectives
Command: npx skills add https://github.com/masa-codehub/gemini_agent --skill conducting-retrospectives

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Replaces the work of reflecting on completed tasks with structured frameworks (YWT or KPT) to derive concrete improvement actions that can be codified as assets.

Core Features & Use Cases

  • Framework selection between YWT (root-cause analysis of technical failures or unknown behaviors) and KPT (process improvement across workflows).
  • Fact gathering and analysis guided by built-in templates in assets, enabling clear documentation of observations and alignment with SSOT.
  • Action formulation and assetization, including multi-hypothesis planning and structured reporting to ADR/retrospective repositories.

Quick Start

Initiate a retrospective using YWT or KPT to collect facts, identify improvement actions, and document the results.

Frequently Asked Questions about conducting-retrospectives

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

FAQPage Schema
How do I turn retrospective reflections into concrete improvement actions?▼

To turn retrospective reflections into concrete improvement actions, use structured frameworks like YWT or KPT to gather facts, formulate multi-hypothesis action plans, and document results into ADR repositories using built-in templates.

What is the difference between YWT and KPT frameworks for process improvement?▼

YWT is used for root-cause analysis of technical failures or unknown behaviors, while KPT focuses on process improvement and optimization across workflows. Selecting the right retrospective framework guides targeted action planning.

When should I use a structured retrospective framework?▼

Use a structured retrospective framework when replacing unstructured reflection with fact gathering and analysis, ensuring observations align with a single source of truth and yield codifiable assets.

Can I document retrospective results directly into an ADR repository?▼

Yes, you can document retrospective results directly into an ADR repository. The process uses structured reporting and built-in templates to assetize improvement actions and maintain clear documentation.

What is the best way to conduct root-cause analysis for technical failures?▼

The best way to conduct root-cause analysis for technical failures is applying the YWT framework to collect facts, analyze unknown behaviors, and generate hypothesis-based action plans for codified process improvements.

Related Skills

Explore More Software Engineering Skills→
sngmdsngmd
3

okr-retrospective

Analyze OKR results, score achievement, and generate retrospective reports.

Community
Advanced
autostay-krautostay-kr
1

retro

Facilitate structured sprint retrospectives and generate prioritized action plans.

Official
Intermediate
GerstepGerstep
105

gtd

Convert GTD.md items into executable tasks and write plans to MMDD-<slug>.md.

Community
Advanced
RyoMurakami1983RyoMurakami1983
2

furikaeri-practice

Facilitate structured retrospectives using KPT, YWT, 5 Whys, and SMART goals.

Community
Intermediate