self-improve

Convert session improvements into prioritized todos with scoped tags.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/peerasak-u/pi-config --skill self-improve-peerasak-u
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: self-improve
Source: https://github.com/peerasak-u/pi-config/tree/main/skills/self-improve
Command: npx skills add https://github.com/peerasak-u/pi-config --skill self-improve-peerasak-u

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies actionable improvements from the current session and converts them into structured improvement suggestions to guide post-session actions.

Core Features & Use Cases

  • Reflect on the session to surface concrete improvement opportunities across agent config, tests, docs, and code.
  • Generate a prioritized set of improvement suggestions and corresponding todos for execution.
  • Create and verify todos with scoped impact (global vs project) and track progress through completion.

Quick Start

Run the self-improve process to review the current session and generate actionable todos for implementation.

Frequently Asked Questions about self-improve

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

FAQPage Schema
How do I generate actionable todos from a development session?▼

To generate actionable todos from a development session, analyze the current work to identify concrete improvements across agent config, tests, docs, and code, then convert them into a prioritized table of structured improvement suggestions.

What is a session retrospective for agent configuration and code quality?▼

A session retrospective for agent configuration and code quality is a review process that surfaces concrete improvement opportunities, validates changes before commit, and creates scoped todos to track implementation progress across global and project levels.

How do I structure improvement suggestions for project-level workflows?▼

Structure improvement suggestions for project-level workflows by creating a prioritized set of actionable todos with proper tags, defining scoped impact for global versus project levels, and validating changes before committing code.

Can I apply session improvements to both global agent config and project tests?▼

Yes, you can apply session improvements to both global agent config and project tests, as the process identifies actionable improvements across agent configuration, skill definitions, tests, docs, and project-level code workflows.

What's the best way to track end-of-session improvements and todos?▼

The best way to track end-of-session improvements is to generate prioritized todos with proper tags and scoped impact, validating changes before commit and tracking progress through completion across global and project configurations.

When should I not use automated session retrospectives for quality improvement?▼

Avoid automated session retrospectives when a session lacks sufficient actionable changes across agent config, tests, docs, or code, as the process requires generating a prioritized table of improvements and validating changes before commit.