vivado-impl

Guide selection of Vivado implementation directives and optimization strategies for FPGA designs.

27|5|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/adeleempurpled290/FPGA-Agent-skills --skill vivado-impl-adeleempurpled290
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vivado-impl
Source: https://github.com/adeleempurpled290/FPGA-Agent-skills/tree/main/vivado-impl
Command: npx skills add https://github.com/adeleempurpled290/FPGA-Agent-skills --skill vivado-impl-adeleempurpled290

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

FPGA engineers frequently face challenges navigating the wide array of Vivado implementation directives and optimization options to meet design requirements for timing, routability, and area, often resulting in excessive compile times and suboptimal design performance. This Skill removes the guesswork by providing clear, scenario-based decision guidance for every stage of the Vivado implementation flow.

Core Features & Use Cases

  • Directive Selection Guidance: Access decision tables for opt_design, place_design, phys_opt_design, and route_design to choose the right directives for performance-focused, congestion-heavy, or area-constrained designs.
  • Advanced Flow Support: Get step-by-step guidance for incremental implementation, ECO flows, PSIP physical synthesis, and congestion resolution for complex multi-die and high-utilization FPGA designs.
  • Use Case: If your post-route design has 15 failing timing endpoints and moderate congestion, use this Skill to select the correct phys_opt_design options and incremental implementation strategies to close timing without unnecessary recompile overhead.

Quick Start

Use the vivado-impl skill to recommend the optimal phys_opt_design options for your post-route design with failing timing endpoints and moderate congestion.

Frequently Asked Questions about vivado-impl

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

FAQPage Schema
How do I fix failing timing endpoints and congestion in Vivado implementation?

To resolve timing failures and congestion during Vivado implementation, select appropriate phys_opt_design directives and incremental implementation strategies to optimize post-route designs without excessive recompile overhead.

What is the best way to choose Vivado directives for area-constrained FPGA designs?

Choosing Vivado implementation directives for area-constrained designs involves consulting decision tables for opt_design, place_design, and route_design to match optimization strategies with specific performance and area requirements.

How does phys_opt_design work for timing closure on UltraScale and Versal devices?

The phys_opt_design phase works by applying physical optimization directives to resolve timing closure challenges on UltraScale and Versal devices, targeting failing endpoints through placement and logic adjustments.

Can I use incremental implementation and ECO flows for high-utilization FPGA designs?

Incremental implementation and ECO flows support high-utilization FPGA designs by guiding step-by-step updates to complex multi-die layouts, reducing compile time while maintaining timing closure.

Why does routing congestion occur in Vivado and how can I resolve it?

Routing congestion occurs due to high utilization and suboptimal placement, and you can resolve it by applying targeted place_design and route_design directives alongside congestion resolution strategies.

When do I need PSIP physical synthesis in the AMD Vivado workflow?

PSIP physical synthesis is needed in the AMD Vivado workflow when standard optimization fails to meet timing closure, requiring advanced physical synthesis techniques to improve QoR.