ワンクリックでManusで任意のスキルを実行

block-requirements-normalizer

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.

Manusで実行

概要

インストールコマンド

npx skills add https://github.com/asicdesign-ai/asic-ai-workflows --skill block-requirements-normalizer

このコマンドをClaude Codeにコピー＆ペーストしてスキルをインストール

ソース

asicdesign-ai/asic-ai-workflows

スター3

フォーク2

更新日2026年4月8日 06:34

SKILL.md

readonly

name	block-requirements-normalizer
description	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.

Block Requirements Normalizer Skill

Convert a user brief into one structured requirement set for a block-level RTL planning flow.

Scope: block or small IP. This is an intake and normalization skill, not a microarchitecture or RTL generator.

Rules

Apply these repo rules before analysis and output generation:

../../rules/common/evidence-grounding.md
../../rules/common/output-discipline.md
../../rules/arch/requirements-traceability.md
../../rules/arch/ppa-capture.md

Analysis

Read the user brief and any optional RTL context, then perform these steps:

Extract atomic block requirements and assign stable REQ-NNN IDs.
Separate functional, interface, clock/reset, and PPA requirements.
Capture performance, power, and area independently as numeric, qualitative, or missing.
Emit blocking open questions whenever the intake does not support specification work, especially for missing PPA.
Keep descriptions short, factual, and grounded in the provided brief.

Output Format

Produce a single YAML document:

design:
  top_module: event_counter
  brief_summary: "Programmable event counter with optional interrupt threshold."

requirements:
  - id: REQ-001
    title: count qualified input events
    category: function
    priority: must
    source: user
    description: "The block increments a stored count when event_valid is asserted."
    acceptance_criteria: "With counting enabled, each qualified event increments count_value by one."

ppa_targets:
  performance:
    target: "600"
    units: "MHz"
    priority: "primary"
    status: numeric
  power:
    target: "minimize dynamic power"
    units: null
    priority: "secondary"
    status: qualitative
  area:
    target: null
    units: null
    priority: "secondary"
    status: missing

open_questions:
  - topic: area target
    question: "What area budget or utilization limit constrains the block?"
    blocking: true
    related_requirement_ids:
      - REQ-001

summary:
  total_requirements: 1
  total_open_questions: 1
  ppa_complete: false

Scope Limitations

Can do: normalize intent, capture explicit PPA status, and surface missing intake data.
Cannot do: derive a complete microarchitecture, choose undocumented protocols, or claim front-end closure.

このリポジトリの他の Skills

同じリポジトリ

hdl-design-view-extractor

asicdesign-ai/asic-ai-workflows

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.

2026-04-273

rtl-timing-analyzer

asicdesign-ai/asic-ai-workflows

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.

2026-04-273

rtl-designer

asicdesign-ai/asic-ai-workflows

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.

2026-04-263

rtl-lint-auditor

asicdesign-ai/asic-ai-workflows

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.

2026-04-263

block-rtl-package-assembler

asicdesign-ai/asic-ai-workflows

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.

2026-04-083

microarchitecture-spec-author

asicdesign-ai/asic-ai-workflows

Turn normalized block requirements into a Markdown microarchitecture specification with requirement traceability and targeted diagrams. Use this skill whenever the workflow needs a deterministic architecture document before RTL generation.

2026-04-083

ソース

asicdesign-ai

asicdesign-ai/asic-ai-workflows

GitHub リポジトリを開く Creator のリポジトリを見る

インストールコマンド

ダウンロード

Manusで実行

役立つ用途SOC

電子エンジニア（コンピュータ除く）建築・工学職17-2072L4

name	block-requirements-normalizer
description	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.

Block Requirements Normalizer Skill

Convert a user brief into one structured requirement set for a block-level RTL planning flow.

Scope: block or small IP. This is an intake and normalization skill, not a microarchitecture or RTL generator.

Rules

Apply these repo rules before analysis and output generation:

../../rules/common/evidence-grounding.md
../../rules/common/output-discipline.md
../../rules/arch/requirements-traceability.md
../../rules/arch/ppa-capture.md

Analysis

Read the user brief and any optional RTL context, then perform these steps:

Extract atomic block requirements and assign stable REQ-NNN IDs.
Separate functional, interface, clock/reset, and PPA requirements.
Capture performance, power, and area independently as numeric, qualitative, or missing.
Emit blocking open questions whenever the intake does not support specification work, especially for missing PPA.
Keep descriptions short, factual, and grounded in the provided brief.

Output Format

Produce a single YAML document:

design:
  top_module: event_counter
  brief_summary: "Programmable event counter with optional interrupt threshold."

requirements:
  - id: REQ-001
    title: count qualified input events
    category: function
    priority: must
    source: user
    description: "The block increments a stored count when event_valid is asserted."
    acceptance_criteria: "With counting enabled, each qualified event increments count_value by one."

ppa_targets:
  performance:
    target: "600"
    units: "MHz"
    priority: "primary"
    status: numeric
  power:
    target: "minimize dynamic power"
    units: null
    priority: "secondary"
    status: qualitative
  area:
    target: null
    units: null
    priority: "secondary"
    status: missing

open_questions:
  - topic: area target
    question: "What area budget or utilization limit constrains the block?"
    blocking: true
    related_requirement_ids:
      - REQ-001

summary:
  total_requirements: 1
  total_open_questions: 1
  ppa_complete: false

Scope Limitations

Can do: normalize intent, capture explicit PPA status, and surface missing intake data.
Cannot do: derive a complete microarchitecture, choose undocumented protocols, or claim front-end closure.