eda-chief

Map legacy eda-chief calls to current agent policies and eda-loop execution.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides a backward-compatible shim for historical eda-chief invocations so older prompts and scripts continue to work without modifying legacy callers, while ensuring requests are governed by the repository-level agent policy and produce concise, artifact-driven outputs.

Core Features & Use Cases

  • Compatibility routing: Load repository routing policy and translate chief-style briefs into scoped execution briefs that downstream orchestrators understand.
  • Governed dispatch: Route execution to the eda-loop and selectively invoke control skills such as theory veto and retrospection when required by risk or cost.
  • Audit-friendly outputs: Keep replies short, attach required artifacts, and follow mandatory artifact contracts and autonomy guardrails for safe recursive loops.
  • Use case: Run a legacy automation that still references eda-chief and have it automatically follow AGENTS.md policies, dispatching work to modern skills without manual rewrite.

Quick Start

Invoke the eda-chief compatibility shim when an older prompt or script calls eda-chief so it loads AGENTS.md, translates the brief, and dispatches execution to eda-loop.

Frequently Asked Questions about eda-chief

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

FAQPage Schema
How do I route legacy eda-chief calls to current agent workflows without modifying old scripts?

Legacy eda-chief calls are routed to current workflows by loading the AGENTS.md routing policy and translating chief-style briefs into scoped execution briefs that downstream orchestrators understand.

What is artifact-driven output in EDA research orchestration?

Artifact-driven output in EDA research orchestration produces concise replies with required artifacts attached, following mandatory artifact contracts and autonomy guardrails for safe recursive loops.

How do I map old prompts to modern governance flows for EDA experiments?

Old prompts are mapped to modern governance flows by dispatching execution to eda-loop and selectively invoking control skills such as theory veto and retrospection based on risk or cost requirements.

Can I use eda-chief compatibility routing for repository-level automation?

Yes, eda-chief compatibility routing applies to repository-level orchestration, ensuring older prompts and scripts automatically follow agent policies and dispatch work to modern skills without manual rewrite.

When do I need a compatibility shim for legacy EDA prompts?

A compatibility shim is needed when historical prompts or scripts invoke eda-chief and must continue working without modification while governed by repository-level agent policies and producing concise artifact-driven outputs.

What are the limitations of routing legacy EDA calls through a compatibility layer?

The compatibility layer relies on AGENTS.md for global routing policy and requires downstream orchestrators like eda-loop; it cannot function autonomously without these governance flows and artifact contracts.