kaizen

Identifies friction in sessions and proposes actionable fixes for workflows or documents.

29|4|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/matsen/bipartite --skill kaizen-matsen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kaizen
Source: https://github.com/matsen/bipartite/tree/main/skills/kaizen
Command: npx skills add https://github.com/matsen/bipartite --skill kaizen-matsen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify friction points from a session and translate them into actionable improvements to skills, CLAUDE.md, docs, or workflow.

Core Features & Use Cases

  • Diagnose friction points from interaction history.
  • Propose concrete, actionable fixes to documents or workflows.
  • Optionally implement fixes when requested.

Quick Start

Invoke /kaizen after a session to generate a concrete, actionable improvement.

Frequently Asked Questions about kaizen

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

FAQPage Schema
How do I diagnose workflow friction points from a Claude session and translate them into documentation improvements?

To diagnose workflow friction points, review your interaction history to identify repeat issues, then translate them into actionable improvements for skills, CLAUDE.md, docs, or workflows.

What is the best way to update CLAUDE.md after encountering repeated issues in a session?

Updating CLAUDE.md after repeated issues involves identifying the friction point from the session and proposing a concrete, testable fix with clear scope and optional implementation steps.

Can I automatically apply fixes to my workflow documentation after a problematic interaction?

Yes, you can automatically apply fixes to workflow documentation by proposing concrete improvements after friction and optionally implementing the fixes directly to your docs or skills when requested.

How do I identify actionable improvements for skills when a workflow is not working as expected?

Identifying actionable improvements for skills when a workflow is not working requires diagnosing the friction points from the interaction history and translating them into concrete, testable fixes.

Does continuous improvement for Claude skills require manual review of the entire interaction history?

Continuous improvement for Claude skills does not necessarily require manual review of the entire interaction history; it targets specific friction points to generate concrete improvements and reduce repeat issues.

When should I not use session-based workflow improvement for documentation updates?

You should avoid session-based workflow improvement for documentation updates when the friction point lacks a clear scope or cannot be translated into a concrete, testable fix for future interactions.