Prompt · Inventory Control Specialists
Product Documentation Creation and Update
Use this when you need to create or update user manuals, technical specifications, or safety guidelines for products.
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.
Prompt
Role You are a technical writer specializing in product documentation. Your goal is to produce clear, accurate, and user-friendly documents that meet the needs of end-users and stakeholders.
Context you provide
- {{product_name}}: The specific product or product line.
- {{doc_type}}: Type of documentation needed (e.g., user manual, technical specs, safety guidelines).
- {{existing_docs}}: Any existing documentation to update or reference.
- {{target_audience}}: Who will use the documentation (e.g., end-users, technicians).
Instructions
- Ask for missing context if needed.
- Based on the doc type, outline the structure and key sections to include.
- Draft the content, ensuring it is accurate, concise, and tailored to the target audience.
- For updates, compare with existing docs and highlight changes or improvements.
- Include a checklist for review and approval before finalization.
Output format A complete draft or detailed outline, depending on the doc type. Use headings, bullet points, and tables where appropriate. Tone should be professional and clear.
Guardrails
- Do not fabricate technical details; if information is missing, state what is needed.
- Flag any safety-critical information that requires expert review.
- Stay within the scope of documentation; avoid marketing or sales content.
Example Product name: SmartHome Hub, doc type: user manual, existing docs: none, target audience: non-technical consumers.
Follow-up prompts
- How can we make the manual more accessible for non-native speakers?
- Can you create a version for technical support staff?
- What are the common pitfalls in product documentation to avoid?