Prompts for Design and Product Engineering

15 ready-to-use ChatGPT prompts for design and product engineering. Fill in the bracketed fields, paste into ChatGPT, and go.

Engineering · 15 prompts

01

Create a 3D CAD Model Specification for a Mechanical Part

Create a 3D model plan with manufacturing-oriented design specifications for a mechanical part.

You’ll needpart purposemanufacturing methodtolerancesconstraints
Prompt
You are a senior design and product engineering architect creating a plan for a real engineering initiative.

Create a plan for the task below.

Context:
- Goal: [goal]
- Stack or environment: [stack]
- Current system or baseline: [current system]
- Constraints such as security, latency, budget, or staffing: [constraints]
- Scale, complexity, or production expectations: [scale]
- Risks, current issues, or dependencies: [risks]

Instructions:
1. Recommend a practical technical approach and explain why it fits the context.
2. Break the work into sensible phases, components, or rollout stages.
3. Explicitly address the failure modes that actually derail this kind of initiative: tolerances specified without considering the actual manufacturing process capability, such as a tolerance achievable in CNC but not in injection molding, draft angles or wall thickness left unspecified in a way that makes the part unmoldable or prone to warping, no material specified before dimensions are locked so a later material swap invalidates the whole tolerance stack, and assembly interfaces designed in isolation with no check against the mating part's actual as-built dimensions.
4. Include validation, rollback, migration, or monitoring considerations where relevant.
5. Keep the plan realistic for the stated context and avoid architecture theater.

Output format:
- Plan overview
- Recommended approach and tradeoffs
- Implementation phases or rollout path
- Risks, dependencies, and validation checks
- Main assumptions or open questions

Missing information policy:
Ask up to 2 concise questions only if the goal or environment is unclear. Otherwise proceed with assumptions.

Quality bar:
- Make the plan executable.
- Avoid overengineering.
- Name the specific failure modes above rather than generic risk language.
- Show how the plan would survive real deployment pressure.
02

Develop a Bridge Load Simulation Plan

Develop a simulation approach to test a bridge design under different load conditions.

You’ll needbridge typeload casessimulation toolconstraints
Prompt
You are a senior design and product engineering architect creating a plan for a real engineering initiative.

Create a plan for the task below.

Context:
- Goal: [goal]
- Stack or environment: [stack]
- Current system or baseline: [current system]
- Constraints such as security, latency, budget, or staffing: [constraints]
- Scale, complexity, or production expectations: [scale]
- Risks, current issues, or dependencies: [risks]

Instructions:
1. Recommend a practical technical approach and explain why it fits the context.
2. Break the work into sensible phases, components, or rollout stages.
3. Explicitly address the failure modes that actually derail this kind of initiative: load cases limited to static loads with no dynamic or fatigue loading considered, boundary conditions in the simulation that don't match the real support conditions on site, a safety factor applied uniformly instead of scaled to the actual consequence of failure for each component, and simulation results treated as final with no plan to validate against a physical load test or existing structure data.
4. Include validation, rollback, migration, or monitoring considerations where relevant.
5. Keep the plan realistic for the stated context and avoid architecture theater.

Output format:
- Plan overview
- Recommended approach and tradeoffs
- Implementation phases or rollout path
- Risks, dependencies, and validation checks
- Main assumptions or open questions

Missing information policy:
Ask up to 2 concise questions only if the goal or environment is unclear. Otherwise proceed with assumptions.

Quality bar:
- Make the plan executable.
- Avoid overengineering.
- Name the specific failure modes above rather than generic risk language.
- Show how the plan would survive real deployment pressure.
03

Write a Consumer Electronics Design Specification

Write a design specification document for a consumer electronic product.

You’ll needproduct typetechnical requirementsmaterialsconstraints
Prompt
You are a senior design and product engineering practitioner creating a reusable engineering asset for a real team workflow.

Build the asset using the context below.

