pnr

Automate the ORFS place-and-route flow for sky130hd designs with PPA reporting.

2|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/xsw632/ChipAgent --skill pnr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pnr
Source: https://github.com/xsw632/ChipAgent/tree/main/skills/pnr
Command: npx skills add https://github.com/xsw632/ChipAgent --skill pnr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the tedious, error-prone manual work of running physical implementation for digital designs on the sky130hd open-source PDK, automating the full ORFS place-and-route flow, report generation, and quality-of-results comparison that would otherwise require manual command execution and artifact parsing.

Core Features & Use Cases

  • Full PnR Automation: Runs the complete ORFS make flow for sky130hd designs, covering synthesis, place-and-route, and GDS export without manual intervention.
  • PPA Reporting: Generates comprehensive power, performance, and area reports with timing, area, power, and DRC violation metrics.
  • QoR Comparison: Supports multi-round parameter tuning with automatic retries and side-by-side comparison of results to identify the optimal configuration.
  • Use Case: For example, if you have a compiled Verilog design for an 8-bit ALU, use this Skill to automatically run the physical implementation flow, test different timing and utilization constraints, and get a verified GDS file plus a formatted performance report.

Quick Start

Use the pnr skill to run the full physical implementation flow for your compiled 8-bit ALU module and generate the GDS file along with timing, power, and area reports.

Frequently Asked Questions about pnr

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

FAQPage Schema
How do I automate place-and-route for sky130hd designs?

Automating place-and-route for sky130hd designs involves running the full OpenROAD-flow-scripts make flow. This process handles synthesis, PnR, and GDS export automatically without manual command intervention.

What is the best way to generate PPA reports from post-synthesis Verilog?

Generating PPA reports from post-synthesis Verilog is done by running an automated physical implementation flow. The process produces comprehensive timing, power, area, and DRC violation metrics directly from the input design.

Can I use OpenROAD-flow-scripts for multi-round quality-of-results comparison?

Yes, you can use OpenROAD-flow-scripts for multi-round quality-of-results comparison. The automated flow supports parameter tuning with automatic retries and generates side-by-side QoR comparison tables to identify optimal configurations.

Does the ORFS make flow support automatic parameter tuning for timing closure?

The ORFS make flow supports automatic parameter tuning for timing closure. It applies multi-round retries to test different timing and utilization constraints, helping achieve production-ready GDS files and optimal QoR.

How do I export a GDS file from a compiled Verilog module using sky130hd?

To export a GDS file from a compiled Verilog module using sky130hd, run the automated physical implementation workflow. The flow processes the post-synthesis design and outputs a verified, production-ready GDS file.

What are the limitations of automating physical design with OpenROAD-flow-scripts?

A limitation of automating physical design with OpenROAD-flow-scripts is that it specifically targets the sky130hd process design kit. Designs must be provided as post-synthesis Verilog to successfully execute the place-and-route and PPA reporting workflow.