analog-spec-extract

Extract analog block specifications from L1 and L5 design documents into machine-readable spec.json files.

26|8|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/vibeic/vibe-ic --skill analog-spec-extract-vibeic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analog-spec-extract
Source: https://github.com/vibeic/vibe-ic/tree/main/vibe-ic-marketplace/plugins/vibe-ic/skills/analog-spec-extract
Command: npx skills add https://github.com/vibeic/vibe-ic --skill analog-spec-extract-vibeic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Analog IC design starts with scattered requirements buried in datasheet prose and interface documents, making it easy to miss blocks that need transistor-level design. This Skill systematically enumerates every analog block from L1/L5 design documents and converts them into structured, machine-readable specifications. ## Core Features & Use Cases - Deterministic block detection: Runs an 8-class keyword scan (oscillator, LDO, bandgap, POR, pull, ESD, charge pump, trim) over design documents so no analog block is silently skipped. - Taxonomy-based classification: Classifies each block into 12 types (LDO, Bandgap, Oscillator, POR, Comparator, ADC, DAC, PLL, Charge pump, OTA, Bias, Level shifter) with a deterministic name-to-type checker. - Structured spec output: Produces per-block spec.json files with supply ranges, numeric specs, interface signals, and constraints, plus a master analog_block_list.json. - Use Case: After Phase 1 generates L1_DATASHEET.json and L5_ADI_SPEC.json for a new chip, run this Skill to get a complete, gated list of analog blocks ready for topology selection in Step A2. ## Quick Start Extract the analog block specifications from the generated L1 and L5 design documents and write the spec.json files for each block.

Frequently Asked Questions about analog-spec-extract

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract analog block specs from IC design documents?▼

Run this Skill after Phase 1 produces L1_DATASHEET.json and L5_ADI_SPEC.json. It parses pin types, electrical characteristics, and analog-digital interface signals, then writes a spec.json per block plus a master analog_block_list.json.

What analog block types does the extraction taxonomy support?▼

The taxonomy covers 12 types: LDO, Bandgap, Oscillator, POR, Comparator, ADC, DAC, PLL, Charge pump, OTA/OpAmp, Bias, and Level shifter. A deterministic program classifies each block by name and fails if the declared type contradicts the lookup.

Can the analog block list be empty if the chip looks digital?▼

No. A hard rule forbids silently emitting an empty block list. An 8-class keyword scan over the input documents acts as a recall floor, and any detected class must produce at least one analog_blocks entry with evidence and implementation status.

Why does analog spec extraction flag spurious blocks?▼

The keyword scan over-fires when a product-name keyword matches a class without any bound spec. Such candidates must be confirmed against the L5 type enumeration before topology selection spends sizing compute, and dropped if L5 does not enumerate that class.

What inputs are required before running analog spec extraction?▼

You need generated_docs/L1_DATASHEET.json containing pin definitions and electrical characteristics, and generated_docs/L5_ADI_SPEC.json containing analog-digital interface signals, protection, and trim outputs. Both are produced by the earlier documentation phase.