Context:
- Goal of the asset: [goal]
- System or project context: [context]
- Audience using it: [audience]
- Constraints, standards, or compliance needs: [constraints]
- Quality risks, failure modes, or review focus: [risk focus]
- Stage of use such as design, implementation, release, or incident response: [stage]

Instructions:
1. Create an asset that is immediately usable in a real workflow.
2. Keep the structure concise and scannable, but include the checks that materially affect quality, safety, or operability.
3. Prioritize measurable, testable requirements over generic completeness: a spec written with vague requirements like 'should be durable' instead of measurable acceptance criteria that engineering and QA can actually test against, no distinction between must-have requirements and nice-to-have ones, causing scope creep during development, regulatory and certification requirements mentioned only in passing instead of specified with the actual standard and test method, and no version control on the spec itself, so different teams end up building against different versions.
4. Separate must-have requirements from nice-to-have ones explicitly.
5. Add short usage guidance when it improves consistency or judgment.
6. Make sure the asset helps a team catch real failure modes before they ship or escalate.

Output format:
- Specification document with measurable acceptance criteria
- Must-have vs nice-to-have separation
- Regulatory/certification requirements with standard and test method
- Version-control guidance

Missing information policy:
Ask up to 2 concise questions only if the goal, audience, or context is unclear. Otherwise proceed with assumptions.

Quality bar:
- Keep it practical.
- Make the structure reusable.
- Name the specific failure modes above rather than generic checklist bloat.
- Emphasize the checks that prevent real mistakes.
04

Design a Sustainable Product Concept

Design a product with sustainability goals using eco-friendly materials and efficient features.

You’ll needproduct categorysustainability goalsmaterials constraintsuser needs
Prompt
You are a senior design and product engineering architect creating a plan for a real engineering initiative.

Create a plan for the task below.

Context:
- Goal: [goal]
- Stack or environment: [stack]
- Current system or baseline: [current system]
- Constraints such as security, latency, budget, or staffing: [constraints]
- Scale, complexity, or production expectations: [scale]
- Risks, current issues, or dependencies: [risks]

Instructions:
1. Recommend a practical technical approach and explain why it fits the context.
2. Break the work into sensible phases, components, or rollout stages.
3. Explicitly address the failure modes that actually derail this kind of initiative: eco-friendly materials chosen based on a single attribute like recyclability without checking the full lifecycle impact including manufacturing energy and transport, sustainability goals that conflict with durability and produce a product that has to be replaced sooner, negating the environmental benefit, no end-of-life plan for how the product is actually disassembled or recycled in practice, and claims made in marketing that aren't actually verifiable against a real lifecycle assessment.
4. Include validation, rollback, migration, or monitoring considerations where relevant.
5. Keep the plan realistic for the stated context and avoid architecture theater.

Output format:
- Plan overview
- Recommended approach and tradeoffs
- Implementation phases or rollout path
- Risks, dependencies, and validation checks
- Main assumptions or open questions

Missing information policy:
Ask up to 2 concise questions only if the goal or environment is unclear. Otherwise proceed with assumptions.

Quality bar:
- Make the plan executable.
- Avoid overengineering.
- Name the specific failure modes above rather than generic risk language.
- Show how the plan would survive real deployment pressure.
05

Plan a Prototype for an Automotive Component

Create a detailed prototyping plan for a new automotive component.

You’ll needcomponent typematerialstesting needsconstraints
Prompt
You are a senior design and product engineering architect creating a plan for a real engineering initiative.

Create a plan for the task below.

Context:
- Goal: [goal]
- Stack or environment: [stack]
- Current system or baseline: [current system]
- Constraints such as security, latency, budget, or staffing: [constraints]
- Scale, complexity, or production expectations: [scale]
- Risks, current issues, or dependencies: [risks]

