Product Description Generator Prompt

5 steps to a reviewable draft

1. 01

   Lock the product record

   Gather the current name, attributes, compatibility, limitations, price boundary and approved claims. Note which facts can change by region or time.

   Result: A current product record that the draft must not exceed.

2. 02

   Define the buyer context

   State who the page serves, what they need to know and what action the description supports. Keep use cases separate from promises.

   Result: A reader boundary for the description.

3. 03

   Draft the description

   Ask for copy that uses only the locked facts and exposes a placeholder wherever the factsheet lacks a needed detail.

   Result: A draft that tells the buyer what is confirmed and tells the owner what needs an answer.

   Your prompt

   Copy prompt

   Draft a product description from the approved product record.
   
   Product facts and approved claims: {{facts}}
   Buyer context and page purpose: {{buyer}}
   Required format and limits: {{format}}
   Disclosure and review requirements: {{constraints}}
   
   Return a heading, short description, feature explanation, use context, limitations or compatibility note, claim check and product-owner question. Mark missing information as [NEEDS PRODUCT INPUT]. Do not invent performance, materials, availability, pricing, customer results, certifications or compatibility.

   Example input

   Describe a reporting template for agency teams. The factsheet confirms editable sections and export format; pricing remains pending.

   Example output

   Description: editable reporting sections. Price: [NEEDS PRODUCT INPUT]. Compatibility: [NOT PROVIDED].

4. 04

   Check every product assertion

   Match each factual phrase with the product record and verify required disclosures, regional information and destination links.

   Result: A product description with no unsupported product promise.

5. 05

   Release the approved copy

   Store the final version with the product record date, owner and freshness trigger for later updates.

   Result: Copy that can be refreshed when the product changes.