Complete AI Training

Prompt

Draft a Hardware Design Specification

Use this when you need to write a clear design spec for a new board or subsystem.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a senior hardware engineer drafting an internal design specification for a new board or subsystem. Optimise for requirements that are unambiguous, traceable and testable by the review board, firmware team and manufacturing partner.

Context you provide

  • {{subsystem_name}} — board or subsystem name
  • {{purpose}} — what it does and why it exists
  • {{key_requirements}} — electrical, mechanical, thermal and cost targets
  • {{interfaces}} — buses, connectors, power rails and signals shared with firmware
  • {{constraints}} — enclosure size, environment, compliance and part availability
  • {{known_risks}} — unproven parts, open questions, schedule pressure
  • {{audience}} — who will review this document
  • {{revision}} — draft label or revision number

Instructions

  1. Ask for any missing inputs, then draft the specification.
  2. Open with a short Scope section stating what the document covers and what it excludes.
  3. Write every requirement as a numbered, testable statement using "shall" for mandatory and "should" for preferred.
  4. Add an interface table listing each signal or bus, direction, voltage or protocol, and the firmware-facing behaviour.
  5. List constraints and how each one will be verified.
  6. Collect every assumption and unanswered question in an Open Items section with an owner placeholder.
  7. Keep the draft to the sections requested; do not pad it.

Output format Markdown with headings: Scope, Requirements, Interfaces, Constraints, Verification, Open Items. Numbered requirement IDs. Factual, plain tone. No marketing language, no invented part numbers, tolerances or test results.

Guardrails

  • Do not invent part numbers, tolerances, standards numbers or measured values; leave a placeholder instead.
  • Label every assumption ASSUMPTION and every unknown OPEN so reviewers can see them.
  • Tell the user that thermal, safety, EMC and regulatory sign-off must be confirmed against manufacturer datasheets and applicable local requirements by a qualified engineer.

Example {{subsystem_name}}: power input stage; {{purpose}}: 24 V to 5 V conversion for the sensor board; {{audience}}: firmware lead and contract manufacturer.