skills.rest
silenvx
silenvxCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

reflect

Conduct post-session retrospectives with five-whys analysis and generate improvement issues.

1|Updated Jan 3, 2026
Search Tags:#automation#retrospective#root-cause#issue-tracking#process-improvement#log-analysis#five-whys
One-click install
npx skills add https://github.com/silenvx/flow-development-program --skill reflect-silenvx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reflect
Source: https://github.com/silenvx/flow-development-program/tree/main/examples/dekita/.claude/skills/reflect
Command: npx skills add https://github.com/silenvx/flow-development-program --skill reflect-silenvx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to conduct post-session retrospectives by performing a five-whys analysis and turning improvements into issues.

Core Features & Use Cases

  • Self-assessments: run a structured reflection using mandatory checks and the five-whys method to identify root causes.
  • Log analysis: examine session logs to surface actionable insights and improvement opportunities.
  • Issue generation: convert findings into well-scoped issues to track improvements and prevent recurrence.

Quick Start

After a session ends, invoke reflect to generate a concise retrospective and create improvement issues.

Frequently Asked Questions about reflect

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

FAQPage Schema
How do I conduct a post-session retrospective with five-whys analysis?▼

A post-session retrospective with five-whys analysis uses structured prompts and mandatory checks to identify root causes, then converts findings into actionable issues to prevent recurrence.

How do I turn root-cause findings into tracked issues for process improvement?▼

Turning root-cause findings into tracked issues involves formatting outputs as well-scoped issues with explicit requirements, ensuring improvements are documented for issue-tracking and process improvement.

Can I use session log analysis to surface actionable improvement insights?▼

Yes, session log analysis examines logs to surface actionable insights and improvement opportunities, applying structured retrospective methods to translate raw log data into concrete process improvements.

What is the best way to automate root-cause investigation after a session ends?▼

Automating root-cause investigation after a session ends is best handled by invoking a structured retrospective that enforces five-whys analysis, records outcomes, and generates well-scoped issues automatically.

When should I use a structured retrospective over informal post-session reviews?▼

Use a structured retrospective over informal post-session reviews when you need consistent root-cause identification, mandatory checks, and formatted issue outputs to drive measurable process improvement.

Do I need existing issue-tracking setup to run a five-whys retrospective?▼

No existing issue-tracking setup is required to run a five-whys retrospective; the process independently formats outputs as actionable issues with explicit requirements for later tracking.

Related Skills

Explore More Product & Management Skills→
rampstackcorampstackco
523

after-action-report

Run structured after-action reviews using a six-section framework.

Official
Intermediate
hwj123hwjhwj123hwj
4

triage

Classify project issues as bugs or enhancements and manage their triage states.

Community
Intermediate
pradyumnasagarpradyumnasagar
6

agent-handoff

Automate inter-skill data transfer and provenance capture via JSON Material Passports.

Community
Advanced
holseeholsee
10

log-analyzer

text

Community
Intermediate