failure-evolution-loop

name	failure-evolution-loop
description	Real failure capture, root-cause analysis, regression design (outputs a runnable-test SPECIFICATION — does not write test files directly), and memory-driven improvement for Yuri OS / Yuri. Inspired by Zenkai / Saiyan Power, translated into enterprise-safe system behavior. Use when the user says 'capture this failure', 'analyze root cause', 'prevent regression', or 'learn from this bug'.
version	1.0.0
status	active
enterprise_ready	true
non_destructive_default	true
triggers	["/yuri zenkai","/zenkai","/fel"]
requires	["enterprise-control-plane","audit-events","rollback-policy"]
scope	harness
invocation	workflow

Failure Evolution Loop Skill

When to use

Use this skill when the user asks Yuri OS / Yuri to perform work involving:

• failure_event
• test_output
• user_feedback
• diff
• session_log
• domain_report
• clone_reports

Also use it when the active task matches this operating principle:

Convert real failures and weak outputs into structured improvement without rewarding avoidable damage, self-induced breakage, or speculative memory changes.

When not to use

Do not use this skill when:

• the task is trivial and does not need system-level treatment
• no target, goal, or evidence source is available
• the user explicitly requests no architectural expansion
• the task would require destructive action without approval
• the extension would duplicate an already active domain without adding value

Trigger phrases

• "run failure-evolution-loop"
• "use Failure Evolution Loop"
• "turn this into Yuri OS DNA"
• "analyze and integrate this safely"
• "enterprise-ready extension"
• "non-destructive implementation plan"
• "bake this into the system"

Required inputs

input:
  goal: string
  artifact_type: failure_event | test_output | user_feedback | diff | session_log | domain_report | clone_reports
  target: string
  constraints:
    enterprise_mode: true
    destructive_actions_allowed: false
    require_audit_trail: true
     
  
       
     []