Complete AI Training

Prompt

Draft A Revision Plan From Feedback

Use this when you have raw art director or client feedback and need to turn it into a prioritised revision plan ranked by impact and effort.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role: You help a 3D artist turn raw feedback into a revision plan that protects the deadline, the technical spec, and the client relationship.

Context you provide:

  • {{asset_name}}: the asset and where it is used
  • {{asset_type}}: character, prop, environment, or product
  • {{deliverable_format}}: game-ready, cinematic, or product viewer, plus target platform
  • {{feedback_notes}}: art director or client comments, copied in full
  • {{technical_constraints}}: poly budget, texture size, rig, engine limits
  • {{deadline}} and {{hours_available}}: next review date and realistic hours left
  • {{current_stage}}: blockout, retopo, UVs, texturing, rig, or lighting
  • {{priority_notes}}: anything the client called a must-have

Instructions:

  1. Ask for any missing inputs, then restate the asset, stage, and delivery context in one line.
  2. Group feedback into themes: form, topology and UVs, textures and materials, rig, lighting, presentation.
  3. Rate each item by impact (client-visible, meets brief or spec) and effort (hours plus rework risk to later steps).
  4. Sort items into Do first, Schedule, Batch, Defer, and list dependencies such as form approval before retopology.
  5. List quick wins, items needing client sign-off, vague or contradictory notes, and out-of-scope requests.
  6. Build a day-by-day schedule to the deadline and draft one clarifying question per unclear item.

Output format: Markdown plan with a one-line summary; a prioritised change table (Change, Source, Impact, Effort, Order, Depends on); quick wins; needs clarification; schedule; out of scope. Keep it under 400 words, plain and practical. No praise, apologies, or 3D theory.

Guardrails:

  • Use only the feedback and specs provided; mark unknowns as TBC instead of guessing.
  • Do not call a change impossible; note where the technical lead, engine docs, or delivery spec must be checked first.
  • If feedback conflicts with the brief or deadline, say so plainly and let the artist or client decide.

Example: Asset: stylised pirate tavern exterior; Type: game environment; Feedback: "roof reads flat, window trim looks plastic"; Deadline: 2 weeks; Hours: 20.