self-improvement

Name: self-improvement
Availability: InStock
Author: Wilder1222

Evaluates sprint outcomes and generates improvement reports in docs/superomni/improvements/ for software teams.

2|Updated Mar 25, 2026

Search Tags:#documentation #self-improvement #retrospective #process #sprint #first-principles

Ready to run

npx skills add https://github.com/Wilder1222/superomni --skill self-improvement-wilder1222

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: self-improvement
Source: https://github.com/Wilder1222/superomni/tree/main/skills/self-improvement
Command: npx skills add https://github.com/Wilder1222/superomni --skill self-improvement-wilder1222

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Canonical reflection skill for post-task and post-sprint review. Applies first-principles reflection across process quality and delivery history. Produces improvement reports in docs/superomni/improvements/ and can generate retrospective evidence. Triggers: "self-improve", "evaluate performance", "reflect on execution", "how did we do", "what could be better", "evaluate this sprint", "improve process", "first principles review", "/retro", "weekly retro", "what did we ship", "engineering retrospective".

Core Features & Use Cases

Generates structured retrospectives and improvement reports.
Evaluates sprint outcomes using a first-principles framework.
Publishes artifacts to docs/superomni/improvements/ for audit and learning.

Quick Start

Run self-improvement to analyze the latest sprint and generate a documented improvement plan.

Frequently Asked Questions about self-improvement

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

FAQPage Schema

How do I generate a post-sprint retrospective report for my software team?▼

Post-sprint retrospectives are generated by evaluating sprint outcomes through a first-principles framework, producing structured improvement reports stored under the docs/superomni/improvements/ directory for continuous learning.

What is first-principles reflection in an engineering retrospective?▼

First-principles reflection analyzes process quality and delivery history by breaking down sprint outcomes into fundamental truths, generating actionable improvement evidence rather than relying on assumptions or surface-level observations.

How do I track continuous improvement actions after a sprint review?▼

Continuous improvement actions are tracked by auto-generating documented improvement plans and retrospective artifacts, ensuring post-task and post-sprint learnings are auditable and stored for future reference.

Does the retrospective process enforce a strict completion protocol per session?▼

The retrospective process enforces a strict completion protocol per session using statuses like DONE, DONE_WITH_CONCERNS, or BLOCKED, ensuring clear visibility into execution outcomes and unresolved blockers.

How do I evaluate what we shipped during the latest sprint?▼

To evaluate what you shipped, trigger a performance evaluation on the latest sprint to analyze delivery history, assess process quality, and output an evidence-based improvement report.

Can I run a weekly retro without manual documentation overhead?▼

Weekly retrospectives can be run without manual documentation overhead by auto-generating structured improvement reports and retrospective evidence directly to your repository's docs directory.