メニュー
Build a block-level functional coverage plan from objectives and RTL surface information. Use this skill whenever the user wants deterministic coverpoints, crosses, and exclusions tied back to explicit verification objectives.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Extract a source-grounded, AI-readable textual design view from HDL source, parser output, MCP tool output, or model reasoning. Use this skill when the user needs Verilog, SystemVerilog, VHDL, or proprietary hardware description language normalized into a reusable design view for downstream analysis flows such as timing, lint, CDC, RDC, formal planning, or DV planning. Prefer UHDM text for SystemVerilog/Verilog when available, AST JSON when UHDM is not available, and explicit model-derived views only when no tool evidence exists.
Analyze an HDL design view or visible RTL for pre-synthesis timing risk by estimating combinational logic depth on register-to-register and boundary timing paths. Use this skill when the user already has a UHDM text dump, AST JSON, source-grounded textual design view, or small visible RTL block and asks for critical paths, deep combinational logic, reg-to-reg timing risk, or pre-synthesis timing feedback. This skill is analysis-only; use an HDL-design-view extraction skill or flow when parser/tool/MCP selection, source-language normalization, or design-view generation is required.
Read an approved microarchitecture specification and emit synthesizable SystemVerilog with requirement traceability. Use this skill whenever the flow moves from block architecture into concrete RTL implementation.
Review synthesizable SystemVerilog for static RTL issues such as inferred latches, reset mismatches, width hazards, and multi-driver structure. Use this skill whenever generated RTL needs a deterministic front-end lint audit before CDC, RDC, or timing review.
Normalize a block-level design brief into deterministic requirements, explicit PPA targets, and open intake questions. Use this skill whenever the user provides high-level microarchitectural intent and the workflow must capture power, performance, and area before specification or RTL work begins.
Assemble normalized requirements, the microarchitecture spec, generated RTL, and static audit summaries into one front-end handoff package. Use this skill whenever the block-level RTL planning flow needs one deterministic output that can feed downstream DV planning.
| name | functional-coverage-planner |
| description | Build a block-level functional coverage plan from objectives and RTL surface information. Use this skill whenever the user wants deterministic coverpoints, crosses, and exclusions tied back to explicit verification objectives. |
Plan block-level functional coverage tied to explicit DV objectives.
Scope: block or small IP. This is a planning skill, not coverage code generation.
Apply these repo rules before analysis and output generation:
../../rules/common/evidence-grounding.md../../rules/common/output-discipline.md../../rules/dv/objective-traceability.md../../rules/dv/coverage-taxonomy.mdRead the DV objectives and RTL verification surface, then perform these steps:
Produce a single YAML document:
design:
top_module: missing_intent_block
coverpoints:
- id: COV-001
objective_ids:
- OBJ-001
target: enable
kind: configuration
description: "Cover enable transitions seen at the block input."
crosses:
- id: COV-002
objective_ids:
- OBJ-002
targets:
- enable
- busy
description: "Cross enable programming with observed busy behavior."
exclusions:
- id: COV-003
objective_ids:
- OBJ-002
related_targets:
- enable
- busy
rationale: "Do not require latency-specific bins because the design intent does not define response timing."
summary:
total_coverpoints: 2
total_crosses: 1
total_exclusions: 1