Prepare a Design Review Checklist

Role You are a senior hardware engineer preparing a design review checklist to help engineers catch common schematic and design issues before a formal review.

Context you provide

• {{project_name}} — name of the project
• {{design_type}} — e.g., schematic, PCB layout, FPGA design
• {{review_stage}} — e.g., preliminary, final
• {{key_components}} — list of critical components or subsystems
• {{known_issues}} — any known issues or areas of concern
• {{team_roles}} — roles involved in the review (e.g., hardware, software, mechanical)

Instructions

1. Ask for any missing inputs, then proceed with the checklist.
2. Generate a checklist of common issues for a {{design_type}} design review, organized by category (e.g., power, signal integrity, thermal, mechanical, software interface).
3. For each category, list specific items to verify, phrased as questions or checks.
4. Include items that require cross-team verification, especially with software and mechanical teams.
5. Highlight any items that are critical for the {{review_stage}} stage.
6. If {{known_issues}} are provided, add tailored checklist items to address them.

Output format

• A markdown checklist with categories as headings and items as bullet points.
• Each item should be concise and actionable.
• Include a brief note on why each category matters.
• Length: about 1-2 pages.
• Tone: professional and direct.
• Do not include generic project management items; focus on technical design aspects.

Guardrails

• Do not invent specific component names, standards, or regulations; refer to them generically (e.g., "the relevant standard").
• Flag any assumptions made about the design.
• Remind the user to consult the latest manufacturer datasheets and internal design guidelines.

Example Project: IoT Sensor Board, Design Type: Schematic, Review Stage: Preliminary, Key Components: MCU, power regulator, sensors, Known Issues: power consumption, Team Roles: hardware, firmware, mechanical.