Menu
Parse natural language hardware descriptions into structured JSON specifications, writing the result to workspace/<ModuleName>/spec.json.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Run full Chipyard-to-ORFS PnR flow for large designs (SmallBOOM etc.) using All-Mock memory blackboxing in Docker: generate RTL, preprocess nosram, run multi-round ORFS synth->finish with mock SRAMs to avoid OOM.
Docker Chipyard flow: generate RTL from a Chipyard config via Docker, run SRAM mapping, stage artifacts into MyDesign, and hand off to PnR.
Run full Chipyard-to-ORFS PnR flow with multi-round parameter iteration in Docker: generate RTL from Chipyard Docker, preprocess nosram+SRAM override, run 3 rounds of ORFS synth→finish on sky130hd with progressive clock/utilization/density tuning for optimal PPA.
Run full Chipyard-to-ORFS PnR flow with multi-round parameter iteration: generate RTL from Chipyard with ENABLE_YOSYS_FLOW, preprocess nosram+SRAM override, run 3 rounds of ORFS synth→finish on sky130hd with progressive clock/utilization/density tuning for optimal PPA.
Unified Chipyard PnR flow: automatically routes to local or Docker workflow based on backend_mode setting.
Unified Chipyard flow: automatically routes to local or Docker workflow based on backend_mode setting.
| name | requirement-parser |
| description | Parse natural language hardware descriptions into structured JSON specifications, writing the result to workspace/<ModuleName>/spec.json. |
| disable-model-invocation | true |
| allowed-tools | ["Read","Write","Bash","Grep","Glob"] |
Parse a natural language hardware description into a structured JSON specification file.
/chip-agent:requirement-parser <hardware description>
Extract the hardware description from $ARGUMENTS. If $ARGUMENTS is empty or blank, ask the user: "Please describe the hardware module you want to create. For example: 'A 32-bit ALU supporting ADD, SUB, AND, OR, XOR, and SLT operations with a zero flag output.'"
Determine the project root directory by finding the nearest ancestor directory of this skill file that contains .claude. Use that directory as the base for all relative paths below.
Read the requirement-parser agent definition at agents/requirement-parser.md (relative to the project root). This agent contains the full parsing rules, schema definitions, and examples for both simple and complex hardware designs.
Follow the agent's instructions to parse $ARGUMENTS into a structured JSON specification. The agent returns ONLY the raw JSON -- no markdown fences, no explanation. Apply all parsing rules from the agent definition including:
io.<portName> prefix.asSIntValidate the JSON output before writing to disk:
moduleName is present and PascalCase (first character uppercase, alphanumeric only)type is "simple" or "complex"direction (input/output), type (UInt/SInt/Bool), and width (integer)ports array is non-empty with at least one input and one outputtopModule.submodules matches a name in modules[]Create the workspace directory structure using Bash:
mkdir -p workspace/<moduleName>/generated workspace/<moduleName>/sim/logs
Write the JSON spec to disk using the Write tool. Write to:
workspace/<moduleName>/spec.json
This step is CRITICAL. The requirement-parser agent returns JSON to conversation output only -- it does NOT write files itself. This skill MUST capture the JSON and write it to disk so that downstream skills (testbench, compile, etc.) can read it.
Present a summary to the user:
workspace/<moduleName>/spec.json/chip-agent:testbench <ModuleName> to generate a testbench, or /chip-agent:compile <ModuleName> to compile to Verilog."$ARGUMENTS -- A natural language description of a hardware module (e.g., "A 32-bit ALU with ADD, SUB, AND, OR operations").
workspace/<ModuleName>/spec.json containing the structured JSON specification. The workspace directory tree is also created with generated/ and sim/logs/ subdirectories.