From requirements to reviewable results.

Define user, use case, target hardware, deliverables and exclusions.

Acceptance: Approved brief names a demonstrable outcome and acceptance owner.

Specify behavior, interfaces, throughput, latency, memory and power budgets.

Acceptance: Unique IDs, units, tolerance, source and verification method; TBDs assigned owners.

Map every requirement to tests, analysis or inspection.

Acceptance: No orphan requirement; acceptance rules documented before execution.

Inventory boards, tools, instruments, IP licences and lead times.

Acceptance: Approved budget; tool and IP availability verified.

Assign design, verification, quality, security and customer roles.

Acceptance: Reviewers, escalation and change-impact workflow approved.

Document datapaths, state machines, clocks, resets, buses and register maps.

Acceptance: Interface contracts and reset behavior reviewed by both design and verification owners.

Pin source, dependencies, constraints, test data and build scripts.

Acceptance: Clean checkout reproduces the build with recorded versions and hashes.

Build an independent behavioral oracle for expected outputs and error responses.

Acceptance: Normal, boundary and invalid-input examples agree with the written specification.

Configure lint, compiler warnings and coding review rules.

Acceptance: No unresolved high-severity finding; waivers have rationale and owners.

Archive deterministic test results, logs and seeds.

Acceptance: Failed checks block promotion; a retained seed reproduces a failure.

Test arithmetic, registers, control logic, reset and parameters.

Acceptance: Expected-value checks cover documented boundaries and configurations.

Exercise legal/malformed sequences, stalls, retries and arbitration.

Acceptance: No loss, duplication or unbounded stall within documented assumptions.

Define invariants, progress properties and formal assumptions.

Acceptance: Bounds, counterexamples and gaps reviewed; bounded proof is labeled accurately.

Track requirements, functional scenarios and supported code coverage.

Acceptance: Approved goals met or exclusions signed; coverage alone is not correctness.

Review crossings, synchronization intent and reset release.

Acceptance: Every crossing has handling and review evidence; simulation alone is not CDC signoff.

Inspect inferred logic, warnings and target utilization.

Acceptance: No unexplained critical warning; resource use fits the approved budget.

Review clocks, delays, exceptions, setup/hold and unconstrained paths.

Acceptance: Required paths constrained and timing meets the approved target and corners.

Cross-check package pins, bank voltages and board interfaces with vendor data.

Acceptance: Peer-reviewed constraints match the actual board revision.

Compare known-input/output captures with reference results.

Acceptance: Board serial, bitstream hash and instrument settings retained; discrepancies resolved.

Measure latency, throughput, restart and error recovery.

Acceptance: Measured results meet requirements; repeatability and limitations recorded.

Verify assembly revision, BOM, power compatibility and vendor bring-up guidance.

Acceptance: Inspection checklist and authorized bench setup approved.

Test GPIO, UART, SPI, I2C and selected devices or fixtures.

Acceptance: Transactions, invalid responses, timeouts and recovery meet interface contracts.

Exercise logic, state transitions, buffer boundaries and concurrency.

Acceptance: Repeatable host and target tests mapped to requirements and versioned builds.

Review access control, secret storage, update authenticity and recovery.

Acceptance: Negative tests reject unauthorized operations; recovery verified on an approved target.

Measure memory, scheduling, power and long-run behavior.

Acceptance: Project-specific budgets and duration met; resets and data-loss anomalies dispositioned.

Review ERC, DRC, stackup, return paths, interfaces and footprints.

Acceptance: Violations resolved or signed; supplier fabrication constraints confirmed.

Prepare BOM, fabrication, assembly, sourcing and traceability records.

Acceptance: Independent review checks file revisions, pin mapping, alternates and supplier needs.

Use a licensed flow with recorded PDK, libraries and constraints.

Acceptance: Reports retain provenance; educational PDK results labeled as studies.

Plan equivalence, corners, DRC/LVS, power integrity and DFT as applicable.

Acceptance: Specialists approve required checks; no tapeout claim without foundry signoff evidence.

Review uncertainty, costs, supply risk and test access before ordering.

Acceptance: Written release gate with accepted risks, frozen revision and inspection plan.

Integrate firmware, FPGA, host tools and interfaces.

Acceptance: Every accepted requirement traces to current evidence or an approved disposition.

Exercise approved disconnects, invalid data, restart and resource exhaustion.

Acceptance: Recovery meets requirements without undocumented data loss.

Record calibration, method, repetitions, uncertainty and raw data.

Acceptance: Conclusions stay within instrument capability and test applicability.

Prepare manifest, installation, backup and rollback instructions.

Acceptance: Independent install and restore reproduce the accepted configuration.

Deliver source/licences, reports, operating notes and known issues.

Acceptance: Customer accepts scope; limitations and future work remain visible.

Define audit, sprint, verification study and team-lab deliverables.

Acceptance: Written price, stages, exclusions and support terms reviewed.

Link commissioned scope, orders and delivery acceptance.

Acceptance: Payments use verified provider records; completion needs acceptance evidence.

Define severity, response targets, ownership and patch cadence.

Acceptance: Sample issue traces through acknowledgement, resolution and retest.

Identify market, product category and applicable safety/EMC/privacy obligations.

Acceptance: Qualified reviewers approve obligations; this template is not certification.

Review defects, schedule, costs and customer feedback.

Acceptance: Next-quarter studies have owners, test goals, scope and provisional deadlines.

Plan RTL, FPGA, firmware, PCB and verification explainers for four channels.

Acceptance: Audience, sources, owner, review date and channel targets assigned.

Link claims to sources and identify simulated versus bench results.

Acceptance: Technical review checks claims, demonstrations and licences.

Produce readable visuals, captions, thumbnails and commissioned narration.

Acceptance: Rendered video passes factual, visual, caption and rights review.

Connect YouTube and record LinkedIn, Instagram and Facebook ownership.

Acceptance: Publishing access verified; measured engagement tied to platform reports.

Track project enquiries, sponsorships and educational products.

Acceptance: Disclosures and offers approved; measured conversion informs future topics.