If an AI edit completes only half of a multi-part request, turn the request into a dependency list before rewriting it again. Some changes can be judged independently. Others alter the framing, position, or object structure that later instructions depend on. A longer paragraph can preserve every word while still leaving that order unresolved.
Describe operations as visible decisions
Replace “make it professional and fix everything” with a list of observable changes. For example: expand the canvas on the right, move the subject into the left third, change the coat color, and remove one stain. Separately list protected features such as face, body proportions, product lettering, and accepted background objects.
Now ask what each operation needs as input. Moving the subject changes where a stain or accessory sits. Expanding the canvas may change the final crop. A local instruction referring to the upper-right corner can become ambiguous after a structural change. Put geometry and placement decisions before edits that depend on their final coordinates.
Use a dependency table
| Operation | Needs first | Acceptance | Rollback point |
|---|---|---|---|
| Expand right margin | Approved source and final ratio | Required space without subject distortion | Original |
| Move subject left | Approved expanded composition | Correct placement and contact | Expansion accepted |
| Change coat color | Accepted subject location | Color changes; face and cut stay faithful | Placement accepted |
| Remove stain | Correct final coat region | Stain removed without new fabric defect | Color accepted |
This hypothetical sequence is a planning tool, not a required order for every editor. If your application offers deterministic layout tools, use those where appropriate instead of asking a generative model to repeat a correct operation. Keep separate versions, consistent with the non-destructive editing principle of retaining usable source information.
Separate dependent stages from independent options
Two alternative background colors do not need to be generated serially from one another. They can branch from the same accepted composition. Feeding the blue-background experiment into the green-background experiment makes the second test inherit unrelated changes and weakens the comparison.
By contrast, a final shadow adjustment genuinely depends on where the subject now stands. Complete and inspect that placement before solving contact. The objective is not to maximize the number of steps; it is to prevent a failed prerequisite from being polished through several later edits.
Approve a stage before it becomes evidence
For each result, check the named change, the protected features, and whether it remains a valid input for the next stage. If a coat-color edit changes a face, record that as a failure even if the coat is excellent. Return to the last accepted stage or use a suitable localized repair rather than carrying an unapproved face forward.
In an Imagild workflow, keep this table beside the input files and the actual downloaded results. When requesting another revision, identify the accepted starting version and only the unresolved operation. A concise stage-specific brief can be more actionable than repeating a complete project paragraph whose earlier requirements have already been satisfied.