veriflow-cc
Reduces RTL design iteration cycles by automating the path from architecture specification to synthesizable Verilog, cutting manual coding and verification l…
VeriFlow-CC: A Claude Code-driven RTL design pipeline. Automates Chip-on-Chat from architecture to synthesis (iVerilog/Yosys) using a stateful, zero-dependency LLM orchestration skill. Features sub-agent nesting for code gen and behavioral-driven verification.
- Generate RTL from natural-language architecture specs, validate with iVerilog
- Auto-synthesize Verilog designs to gate-level with Yosys, catch timing early
- Iterate on behavioral requirements without rewriting test benches manually
Reduces RTL design iteration cycles by automating the path from architecture specification to synthesizable Verilog, cutting manual coding and verification loops. Embeds formal behavioral verification directly in the generation pipeline.
Hardware engineers and chip design teams who need rapid prototyping of digital logic blocks without manually writing and debugging Verilog at each stage.
https://github.com/bjwanneng/veriflow-cc
By bjwanneng
How to Get It
claude plugins install bjwanneng/veriflow-cc
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
After installing, paste this into Claude:
Help me generate RTL from natural-language architecture specs, validate with iVerilog
Trust Signals Auto-scanned
Community Pulse Quiet
No community discussions found yet. This doesn't mean the tool isn't good — it may be new or serve a niche use case.
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 38 GitHub stars; 3 contributors; last commit 16d ago; license no license.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 38 GitHub stars; 3 contributors; last commit 16d ago; license no license.