physical-design

Orchestrate SoC physical design from gate-level netlist to GDS-II.

180|46|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/chuanseng-ng/digital-chip-design-agents --skill physical-design-chuanseng-ng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: physical-design
Source: https://github.com/chuanseng-ng/digital-chip-design-agents/tree/main/plugins/pd/skills/physical-design
Command: npx skills add https://github.com/chuanseng-ng/digital-chip-design-agents --skill physical-design-chuanseng-ng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openroad, librelane, innovus, icc2, aprisa, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the full physical design flow, including floorplanning, placement, clock tree synthesis, routing, and sign-off, closing timing and power.

Core Features & Use Cases

  • Automated Physical Design Flow: Full end-to-end physical design automation from gate-level netlist to GDS-II.
  • Multi-tool Support: Integrates with various EDA tools like OpenROAD, LibreLane, Cadence Innovus, Synopsys IC Compiler 2, and Siemens Aprisa.
  • Stages: Floorplanning, placement, CTS, routing, timing optimization, power optimization, area optimization, and sign-off.
  • Use Case: Ideal for complex SoC designs where timing and power closure are critical.

Quick Start

Run the full physical design flow for the 'my_design.def' netlist using the 'physical-design' skill.

Frequently Asked Questions about physical-design

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

FAQPage Schema
How do I automate the physical design flow from gate-level netlist to GDS-II?

To automate the physical design flow from gate-level netlist to GDS-II, you can orchestrate end-to-end stages including floorplanning, placement, CTS, routing, and sign-off to close timing and power for complex SoC designs.

Does this physical design skill support Cadence Innovus and Synopsys IC Compiler 2?

Yes, this physical design skill supports multi-tool environments and integrates natively with Cadence Innovus, Synopsys IC Compiler 2, Siemens Aprisa, OpenROAD, and LibreLane to execute the full SoC design flow.

What is the best way to achieve timing and power closure in complex SoC designs?

The best way to achieve timing and power closure in complex SoC designs is to run an automated physical design flow that performs dedicated timing optimization, power optimization, and area optimization through to final sign-off.

Can I use OpenROAD for floorplanning and routing in an automated SoC physical design process?

Yes, you can use OpenROAD for floorplanning, placement, CTS, and routing within an automated physical design process that orchestrates these stages to generate a final GDS-II file.

What stages are included in an end-to-end physical design flow for SoC?

An end-to-end physical design flow for SoC includes floorplanning, placement, clock tree synthesis, routing, timing optimization, power optimization, area optimization, and final sign-off to generate GDS-II.

Why does my physical design flow stop before reaching timing and power closure?

Your physical design flow may stop before closure if it lacks integrated timing optimization, power optimization, and area optimization stages, which are required to resolve violations and finalize the GDS-II output.