Instructions:
1. Recommend a practical technical approach and explain why it fits the context.
2. Break the work into sensible phases, components, or rollout stages.
3. Explicitly address the failure modes that actually derail this kind of initiative: a prototype built to a fidelity level that doesn't match what the current test phase actually needs, wasting budget on finish quality nobody is evaluating yet, safety-critical components tested with the same rigor as cosmetic ones instead of prioritized, no plan for how prototype learnings actually feed back into the next design iteration, and supplier lead times for prototype-specific parts not accounted for in the schedule.
4. Include validation, rollback, migration, or monitoring considerations where relevant.
5. Keep the plan realistic for the stated context and avoid architecture theater.

Output format:
- Plan overview
- Recommended approach and tradeoffs
- Implementation phases or rollout path
- Risks, dependencies, and validation checks
- Main assumptions or open questions

Missing information policy:
Ask up to 2 concise questions only if the goal or environment is unclear. Otherwise proceed with assumptions.

Quality bar:
- Make the plan executable.
- Avoid overengineering.
- Name the specific failure modes above rather than generic risk language.
- Show how the plan would survive real deployment pressure.
06

Design an Ergonomic Workstation Layout

Design an ergonomic workstation layout that reduces strain and improves productivity.

You’ll needwork typespace constraintsuser needsproductivity goals
Prompt
You are a senior design and product engineering architect creating a plan for a real engineering initiative.

Create a plan for the task below.

Context:
- Goal: [goal]
- Stack or environment: [stack]
- Current system or baseline: [current system]
- Constraints such as security, latency, budget, or staffing: [constraints]
- Scale, complexity, or production expectations: [scale]
- Risks, current issues, or dependencies: [risks]

Instructions:
1. Recommend a practical technical approach and explain why it fits the context.
2. Break the work into sensible phases, components, or rollout stages.
3. Explicitly address the failure modes that actually derail this kind of initiative: the layout designed around a single 'average' body size instead of the actual range of users who will use it, reach and sightline distances validated in a static drawing but never checked with a real person in the actual workspace, adjustability features added without checking whether users will actually know how or bother to use them, and no plan for how the layout accommodates equipment changes over time.
4. Include validation, rollback, migration, or monitoring considerations where relevant.
5. Keep the plan realistic for the stated context and avoid architecture theater.

Output format:
- Plan overview
- Recommended approach and tradeoffs
- Implementation phases or rollout path
- Risks, dependencies, and validation checks
- Main assumptions or open questions

Missing information policy:
Ask up to 2 concise questions only if the goal or environment is unclear. Otherwise proceed with assumptions.

Quality bar:
- Make the plan executable.
- Avoid overengineering.
- Name the specific failure modes above rather than generic risk language.
- Show how the plan would survive real deployment pressure.
07

Write a Feasibility Study for a Medical Device

Write a feasibility study for a new medical device including technical, regulatory, and market factors.

You’ll needdevice conceptregulatory contextmarket needconstraints
Prompt
You are a senior design and product engineering architect creating a plan for a real engineering initiative.

Create a plan for the task below.

Context:
- Goal: [goal]
- Stack or environment: [stack]
- Current system or baseline: [current system]
- Constraints such as security, latency, budget, or staffing: [constraints]
- Scale, complexity, or production expectations: [scale]
- Risks, current issues, or dependencies: [risks]

Instructions:
1. Recommend a practical technical approach and explain why it fits the context.
2. Break the work into sensible phases, components, or rollout stages.
3. Explicitly address the failure modes that actually derail this kind of initiative: a regulatory pathway assumed based on a similar past product without confirming it against this device's actual risk classification, technical feasibility assessed in isolation from the clinical evidence burden the regulatory pathway will actually require, market sizing based on total addressable population instead of the realistic reimbursement- and adoption-constrained segment, and no early input from the actual regulatory or clinical stakeholders who will determine if this ships.
4. Include validation, rollback, migration, or monitoring considerations where relevant.
5. Keep the plan realistic for the stated context and avoid architecture theater.

Output format:
- Plan overview
- Recommended approach and tradeoffs
- Implementation phases or rollout path
- Risks, dependencies, and validation checks
- Main assumptions or open questions

Missing information policy:
Ask up to 2 concise questions only if the goal or environment is unclear. Otherwise proceed with assumptions.

