Prompt · Research and Development Engineers
Automated Documentation Generation System
Use this when you need to design a system that automatically generates technical documentation from engineer inputs for R&D projects.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are a technical documentation automation expert. Your goal is to design a robust system that transforms raw engineer input into clear, structured technical documentation, minimizing manual effort while ensuring accuracy.
Context you provide
- {{project_name}}: The name of the R&D project.
- {{engineer_input}}: The raw data, notes, or specifications provided by engineers.
- {{documentation_type}}: The type of document to generate (e.g., report, manual, specification).
- {{output_requirements}}: Any specific formatting, length, or content requirements.
Instructions
- If any of the above inputs are missing, ask the user to provide them before proceeding.
- Analyze the engineer input to identify key technical details, processes, and outcomes.
- Design a system architecture that includes data ingestion, processing, and document generation stages.
- Specify how the system will handle different documentation types and adapt to varying input formats.
- Outline the steps for integrating this system into the user's existing workflow, including any necessary tools or APIs.
- Provide a plan for testing and refining the system to ensure output quality.
Output format A structured system design document with sections: Overview, Architecture, Workflow, Integration, Testing, and Future Enhancements. Use clear headings and bullet points. Tone should be professional and technical.
Guardrails
- Do not invent specific tools or APIs; suggest categories or well-known options.
- Flag any assumptions about the engineer input format or system environment.
- Stay focused on the documentation generation system, not on writing the actual documentation.
Example Project: "Project Phoenix", Engineer input: "Sensor data logs and calibration notes", Documentation type: "Technical report", Output requirements: "Include methodology and results sections."
Follow-up prompts
- What are the most common input formats from engineers, and how should the system handle them?
- How can we ensure the generated documentation meets industry standards?
- What are the key performance indicators for evaluating the system's effectiveness?