me-4

Score RED failure retry strategies across four dimensions with MICRO-EVOLVE logging.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/gapfDev/workflow --skill me-4
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: me-4
Source: https://github.com/gapfDev/workflow/tree/main/c1.2/.claude/skills/me-4
Command: npx skills add https://github.com/gapfDev/workflow --skill me-4

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured, quantitative framework to evaluate and retry failed RED tasks, enabling consistent improvement and faster recovery.

Core Features & Use Cases

  • Four-Dimensional scoring: Dg, C, A, E scores to guide retry strategies.
  • Structured analysis: Clear guidance on root cause, scope, and potential regressions.
  • Standardized logging: MICRO-EVOLVE log format records all attempts for traceability and audits.

Quick Start

Run ME-4 on the latest RED incident to score Diagnostic, Clarity, Accuracy, and Economy, then log the result in the MICRO-EVOLVE format.

Frequently Asked Questions about me-4

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

FAQPage Schema
How do I score retry strategies for RED failure diagnostics?

Score retry strategies for RED failures by evaluating four dimensions: Diagnostic, Clarity, Accuracy, and Economy. Calculate a simple average to quantify quality and guide consistent improvement during debugging sessions.

What is the best way to analyze root causes for code changes during iteration?

Analyze root causes for code changes using a four-dimensional scoring framework. This provides explicit sub-questions to evaluate scope and potential regressions, enabling controlled iteration planning across code modifications.

How do I log diagnostic-heavy debugging sessions for traceability?

Log diagnostic-heavy debugging sessions using the MICRO-EVOLVE format. This standardized log records all retry attempts and post-failure analysis results to ensure traceability and facilitate audits.

Can I use retry strategy scoring for controlled iteration planning?

Use retry strategy scoring for controlled iteration planning by quantifying diagnostic quality across code changes. The scoring framework evaluates scope and regressions to enable faster recovery and structured improvement.

When do I need a quantitative framework for post-failure analysis?

Use a quantitative framework for post-failure analysis when you need consistent improvement and faster recovery from RED issues. It scores retry quality to guide structured root cause investigations and prevent regressions.