AI Prompts for ChatGPT for Engineering

Write a technical design document (TDD) for [DESCRIBE THE SYSTEM, FEATURE, OR COMPONENT]. Context: [DESCRIBE WHY THIS IS BEING BUILT, WHAT PROBLEM IT SOLVES, WHO USES IT]. Sections to include: (1) Overview and Goals, (2) Requirements (functional and non-functional), (3) Design Approach (chosen solution and rationale), (4) Architecture (system components, data flow, interfaces), (5) Trade-offs and Alternatives Considered (why you chose this approach over others), (6) Implementation Plan (phases and dependencies), (7) Testing Strategy, (8) Open Questions and Risks. Write for an engineering team audience. Use specific, technical language appropriate for [SOFTWARE/MECHANICAL/ELECTRICAL/CIVIL] engineering.

Write API documentation for these endpoints: [PASTE OR DESCRIBE THE API ENDPOINTS, PARAMETERS, RESPONSES, AND AUTHENTICATION]. For each endpoint, document: (1) endpoint URL and method, (2) description of what it does, (3) authentication requirements, (4) request parameters (type, required/optional, description, example), (5) request body schema (if POST/PUT), (6) response schema with all fields documented, (7) error codes and their meanings, (8) a complete example request and response (use realistic sample data, not "string" or "123"). Write in a style consistent with Stripe, Twilio, or SendGrid API documentation.

Write a system architecture overview document for [DESCRIBE THE SYSTEM: A DISTRIBUTED SYSTEM, A PRODUCT OR PLATFORM, A MANUFACTURING PROCESS, AN INFRASTRUCTURE SETUP]. The document should explain: (1) the system's purpose and the problem it solves, (2) the major components or subsystems and what each does, (3) how data or work flows through the system, (4) the key interfaces and integration points, (5) the scalability and reliability approach, (6) the primary technology choices and why. Write for a mixed audience of engineers and technical leadership. Use precise terminology but avoid unexplained acronyms. Describe where diagrams would go and what they should show.

Write an Engineering Change Order (ECO) for the following design change: [DESCRIBE WHAT IS CHANGING, WHY, AND FROM WHAT TO WHAT]. The ECO should document: (1) Change Description: what is being changed and why, (2) Problem Statement: what issue or opportunity drives this change, (3) Impact Assessment: which documents, drawings, parts, or processes are affected, (4) Required Actions: what needs to be updated, who is responsible, (5) Testing Required to Validate: what verification is needed before the change is released, (6) Schedule Impact: timeline implications, (7) Cost Impact: engineering hours and any material cost changes. Professional technical tone.

Write a lessons learned report for [DESCRIBE THE PROJECT, PRODUCT DEVELOPMENT CYCLE, OR ENGINEERING PROGRAM]. Key information to capture: [DESCRIBE WHAT WENT WELL, WHAT DID NOT GO WELL, WHAT WAS UNEXPECTED, WHAT TOOLS OR PROCESSES WERE HELPFUL OR NOT]. The report should: (1) briefly describe the project context and objectives, (2) document lessons in categories: technical, process, team and communication, schedule and cost, (3) for each lesson: describe what happened, why it happened, and what to do differently next time, (4) include a top-5 prioritized action item list for future projects. Blameless and factual tone. This report will be shared with future project teams.

Write a requirements document for [DESCRIBE THE SYSTEM OR PRODUCT: A SOFTWARE SYSTEM, A MECHANICAL COMPONENT, A MANUFACTURING PROCESS, AN EMBEDDED DEVICE]. Requirements to capture: [LIST OR DESCRIBE FUNCTIONAL, PERFORMANCE, ENVIRONMENTAL, SAFETY, AND COMPLIANCE REQUIREMENTS]. Format each requirement as: a unique identifier (e.g., REQ-001), the requirement statement in "The system shall..." format, the rationale, the priority (mandatory/desired/optional), and the verification method (test, analysis, inspection, demonstration). Ensure every requirement is: specific, measurable, achievable, necessary, and testable. Flag any requirement that is ambiguous or untestable.

Create a design review checklist for a [PRELIMINARY DESIGN REVIEW (PDR) / CRITICAL DESIGN REVIEW (CDR) / FINAL DESIGN REVIEW] for [DESCRIBE THE PRODUCT OR SYSTEM]. The checklist should verify: (1) requirements coverage (are all requirements addressed by the design), (2) design completeness (are all subsystems defined), (3) interface control (are all interfaces between components defined), (4) failure mode consideration (have FMEAs been conducted for critical components), (5) safety analysis, (6) testability, (7) manufacturability, (8) material and component selection documentation, (9) compliance with applicable standards (list if known), (10) action item tracking from previous reviews.

