start-board-implementation

Initiate new board/ROM bring-up in the CERF emulator with identity confirmation and readiness assessment.

76|6|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/gweslab/cerf --skill start-board-implementation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start-board-implementation
Source: https://github.com/gweslab/cerf/tree/main/.claude/skills/start-board-implementation
Command: npx skills add https://github.com/gweslab/cerf --skill start-board-implementation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill initiates the process of bringing up a new board/ROM in the CERF emulator, ensuring accurate identification, verification, and readiness for implementation.

Core Features & Use Cases

  • Board Identification: Confirms the identity of the board/ROM by analyzing its bytes and cross-referencing with available information.
  • Readiness Assessment: Evaluates the readiness of the board for implementation, considering factors like existing support, SoC/CPU family, and manifest status.
  • Cross-Session Tracking: Seeds a tracking document for cross-session work on the board bring-up, guiding the user through the process.

Quick Start

Start the board implementation process by typing /start-board-implementation.

Frequently Asked Questions about start-board-implementation

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

FAQPage Schema
How do I start bringing up a new board in an emulator?

To start board bring-up, use the command to initiate the process, which confirms the board identity by analyzing its bytes and evaluates its readiness for implementation.

What is board bring-up in software emulation?

Board bring-up is the process of identifying a new ROM's bytes, verifying its SoC/CPU family, and assessing its manifest status to prepare it for implementation in an emulator.

Can I track emulator board implementation progress across multiple sessions?

Yes, cross-session tracking is supported by seeding a tracking document that guides you through the board bring-up process and maintains progress across multiple work sessions.

How does an emulator verify a new ROM's readiness for implementation?

Readiness assessment evaluates implementation viability by checking existing support, identifying the SoC/CPU family, and reviewing the manifest status of the board or ROM.

Do I need a manifest to begin the board bring-up process?

A manifest is evaluated during the readiness assessment to determine implementation readiness, but the process begins by analyzing the board's bytes to confirm its identity first.