self-improvement

Convert user corrections into structured lessons in tasks/lessons.md.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/allexcd/claude-workspace-kit --skill self-improvement-allexcd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: self-improvement
Source: https://github.com/allexcd/claude-workspace-kit/tree/main/.claude/skills/self-improvement
Command: npx skills add https://github.com/allexcd/claude-workspace-kit --skill self-improvement-allexcd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After any user correction or reviewer feedback, this skill captures the mistake and creates a structured lesson entry to prevent recurrence in future tasks.

Core Features & Use Cases

  • Converts corrections into actionable prevention rules stored in tasks/lessons.md.
  • Automates the iterative learning loop by surfacing lessons at session start to guide future work.

Quick Start

Open tasks/lessons.md and add a new Lesson entry with Date, Issue, Correction from user, Root cause, and a concrete Prevention rule.

Frequently Asked Questions about self-improvement

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

FAQPage Schema
How do I track corrections and prevent recurring mistakes in my workflow?

Track corrections by logging each mistake as a structured lesson in tasks/lessons.md. Record the issue, correction, root cause, and a prevention rule to stop recurring mistakes in future workflows.

What is root cause analysis for process improvement after reviewer feedback?

Root cause analysis for process improvement involves identifying the underlying reason for a correction and converting it into a concrete prevention rule. This systematically prevents the same reviewer feedback from recurring.

How do I create a structured lesson entry for workflow corrections?

Create a structured lesson entry by opening tasks/lessons.md and adding the Date, Issue, Correction, Root cause, and a concrete Prevention rule for each workflow correction or mid-task error encountered.

When do I need to review lessons for ongoing self-improvement?

Review accumulated lessons at the start of each session to guide ongoing self-improvement. Surfacing past corrections and prevention rules before working ensures process improvements actively shape future tasks.

Can I apply this process improvement method across different workflows?

Yes, this process improvement method is applicable across workflows after any corrections, reviewer feedback, or mid-task errors. It standardizes iterative learning by writing all prevention rules to tasks/lessons.md.

Do I need any dependencies to convert corrections into lasting improvements?

No dependencies are required to convert corrections into lasting improvements. You only need to open tasks/lessons.md and log entries with the issue, correction, root cause, and prevention rule.