full-flow-demo

Orchestrate the Xilinx FPGA build flow from RTL simulation to bitstream generation.

11|7|Updated Jun 5, 2026
One-click install
npx skills add https://github.com/LNC0831/oh-my-fpga --skill full-flow-demo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: full-flow-demo
Source: https://github.com/LNC0831/oh-my-fpga/tree/main/skills/full-flow-demo
Command: npx skills add https://github.com/LNC0831/oh-my-fpga --skill full-flow-demo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of fragmented FPGA development by providing a structured, gated orchestration layer that ensures every stage of the build process—from RTL to bitstream—is verified before proceeding.

Core Features & Use Cases

  • Stage-by-Stage Gating: Enforces strict verification gates (syntax, simulation, CDC, synthesis, implementation, and signoff) to prevent silent regressions.
  • Automated Signoff: Validates timing (setup/hold), routing, DRC, and methodology on the implemented design before allowing bitstream generation.
  • Use Case: Use this when you need to take a complex design from source files to a production-ready bitstream, ensuring that every step is proven by tool reports rather than blind execution.

Quick Start

Invoke the full-flow-demo skill to run the complete build sequence from RTL to bitstream for the current project.

Frequently Asked Questions about full-flow-demo

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

FAQPage Schema
How do I automate the complete FPGA build flow from RTL to bitstream?

To automate the complete FPGA build flow, you can use an orchestration skill that sequences RTL simulation, synthesis, implementation, and bitstream generation. This enforces stage-by-stage verification gates to prevent silent regressions before generating the final bitstream.

What is stage-by-stage gating in Xilinx FPGA implementation?

Stage-by-stage gating is a verification mechanism that enforces strict checks across syntax, simulation, CDC, synthesis, and implementation phases. It ensures every stage of the FPGA build process is proven by tool reports before proceeding to the next step.

How do I ensure timing closure and DRC compliance before bitstream generation?

To ensure timing closure and DRC compliance, you need automated signoff validation on the implemented design. This process checks setup and hold timing, routing, and methodology reports, blocking bitstream generation until all metrics pass.

Do I need a Vivado Tcl server to run automated FPGA synthesis and implementation?

Yes, you need an active SynthPilot MCP connection to a Vivado Tcl server. This connection is required to execute tool commands, sequence the build flow, and validate design metrics during synthesis and implementation.

What's the best way to prevent silent regressions during FPGA timing closure?

The best way to prevent silent regressions is to use a gated orchestration layer for your FPGA build. By validating design metrics and enforcing rigorous stage-by-stage verification, the flow halts if timing closure or DRC compliance fails.

Can full-flow-demo handle complex FPGA designs requiring production-ready bitstreams?

Yes, full-flow-demo is designed to take complex designs from source files to a production-ready bitstream. It ensures every build step is verified through automated signoff, validating timing, routing, and DRC compliance before completion.