hansei

Guide structured, blame-free retrospectives through four sequential phases to extract systemic lessons.

6|1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/kouko/monkey-skills --skill hansei
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hansei
Source: https://github.com/kouko/monkey-skills/tree/main/philosophers-toolkit/skills/hansei
Command: npx skills add https://github.com/kouko/monkey-skills --skill hansei

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps individuals conduct a blame-free, structured retrospective to turn failures, surprises, or disappointing outcomes into systemic insights and a single actionable next step. The Skill prevents premature conclusions, separates observable facts from interpretation, and avoids self-blame loops so learning is concrete and implementable.

Core Features & Use Cases

  • Phase-driven four-step process: Confirm Facts, Introspection, Learning, Next Step, enforced in strict order.
  • Guided questioning that separates facts from interpretation, refocuses on the user's role, and escalates shallow takeaways into structural changes.
  • Safety and tone guardrails to avoid blame, mitigate emotional harm, and stop progression if the user is distressed.
  • Use case: a PM reflecting on a missed deadline — the Skill elicits facts, surfaces the PM's overlooked assumptions, derives a process change (e.g., dependency risk checklist), and defines a single measurable action for tomorrow.

Quick Start

Ask the assistant to run a Hansei by stating the event and providing only factual details, then proceed when the agent prompts Phase 1.

Frequently Asked Questions about hansei

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

FAQPage Schema
How do I conduct a blame-free postmortem after a project failure?

A blame-free postmortem separates observable facts from interpretations to extract systemic lessons. You guide a structured reflection through four sequential phases, preventing premature conclusions and avoiding self-blame loops to ensure learning remains concrete and implementable.

What is the best way to structure a personal retrospective for systemic insights?

The best way to structure a personal retrospective is enforcing a strict four-step sequence: Confirm Facts, Introspection, Learning, and Next Step. This phase-driven process separates facts from interpretation, refocuses on your role, and escalates shallow takeaways into structural changes.

Can I use structured self-reflection to process team conflicts and technical decisions?

Yes, you can use structured self-reflection to process team conflicts and technical decisions. The guided questioning applies to individual retrospectives after project delays, feature failures, or personal mistakes where you seek structural insight rather than blame.

How do I turn a missed deadline into a process change without self-blame?

Turning a missed deadline into a process change without self-blame requires separating facts from interpretation during introspection. Safety guardrails mitigate emotional harm, stop progression if distressed, and help derive a single actionable next step like a dependency risk checklist.