Write a test plan for [DESCRIBE WHAT IS BEING TESTED: A SOFTWARE SYSTEM, A MECHANICAL ASSEMBLY, AN ELECTRICAL CIRCUIT, A MANUFACTURED PRODUCT]. The test plan should include: (1) Test Objectives and Scope, (2) Test Items (what specifically is being tested), (3) Features to Test and Features Not to Test, (4) Testing Approach: test levels (unit, integration, system, acceptance), types of testing, and test environment, (5) Test Cases (for each requirement, describe the test condition, input, expected output, and pass/fail criteria), (6) Test Schedule and Milestones, (7) Resource Requirements, (8) Risks and Contingencies. Formal technical document style.

Create a Failure Mode and Effects Analysis for [DESCRIBE THE SYSTEM, COMPONENT, OR PROCESS]. For each major subsystem or process step, identify: (1) potential failure modes (how could it fail), (2) potential effects of each failure (what would happen to the system or end user), (3) potential causes of each failure, (4) current controls that detect or prevent the failure, (5) severity rating (1-10), (6) occurrence rating (1-10), (7) detection rating (1-10), (8) RPN (Risk Priority Number = S x O x D), and (9) recommended actions for high-RPN failures (RPN > 100). Format as a table with these columns. Prioritize the top 5 high-RPN items for action.

Write an Interface Control Document for the interface between [SYSTEM A] and [SYSTEM B]. Describe the interface: [DESCRIBE WHAT TYPE OF INTERFACE: MECHANICAL, ELECTRICAL, SOFTWARE, FLUID, COMMUNICATION PROTOCOL]. The ICD should define: (1) interface purpose and overview, (2) physical interface characteristics (dimensions, tolerances, connectors, materials), (3) functional requirements (what must the interface enable), (4) electrical or signal characteristics (voltages, current, signal protocols, data rates), (5) environmental requirements at the interface (temperature, vibration, IP rating), (6) performance requirements (bandwidth, latency, load), (7) verification approach. This document governs how both teams must design to the interface.

Explain [DESCRIBE THE TECHNICAL CONCEPT, ENGINEERING PRINCIPLE, OR DESIGN DECISION] to a [PROJECT MANAGER / EXECUTIVE / CLIENT / END USER] who does not have an engineering background. The explanation should: (1) start with an analogy or everyday example that makes the concept intuitive, (2) explain the core principle in plain language without dumbing it down to the point of inaccuracy, (3) connect it to the decision or outcome they care about, (4) use one visual description or diagram suggestion to reinforce the concept, (5) avoid acronyms without defining them. Test the explanation by asking: would a smart non-engineer walk away understanding what this is and why it matters?

Write a technical project status report for senior leadership (non-engineers). Project: [DESCRIBE]. Current status: [ON TRACK/AT RISK/DELAYED]. Key technical update: [DESCRIBE IN ENGINEERING TERMS]. The report should: (1) state the overall project health clearly in the first line, (2) summarize progress in outcome terms (what is now working, what is not), (3) translate any technical issues into business impact language (not "the API timeout is 500ms over spec" but "this will delay launch by 3 weeks unless resolved"), (4) present the 1-2 decisions or resources needed from leadership clearly, (5) avoid engineering jargon that requires technical background. Under 350 words.

Write a trade study summary presenting the options analysis for [DESCRIBE THE DESIGN DECISION: MATERIAL CHOICE, ARCHITECTURE APPROACH, TECHNOLOGY SELECTION, VENDOR CHOICE]. Options evaluated: [LIST A, B, C WITH BRIEF DESCRIPTIONS]. Evaluation criteria: [LIST WITH WEIGHTS IF APPLICABLE]. The summary should: (1) state the recommendation in the first paragraph, (2) describe each option and its key trade-offs, (3) present the evaluation in a table format, (4) explain why the recommended option was selected over the alternatives, (5) identify the key assumption that would change the recommendation if it proves false. Write for a mixed audience of engineers and technical management.

Write a technical risk register update for [PROJECT NAME] to be shared with the project steering committee. Risks to document: [DESCRIBE 5-8 TECHNICAL RISKS]. For each risk: (1) risk description (what could happen), (2) probability (High/Medium/Low), (3) impact (High/Medium/Low), (4) current mitigation actions in place, (5) residual risk after mitigation, (6) owner, (7) early warning indicators. The register should: distinguish between risks that are being actively monitored (yellow) and those that require immediate attention (red). Present in a table format followed by a 3-sentence executive summary of the overall risk posture.