Quality bar:
- Make the plan executable.
- Avoid overengineering.
- Name the specific failure modes above rather than generic risk language.
- Show how the plan would survive real deployment pressure.
08

Create a Drone Aerodynamics Simulation Plan

Create a simulation model plan for testing a new drone's aerodynamic properties.

You’ll needdrone typeflight goalssimulation toolsconstraints
Prompt
You are a senior design and product engineering architect creating a plan for a real engineering initiative.

Create a plan for the task below.

Context:
- Goal: [goal]
- Stack or environment: [stack]
- Current system or baseline: [current system]
- Constraints such as security, latency, budget, or staffing: [constraints]
- Scale, complexity, or production expectations: [scale]
- Risks, current issues, or dependencies: [risks]

Instructions:
1. Recommend a practical technical approach and explain why it fits the context.
2. Break the work into sensible phases, components, or rollout stages.
3. Explicitly address the failure modes that actually derail this kind of initiative: simulation conditions that only cover steady, calm-air flight and skip gusting or maneuvering conditions where real failures happen, mesh resolution or turbulence model chosen for speed rather than accuracy where it actually matters, results validated only against theory with no plan to correlate against real flight test data, and payload or configuration changes not accounted for as a variable that shifts the aerodynamic behavior being modeled.
4. Include validation, rollback, migration, or monitoring considerations where relevant.
5. Keep the plan realistic for the stated context and avoid architecture theater.

Output format:
- Plan overview
- Recommended approach and tradeoffs
- Implementation phases or rollout path
- Risks, dependencies, and validation checks
- Main assumptions or open questions

Missing information policy:
Ask up to 2 concise questions only if the goal or environment is unclear. Otherwise proceed with assumptions.

Quality bar:
- Make the plan executable.
- Avoid overengineering.
- Name the specific failure modes above rather than generic risk language.
- Show how the plan would survive real deployment pressure.
09

Integrate Renewable Energy into a Building Design

Develop a process for integrating solar or wind into an existing building design.

You’ll needbuilding typeenergy goalssite constraintsconstraints
Prompt
You are a senior design and product engineering architect creating a plan for a real engineering initiative.

Create a plan for the task below.

Context:
- Goal: [goal]
- Stack or environment: [stack]
- Current system or baseline: [current system]
- Constraints such as security, latency, budget, or staffing: [constraints]
- Scale, complexity, or production expectations: [scale]
- Risks, current issues, or dependencies: [risks]

Instructions:
1. Recommend a practical technical approach and explain why it fits the context.
2. Break the work into sensible phases, components, or rollout stages.
3. Explicitly address the failure modes that actually derail this kind of initiative: solar or wind capacity sized against ideal conditions instead of the building's actual local weather and shading profile, structural loading from new equipment not verified against what the existing building was actually designed to carry, no plan for how the integration affects the building's existing electrical system and code compliance, and payback-period claims that ignore maintenance and equipment-replacement costs over the system's real lifetime.
4. Include validation, rollback, migration, or monitoring considerations where relevant.
5. Keep the plan realistic for the stated context and avoid architecture theater.

Output format:
- Plan overview
- Recommended approach and tradeoffs
- Implementation phases or rollout path
- Risks, dependencies, and validation checks
- Main assumptions or open questions

Missing information policy:
Ask up to 2 concise questions only if the goal or environment is unclear. Otherwise proceed with assumptions.

Quality bar:
- Make the plan executable.
- Avoid overengineering.
- Name the specific failure modes above rather than generic risk language.
- Show how the plan would survive real deployment pressure.
10

Design a User-Friendly Industrial Control Interface

Design an interface approach for an industrial control system that operators can use easily.

You’ll needsystem typeoperator taskssafety constraintsusability goals
Prompt
You are a senior design and product engineering architect creating a plan for a real engineering initiative.

Create a plan for the task below.

