Skip to content
cccskills
FreePublished on GitHub

manage-pcba-program

Coordinate an evidence-gated electronic product and PCBA workflow from an idea, circuit description, schematic, netlist, PCB, BOM, or fabrication package through a reviewed order. Use for end-to-end requests, multi-stage hardware projects, workflow recovery, gate tracking, change invalidation, or deciding which specialist skill is required next.

The English summary is being prepared. Showing the original description.

See how to install

Files included (7)

  • SKILL.md3.6 KB
  • agents/openai.yaml257 B
  • LICENSE1.0 KB
  • references/recorded-workflow.md3.9 KB
  • references/stage-gates.md3.0 KB
  • scripts/program_state.py10.2 KB
  • scripts/workflow_record.py13.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

PCBA Program Manager

Coordinate specialists; do not replace them. Default shared artifacts to .pcba-workflow/ and use only PASS, BLOCKED, or USER_REVIEW for gate status.

Start

  1. Read repository instructions and inventory available descriptions, native EDA sources, generators, netlists, renders, PCB files, BOM/CPL files, manufacturing packages, test evidence, and approvals.
  2. Read references/stage-gates.md.
  3. Identify which specialist skills are installed. If a required specialist is absent, report its exact name and stop that stage; never improvise its approval.
  4. Initialize or validate .pcba-workflow/program-state.json with scripts/program_state.py.
  5. When the user requests a timelapse, tutorial, case study, or recorded demo, read references/recorded-workflow.md and initialize the hash-chained event log before the first design action.

Route the work

  • Description or incomplete requirements: $plan-electronic-product.
  • BOM, MPN, stock, package, CAD, lifecycle, or substitution: $qualify-pcba-sourcing.
  • Electrical architecture, ratings, power, reset, timing, safe state, or circuit correctness: $design-and-review-circuit.
  • Label-heavy, visually floating, overlapping, or netlist-like schematic: $schematic-humanizer after capturing a connectivity baseline.
  • Placement, routing, layers, planes, DRC, SI/PI, RF, or DFM: $pcb-layout-review.
  • Gerber, drill, BOM, CPL, render, and revision-consistent release: $release-pcba-fabrication.
  • Live JLCPCB quote, matching, preview, price, cart, or order: $operate-jlcpcb-order.

Run the humanizer early when presentation blocks review, but never use its readability result as circuit approval. Require sourcing and circuit gates before placement freeze.

Manage evidence and change

  • Record every artifact path, revision, SHA-256, gate status, unresolved risk, and approval evidence in program state.
  • Invalidate downstream gates after controlled data changes. Use scripts/program_state.py invalidate --change ...; do not manually preserve a stale PASS.
  • Keep substitution, assembly-placement, final-price, and payment approvals separate. Approval at one gate never implies another.
  • Respect user intent: review-only requests do not authorize design edits, browser mutations, cart changes, or payments.
  • In recorded mode, append events only after saved, inspectable checkpoints. Keep promotion-safe frames separate from private evidence, record authentic failures and corrections without staging fake defects, and validate hashes after every stage. Let the recorder snapshot mutable inputs and outputs; never edit generated sequence-scoped checkpoint copies.
  • Stop on contradictory revisions, missing source-of-truth data, unverifiable safety assumptions, or a specialist BLOCKED result.

Finish

Report current gate, completed evidence, invalidated work, unresolved risks, required user reviews, and the next specialist. A program is complete only when the requested terminal gate is PASS and no required work remains. For a pre-order demo, finish at order_stop: USER_REVIEW, validate and close the recording, and do not cross its declared stop_before boundary.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Design, audit, or correct an electronic circuit from a product brief, native schematic, netlist, block diagram, or circuit description. Use for architecture and component-function review, power and logic-domain checks, reset and boot sequencing, bus ownership, ratings, timing, protection, safe states, component suitability, circuit bugs, or layout-facing electrical constraints.

The English summary is being prepared. Showing the original description.

Keitark/pcba-design-skills34Updated Sep 22, 2026

Operate and review a JLCPCB PCB/PCBA quote, optional physical-stencil request, or order using a frozen Gerber/drill, BOM, CPL, sourcing lock, constraints, and release manifest. Use for browser upload, board or stencil options, cost anomalies, coupons, component matching, substitutions, imported placement calibration, top/bottom preview inspection, cart preparation, or order records without silently accepting placement errors or payment.

The English summary is being prepared. Showing the original description.

Keitark/pcba-design-skills34Updated Sep 22, 2026

Audit, finish, or port PCB placement and routing using circuit intent, mechanical constraints, sourcing evidence, native DRC/connectivity, rendered views, and manufacturing feedback. Use before routing, after autorouting, before fabrication release, when adapting a proven board to another connector, enclosure, platform, or regional variant, or when reviewing layers, GND references, power distribution, decoupling, buses, controlled interfaces, RF keepouts, vias, cost-driving features, opens, or DRC findings.

The English summary is being prepared. Showing the original description.

Keitark/pcba-design-skills34Updated Sep 22, 2026

Turn an electronic product idea, behavior description, reverse-engineering note, or incomplete circuit concept into a decision-ready engineering brief and architecture. Use before schematic design or audit when functions, operating states, power, interfaces, mechanics, production quantity, cost, or measurable requirements are missing or ambiguous.

The English summary is being prepared. Showing the original description.

Keitark/pcba-design-skills34Updated Sep 22, 2026

Verify a PCBA BOM and proposed components before circuit or placement freeze, including exact manufacturer part numbers, pin semantics, packages, footprints, CAD and 3D models, lifecycle, live stock, MOQ, assembly class, price, and approved substitutes. Use for sourcing locks, unavailable or expensive parts, JLCPCB/LCSC matching, BOM risk, or cost-aware substitution decisions.

The English summary is being prepared. Showing the original description.

Keitark/pcba-design-skills34Updated Sep 22, 2026

Build and verify a vendor-neutral PCB/PCBA manufacturing release from one frozen design revision. Use when generating or auditing Gerber, drill, IPC-2581/ODB++, BOM, CPL/pick-and-place, assembly drawings, constraints, renders, DFM evidence, hashes, or release manifests, and when preventing mixed-revision fabrication or assembly uploads.

The English summary is being prepared. Showing the original description.

Keitark/pcba-design-skills34Updated Sep 22, 2026

See all skills by Keitark

Report a problem with this skill