eda-retro

Score improvement proposals and emit retro artifacts with stop and promotion criteria.

8|3|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/Mr-Fang-VLSI/EDAgent --skill eda-retro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eda-retro
Source: https://github.com/Mr-Fang-VLSI/EDAgent/tree/main/skills/eda-retro
Command: npx skills add https://github.com/Mr-Fang-VLSI/EDAgent --skill eda-retro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill provides structured post-experiment retrospectives to identify root causes, categorize failure/success mechanisms, and decide if recursion to a new eda-loop iteration is warranted.

Core Features & Use Cases

  • Consolidates raw artifacts from an experiment batch (summaries, monitors, manifests) into a clear narrative of what happened, why it happened, and what to do next.
  • Supports gating recursion to ensure subsequent iterations are data-driven and risk-aware.
  • Emits a retro artifact that records hypothesis validation, stop/promotion criteria, and concrete next-step actions.

Quick Start

After each experiment batch, run the eda-retro skill to generate a retro summary and decide whether to trigger the next eda-loop.

Frequently Asked Questions about eda-retro

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

FAQPage Schema
How do I automate EDA experiment retrospectives to identify root causes?

EDA retrospectives are automated by consolidating run summaries, monitors, and manifests to identify root causes and categorize failure or success mechanisms. This structured review processes raw experiment batch artifacts to generate a clear narrative of what happened and why.

What is the best way to decide whether to trigger a new EDA recursion iteration?

The best way to gate EDA recursion is by scoring improvement proposals against evidence-driven policies. The retrospective evaluates experiment batch data to enforce risk-aware decisions, emitting explicit stop and promotion criteria to determine if a new iteration is warranted.

How do I gate recursive actions after an EDA experiment batch?

Recursive actions are gated by applying evidence-driven recursion policies to post-experiment data. The process scores improvement proposals based on consolidated run summaries and manifests, ensuring subsequent iterations remain data-driven and explicitly defining stop criteria.

What should a post-experiment retro artifact include for EDA workflows?

A post-experiment retro artifact should include hypothesis validation results, explicit stop and promotion criteria, and concrete next-step actions. It records the root cause analysis and categorizes mechanisms to guide whether a new EDA loop iteration should be triggered.

When do I need a structured retrospective for EDA experiments?

A structured retrospective is needed after completing an EDA experiment batch to consolidate raw artifacts. It is required when you must evaluate hypothesis validation, categorize failure mechanisms, and decide if evidence supports triggering a new recursion iteration.