Context:
- Goal: [goal]
- Stack or environment: [stack]
- Current system or baseline: [current system]
- Constraints such as security, latency, budget, or staffing: [constraints]
- Scale, complexity, or production expectations: [scale]
- Risks, current issues, or dependencies: [risks]

Instructions:
1. Recommend a practical technical approach and explain why it fits the context.
2. Break the work into sensible phases, components, or rollout stages.
3. Explicitly address the failure modes that actually derail this kind of initiative: the interface designed around ideal lighting and quiet conditions instead of the actual noisy, gloved, high-stress environment operators work in, critical safety controls given the same visual weight as routine settings, no plan for how operators are trained or how errors are actually recovered from mid-task, and the design validated only with engineers instead of the actual operators who will use it daily.
4. Include validation, rollback, migration, or monitoring considerations where relevant.
5. Keep the plan realistic for the stated context and avoid architecture theater.

Output format:
- Plan overview
- Recommended approach and tradeoffs
- Implementation phases or rollout path
- Risks, dependencies, and validation checks
- Main assumptions or open questions

Missing information policy:
Ask up to 2 concise questions only if the goal or environment is unclear. Otherwise proceed with assumptions.

Quality bar:
- Make the plan executable.
- Avoid overengineering.
- Name the specific failure modes above rather than generic risk language.
- Show how the plan would survive real deployment pressure.
11

Create a Thermal Testing Method for a New Material

Create a method for testing the thermal properties of a material intended for electronics.

You’ll needmaterial typeuse casetesting conditionsconstraints
Prompt
You are a senior design and product engineering architect creating a plan for a real engineering initiative.

Create a plan for the task below.

Context:
- Goal: [goal]
- Stack or environment: [stack]
- Current system or baseline: [current system]
- Constraints such as security, latency, budget, or staffing: [constraints]
- Scale, complexity, or production expectations: [scale]
- Risks, current issues, or dependencies: [risks]

Instructions:
1. Recommend a practical technical approach and explain why it fits the context.
2. Break the work into sensible phases, components, or rollout stages.
3. Explicitly address the failure modes that actually derail this kind of initiative: test conditions that don't cover the actual temperature range and cycling rate the material will see in the device, thermal properties measured on an isolated sample instead of in the actual assembly context where interface effects matter, no distinction between short-term thermal response and long-term degradation under repeated cycling, and results reported without the measurement uncertainty that determines whether a marginal pass is actually reliable.
4. Include validation, rollback, migration, or monitoring considerations where relevant.
5. Keep the plan realistic for the stated context and avoid architecture theater.

Output format:
- Plan overview
- Recommended approach and tradeoffs
- Implementation phases or rollout path
- Risks, dependencies, and validation checks
- Main assumptions or open questions

Missing information policy:
Ask up to 2 concise questions only if the goal or environment is unclear. Otherwise proceed with assumptions.

Quality bar:
- Make the plan executable.
- Avoid overengineering.
- Name the specific failure modes above rather than generic risk language.
- Show how the plan would survive real deployment pressure.
12

Plan Wearable Technology Product Development

Write a product development plan for bringing wearable technology from concept to production.

You’ll needwearable concepttarget usersproduction goalsconstraints
Prompt
You are a senior design and product engineering architect creating a plan for a real engineering initiative.

Create a plan for the task below.

Context:
- Goal: [goal]
- Stack or environment: [stack]
- Current system or baseline: [current system]
- Constraints such as security, latency, budget, or staffing: [constraints]
- Scale, complexity, or production expectations: [scale]
- Risks, current issues, or dependencies: [risks]

Instructions:
1. Recommend a practical technical approach and explain why it fits the context.
2. Break the work into sensible phases, components, or rollout stages.
3. Explicitly address the failure modes that actually derail this kind of initiative: battery life and comfort treated as secondary to feature count, producing a device users don't actually want to wear all day, no plan for how the device handles being worn by different body types and skin tones, especially for sensors sensitive to fit, water or sweat resistance claims not tested under the device's actual real-world use pattern, and manufacturing cost not modeled until late, forcing a feature cut after the design is already locked.
4. Include validation, rollback, migration, or monitoring considerations where relevant.
5. Keep the plan realistic for the stated context and avoid architecture theater.

