skills.rest
ntholm86
ntholm86COMMUNITY
Explore all skills by this author →
WebsiteGitHub

hansei

Analyze historical logs and decision records to identify recurring process issues.

1|Updated Apr 18, 2026
Search Tags:#retrospective#self-assessment#team reflection#process evaluation#improvement critique
One-click install
npx skills add https://github.com/ntholm86/autonomous-agent-skills --skill hansei-ntholm86
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hansei
Source: https://github.com/ntholm86/autonomous-agent-skills/tree/main/archive/v2/hansei
Command: npx skills add https://github.com/ntholm86/autonomous-agent-skills --skill hansei-ntholm86

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hansei helps teams evaluate and critique their improvement cycles to identify blind spots, recurring issues, and methodological gaps, ultimately enhancing the effectiveness of their development process.

Core Features & Use Cases

  • Trail Examination: Analyze historical logs and decision records to assess progress and detect patterns.
  • Pattern Identification: Spot recurring issues and determine whether they require structural changes or superficial fixes.
  • Meta-Improvement: Provide insights into the effectiveness of current methodologies and suggest adjustments for future cycles.
  • Use Case: Teams conducting iterative development can use Hansei after each cycle to reflect on what went well, what didn't, and how to improve their process for subsequent iterations.

Quick Start

Input the recent improvement logs and decision records to generate a reflection on the effectiveness of your current process.

Frequently Asked Questions about hansei

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

FAQPage Schema
How do I analyze iterative improvement cycles for process evaluation?▼

To analyze iterative improvement cycles, you input historical logs and decision records to assess progress, detect recurring patterns, and identify methodological gaps in your development process.

What is the best way to identify recurring issues and blind spots in team retrospectives?▼

Identifying recurring issues in team retrospectives requires examining historical decision records to spot structural gaps and procedural blind spots, determining whether issues need structural changes or superficial fixes.

Can I use historical logs to evaluate the effectiveness of my current development methodology?▼

Yes, you can use historical logs to evaluate your current development methodology by analyzing past improvement cycles to provide meta-improvement insights and suggest adjustments for future iterations.

Do I need decision records and historical logs to conduct a process review?▼

Yes, decision records and historical logs are required as input data to conduct a process review, enabling the evaluation of structural and procedural gaps within your iterative improvement cycles.

When should I conduct a self-assessment of my improvement process methodology?▼

You should conduct a self-assessment of your improvement process methodology after each iterative development cycle to reflect on progress, critique effectiveness, and adjust methodologies for subsequent iterations.

Related Skills

Explore More Software Engineering Skills→
LazyNinja435LazyNinja435
1

Huddle

Synthesize session logs and decision records for persistent architectural guidance.

Community
Intermediate
terrylicaterrylica
62

link-validation

Scan markdown files with lychee to detect broken links and path policy violations.

Community
Intermediate
lengo0951lengo0951

ck:kanban

Manage task boards for project tracking and team collaboration.

Community
Intermediate
iani-kuliiani-kuli

find-bugs

Analyze git branch diffs for security vulnerabilities and code quality defects.

Community
Advanced