Write the technical approach section of an engineering proposal in response to [DESCRIBE THE RFP, PROCUREMENT SPECIFICATION, OR CUSTOMER REQUEST]. What we are proposing: [DESCRIBE THE TECHNICAL SOLUTION]. The section should: (1) demonstrate understanding of the customer's technical requirements, (2) describe our proposed technical solution at a level of detail appropriate for this stage, (3) explain our engineering methodology and design approach, (4) highlight our relevant technical experience and credentials, (5) present the key technical risks and how we will manage them. Length: [SPECIFY PER RFP REQUIREMENTS OR 500-750 WORDS]. Professional engineering proposal style.

Conduct a root cause analysis for this engineering failure or defect: [DESCRIBE WHAT FAILED, WHEN, UNDER WHAT CONDITIONS, ANY AVAILABLE DATA]. Use the 8D (Eight Disciplines) problem-solving framework: (1) Team formation (who should be involved), (2) Problem description (5W2H: what, where, when, who, why, how, how many), (3) Containment actions (immediate fixes to stop the bleeding), (4) Root cause identification (use Ishikawa/fishbone diagram structure: machine, material, method, measurement, environment, people), (5) Permanent corrective actions, (6) Implementation plan, (7) Prevent recurrence (update FMEA, procedures, training), (8) Lessons learned and recognition. Be specific about each step.

Help me plan a Design of Experiments to optimize [DESCRIBE WHAT YOU ARE TRYING TO OPTIMIZE: A MANUFACTURING PROCESS, A MATERIAL FORMULATION, A SYSTEM PARAMETER]. Response variable(s): [WHAT YOU ARE MEASURING]. Factors under investigation: [LIST THE VARIABLES AND THEIR RANGES]. Constraints: [TIME, COST, NUMBER OF RUNS AVAILABLE]. Recommend: (1) whether to use a full factorial, fractional factorial, or response surface design and why, (2) the specific design matrix for my number of factors, (3) how to randomize and block the runs, (4) what to do with runs that produce outliers, (5) how to analyze the results to identify main effects and interactions. Provide the design table I should use to run the experiment.

Help me set up [AN ENERGY BALANCE / A MASS BALANCE] for this engineering system: [DESCRIBE THE SYSTEM: A CHEMICAL REACTOR, A HEAT EXCHANGER, A COMBUSTION SYSTEM, A BUILDING HVAC SYSTEM]. Inputs to the system: [DESCRIBE]. Outputs from the system: [DESCRIBE]. Relevant physical properties: [LIST KNOWN VALUES]. Set up the balance equation, identify what I need to solve for, identify what data or assumptions I need to complete the calculation, and show the algebraic solution path. If multiple scenarios need to be analyzed, show how the balance changes between them.

Create a decision matrix for this engineering selection problem: [DESCRIBE THE DECISION: SELECTING A MATERIAL, CHOOSING BETWEEN DESIGN CONCEPTS, SELECTING A MANUFACTURING PROCESS]. Options to evaluate: [LIST A, B, C, D]. Evaluation criteria: [LIST YOUR CRITERIA, E.G., COST, PERFORMANCE, MANUFACTURABILITY, RELIABILITY, SCHEDULE RISK, REGULATORY COMPLIANCE]. Assign weights to each criterion (total 100%). Score each option 1-5 on each criterion. Calculate the weighted total score. Present the matrix as a table, state the recommended option, and explain whether the recommendation changes significantly if the weights are adjusted. Identify the one criterion that is most sensitive to the outcome.

Write a detailed engineering Standard Operating Procedure for [DESCRIBE THE PROCESS: RUNNING A SPECIFIC TEST, OPERATING A PIECE OF EQUIPMENT, PERFORMING A CALCULATION OR ANALYSIS, EXECUTING AN INSPECTION PROCEDURE]. The SOP should include: (1) Purpose and Scope, (2) Safety Precautions and PPE required, (3) Equipment and Materials needed, (4) Pre-operation checklist, (5) Step-by-step procedure (numbered, specific, written so a trained technician can execute without asking questions), (6) Acceptance criteria for each critical step, (7) What to do if a step fails or produces out-of-spec results, (8) Post-operation documentation requirements. Write for a technical operator audience.