veripower
Agent & Workflowchipweaver/veripower
An agent workflow plugin for chip front-end design that drives a coding agent from specification through Verilog RTL and UVM testbench work to signoff, tracking stage results and reruns.
- ai-agents
- chip-design
- claude-code
- claude-code-plugin
- dsh
- dsh-plugin
- hardware-verification
- opencode
- rtl-design
- systemverilog
- uvm
- verilog
Verification and compatibility
This section shows evidence collected by the catalog. Undeclared information is labeled as unknown.
- Current-version compatibility
- Verified on the catalog Harness version
- Declared Harness range
- Not declared
- Declared platforms
- Not declared
- Profiles
- web
- Build approval
- Unknown
- Permissions
- Not declared
- External services
- Not declared
- Telemetry
- Unknown
This is not a security endorsement. Review source, permissions, and configuration before installing.
View evidence and scope
Verification covers only the named source, version, and Harness environment. It does not guarantee future compatibility.
github:chipweaver/veripower#c8808816711be97337af787db9eb36c7a13f3fde- The manifest and static structure passed checks; a runtime load check has not completed.
README
VeriPower is an open-source plugin for chip front-end design and verification. Working from your specification, a coding agent develops RTL and a UVM testbench, runs EDA tools, and revises the design based on their results. VeriPower manages the work across stages, keeping track of what has passed and what needs to run again.
Works with Claude Code, opencode, DeepSeek Harness, and Codex.
How it works
Each stage has a skill containing instructions and supporting scripts. The agent follows the skill to carry out the work, while a workflow engine records the result and selects what should run next. When a check fails, the agent investigates the cause and the engine schedules the repair.
Each run records the versions of its input and output files. The engine compares these with the current files to determine which results still apply and which checks need to be repeated. An RTL edit requires simulation, lint/CDC, and synthesis to run again, while a testbench edit leaves lint/CDC results intact. The files and execution history are stored on disk, allowing work to resume in a new session.
The verification plan and reference model are based on the specification. Stage scripts verify that every planned test ran and passed, and check coverage, timing, and power against the specified targets. Independent model reviews examine whether the test stimulus and checking logic can detect incorrect behavior. Together, these checks and reviews determine whether a stage passes.
Before the flow completes, the engine checks that all required stages have passed and their results still apply. The generated RTL, testbench, constraints, and reports are available in the project directory.
More in the architecture guide (中文).
Design flow
The flow covers eight stages, from specification to power analysis. Simulation triage is a separate task that investigates simulation failures when the cause is unclear.
The included skills use Synopsys SpyGlass for lint and CDC, Design Compiler for synthesis, PrimeTime for timing and power analysis, and VCS with UVM for simulation.
Results
Three front-end design tasks, bare Claude Code vs. Claude Code + VeriPower. Same LLM, same spec, same EDA tools.
| Benchmark | Scale | Baseline | + VeriPower |
|---|---|---|---|
| gateGPT — fixed-point GPT inference | 346K gates | 3 of 4 coverage metrics below 90% | pass |
| FSA — FlashAttention accelerator | 32K gates | 2 unresolved CDC violations | pass |
| Coral-NPU — RISC-V ML accelerator | 3.4M gates | 6/19 tests | 19/19 |
Across these tasks, VeriPower closes verification gaps in coverage, CDC and test execution.
Quickstart
claude plugin marketplace add chipweaver/veripower
claude plugin install veripower@chipweaver
Or point at a working copy: claude --plugin-dir /path/to/veripower.
See Claude Code setup and runtime behavior.
Add the plugin to ~/.config/opencode/opencode.json, or to a project-level
opencode.json:
{ "plugin": ["veripower@git+https://github.com/chipweaver/veripower.git"] }
Stage dispatch runs subagents in the background, which opencode gates behind an environment variable, so start it with:
OPENCODE_EXPERIMENTAL_BACKGROUND_SUBAGENTS=true \
OPENCODE_EXPERIMENTAL_OUTPUT_TOKEN_MAX=131072 opencode
opencode 1.18.30 has a default 32,000-token completion ceiling. For models that support
longer output, set the second flag to the model's declared output limit; 131072 is
an example.
See opencode setup and runtime behavior.
Install into the profile you run:
dsh plugin --profile web add "veripower@git+https://github.com/chipweaver/veripower.git"
Run the web profile (dsh web), not the one-shot headless profile.
See DeepSeek Harness setup and runtime behavior.
Native plugin and subagents (tested with CLI 0.154.0 on Linux):
codex plugin marketplace add chipweaver/veripower
codex plugin add veripower@chipweaver --json
Launch with codex --enable hooks --enable multi_agent, review the two VeriPower hooks in
/hooks, and start a new session. The plugin uses native subagents and preserves the host's
permission configuration. See Codex setup and runtime behavior.
Ask it to list its skills — the twelve VeriPower ones confirm the install.
Run the brainstorm skill to settle requirements first, then tell the agent:
Run the design flow for {module_dir}
Full walkthrough in the user manual (中文).
Requirements. Python 3.10+, jsonschema >= 4.18, referencing, PyYAML. Synopsys EDA tools, swappable per skill.
Citation
Paper forthcoming.
Version: v0.2.5. MIT License. Contributing. Issues.