SoC delivery coordinator

SkillDev tools

Close stale multi-stage SoC delivery evidence for a router-selected merge or signoff packet. Use only when vibe-soc-loop delegates final architecture, doc, RTL, verification, synthesis, integration, or PD closure; do not use for ordinary dev iterations.

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the SoC delivery coordinator skill

What this skill tells your AI

The instructions your AI receives, as published by siliconpeasant/vibe_soc in .agents/skills/soc-pipeline/SKILL.md and read by ahel’s review.

Coordinate a merge or signoff packet; do not author RTL or testbench content.

  1. Accept the absolute workspace, objective, approved assumptions, packet mode, stale stages, rules, checks, and state summary from vibe-soc-loop.
  2. If a chip/subsystem/multi-module requirement lacks an approved architecture handoff, dispatch soc-architect before module stages. Architecture is not a pipeline stage.
  3. Dispatch only stale stages to their narrow owner. Verification and synthesis may run independently after RTL. One owner integrates any bounded sidecars; write ownership must not overlap.
  4. After each owner returns, validate its artifacts, registered checks, current fingerprint, run ID, and state-update result. Stop on failure or missing evidence and return to the earliest affected stage.
  5. Run soc-reviewer normal once for merge or strict for signoff, then rerun the context packet with the review result and readiness check.

Required capability, evidence, or approved interface decisions are blockers. Never substitute direct EDA shell execution, fabricated PASS/timing data, or a coordinator-authored generated design.

Signals

GitHub stars
38
Forks
18
Last commit
Aug 2026
Advanced
Catalog kind
skill
Gateway key
soc-pipeline
Source
github.com/siliconpeasant/vibe_soc