ppa-distill

Converts a recovered PPA fix into an evidence-bound case record and draft deterministic rule.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an engineer recovers a PPA result through judgement that the deterministic flow could not reach, that lesson is usually lost or, worse, written down as an over-broad rule that later misfires on unrelated designs. This Skill captures the recovery as a structured case record with evidence hashes, a design fingerprint bounding reuse, counter-examples, and a draft of the deterministic rule it should eventually become. ## Core Features & Use Cases - Structured case capture: Records what failed in metric terms, what the deterministic path did, what judgement changed, and before/after measurements at matched scope. - Design fingerprinting: Binds each case to PDK, clock domains, macros, utilization, hierarchy depth, and flow version so reuse is bounded and benchmark integrity is preserved. - Rule drafting with promotion criteria: Drafts the case as an executable rule (input, condition, action, refutation) with countable promotion criteria, while the actual RAW-to-PROGRAMMED lifecycle stays owned by the deterministic distillation program. - Use Case: After buffering a high-fanout enable net recovers setup WNS on a gf180mcuD design, use this Skill to record the case with artefact hashes, counter-examples, and a draft buffering rule for later promotion. ## Quick Start Ask the assistant to distill the PPA recovery we just completed into a case record with evidence and a draft rule.

Frequently Asked Questions about ppa-distill

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

FAQPage Schema
How do I capture a PPA fix as a reusable case?▼

Record what failed in metric terms, what the deterministic path did, what judgement changed, and the before/after measurements at matched scope. Bind the case to artefact sha256 hashes and a design fingerprint covering PDK, clock domains, macros, utilization, and flow version.

What is a design fingerprint in PPA case distillation?▼

A design fingerprint lists the attributes that might explain why a fix worked, such as PDK, clock domain count, macro count, utilization, hierarchy depth, and flow version. It bounds where the case may be reused and prevents a rule from firing on designs it was never validated for.

Can this skill promote a case to a programmed rule?▼

No. The skill only drafts the rule and records the lifecycle rung; promotion from RAW to PROGRAMMED is owned by the deterministic _ppa/distillation.py program. A case is promoted only when its countable promotion criteria, such as reproduction on three differing designs, are met.

Why must counter-examples be recorded in a PPA case?▼

Counter-examples document designs where the fix was tried and did not help, which is the evidence that prevents an over-broad rule from being promoted. Omitting them removes the only check against a rule firing where it was never true.

What happens if the compliance check fails on the case record?▼

The skill_compliance_check.py script exits 1 and lists the missing elements, such as a Summary section, evidence hash, lifecycle state, or promotion criteria. The task is not complete until the audit returns exit 0 (PASS).