evolution-loop

Scan session logs and failure autopsies to update or create skills.

8|1|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/bordenet/superpowers-plus --skill evolution-loop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evolution-loop
Source: https://github.com/bordenet/superpowers-plus/tree/main/skills/observability/evolution-loop
Command: npx skills add https://github.com/bordenet/superpowers-plus --skill evolution-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Self-improvement cycle: scans session logs, failure autopsies, and decision logs for recurring patterns. Auto-generates skill updates or new skills. Tracks improvement metrics over time.

Core Features & Use Cases

  • Detect recurring failure patterns across sessions and generate targeted skill updates.
  • Auto-create new skills from discovered patterns and track their adoption.
  • Measure improvement metrics over time to validate effectiveness and guardrails.

Quick Start

Run evolution-loop after a major session to identify recurring patterns and queue skill updates.

Frequently Asked Questions about evolution-loop

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

FAQPage Schema
How do I automate skill updates from recurring failure patterns?

You can automate skill updates by scanning session logs, failure autopsies, and decision logs for recurring patterns, then auto-generating targeted skill modifications or new skills to resolve them. This process drives continuous self-improvement and tracks improvement metrics over time.

What is failure autopsy analysis for self-improvement?

Failure autopsy analysis for self-improvement is the process of examining past failures and decision logs to identify recurring patterns. The evolution-loop automates this by scanning session outputs to detect issues and auto-create skills that prevent similar failures.

When should I run pattern detection on session logs?

You should run pattern detection on session logs after a major session, lengthy operations, or when recurring issues are suspected. Operating at these points allows the system to identify repeating failure patterns and queue necessary skill updates efficiently.

Do I need retrospective notes and decision logs to use evolution-loop?

Yes, you need retrospective notes, failure autopsy outputs, and decision logs. The evolution-loop requires access to these inputs to accurately detect recurring failure patterns across sessions and generate valid skill updates.

How do I measure the effectiveness of auto-created skills?

You measure the effectiveness of auto-created skills by tracking improvement metrics over time. The evolution-loop validates effectiveness by monitoring these metrics and applying guardrails to ensure the new skills actually resolve the detected failure patterns.

Best way to auto-generate new skills from discovered patterns?

The best way to auto-generate new skills from discovered patterns is to use an automated evolution loop that scans session logs and failure autopsies, detects recurring issues, and directly authors skill updates while tracking their adoption metrics.