Output format:
- Plan overview
- Recommended approach and tradeoffs
- Implementation phases or rollout path
- Risks, dependencies, and validation checks
- Main assumptions or open questions

Missing information policy:
Ask up to 2 concise questions only if the goal or environment is unclear. Otherwise proceed with assumptions.

Quality bar:
- Make the plan executable.
- Avoid overengineering.
- Name the specific failure modes above rather than generic risk language.
- Show how the plan would survive real deployment pressure.
13

Design a Prototype for a Consumer Gadget

Design a prototype for a consumer gadget covering function, form factor, and UX.

You’ll needgadget ideacore functionsuser needsconstraints
Prompt
You are a senior design and product engineering architect creating a plan for a real engineering initiative.

Create a plan for the task below.

Context:
- Goal: [goal]
- Stack or environment: [stack]
- Current system or baseline: [current system]
- Constraints such as security, latency, budget, or staffing: [constraints]
- Scale, complexity, or production expectations: [scale]
- Risks, current issues, or dependencies: [risks]

Instructions:
1. Recommend a practical technical approach and explain why it fits the context.
2. Break the work into sensible phases, components, or rollout stages.
3. Explicitly address the failure modes that actually derail this kind of initiative: a form factor decided before the internal component layout is validated, forcing a redesign once real components don't fit, user experience tested only on the prototype's happy-path interaction, missing what happens when a user does something unexpected, no plan for how the prototype's cost and complexity will actually scale down to a manufacturable production version, and durability under everyday handling like drops or moisture not tested until far too late in the process.
4. Include validation, rollback, migration, or monitoring considerations where relevant.
5. Keep the plan realistic for the stated context and avoid architecture theater.

Output format:
- Plan overview
- Recommended approach and tradeoffs
- Implementation phases or rollout path
- Risks, dependencies, and validation checks
- Main assumptions or open questions

Missing information policy:
Ask up to 2 concise questions only if the goal or environment is unclear. Otherwise proceed with assumptions.

Quality bar:
- Make the plan executable.
- Avoid overengineering.
- Name the specific failure modes above rather than generic risk language.
- Show how the plan would survive real deployment pressure.
14

Create a Reliability Test Plan for a Mechanical Product

Develop a test plan for evaluating reliability and durability of a mechanical product.

You’ll needproduct typestress conditionsfailure criteriaconstraints
Prompt
You are a senior design and product engineering architect creating a plan for a real engineering initiative.

Create a plan for the task below.

Context:
- Goal: [goal]
- Stack or environment: [stack]
- Current system or baseline: [current system]
- Constraints such as security, latency, budget, or staffing: [constraints]
- Scale, complexity, or production expectations: [scale]
- Risks, current issues, or dependencies: [risks]

Instructions:
1. Recommend a practical technical approach and explain why it fits the context.
2. Break the work into sensible phases, components, or rollout stages.
3. Explicitly address the failure modes that actually derail this kind of initiative: test conditions that don't reflect the actual combined stresses such as vibration plus heat plus humidity the product sees in real use, a sample size too small to say anything statistically meaningful about failure rate, pass/fail criteria set arbitrarily instead of derived from the actual required service life, and failure analysis stopping at 'it broke' without root-causing why, so the same failure mode reappears in the next design iteration.
4. Include validation, rollback, migration, or monitoring considerations where relevant.
5. Keep the plan realistic for the stated context and avoid architecture theater.

Output format:
- Plan overview
- Recommended approach and tradeoffs
- Implementation phases or rollout path
- Risks, dependencies, and validation checks
- Main assumptions or open questions

Missing information policy:
Ask up to 2 concise questions only if the goal or environment is unclear. Otherwise proceed with assumptions.

Quality bar:
- Make the plan executable.
- Avoid overengineering.
- Name the specific failure modes above rather than generic risk language.
- Show how the plan would survive real deployment pressure.