Guide contents
Feedback arrives from chats, calls and comments on the mockup. Some of it repeats, some contradicts itself, and some sounds like “make it feel more modern”. Octodus can turn it into a working list and keep every item linked to the original comment.
What to prepare
- Attach the current screens and the comments on them. Say which version of the design counts as current.
- Label the source of each comment and its author if that matters for sign-off.
- For the first exercise, use the sample file with descriptions of two screens and their comments. It contains a deliberate contradiction.
The source files use sample data. Replace it with your own once you know the process.
Keep the link to the original comments
Ask Octodus to sort the comments by screen and element: headline, form, button, examples block. Every change should keep a reference to the comment number or its author.
Merging identical requests is useful. Replacing several different comments with one vague sentence means losing context.
Turn the attached comments into a plan for the next iteration. For each item give the screen, the element, the essence of the change and the numbers of the original comments. Merge duplicates. List ambiguous requests and contradictions separately. Do not choose between mutually exclusive requirements yourself.
Separate ready actions from open questions
Replacing approved copy can go straight into work. A request to both remove and expand a form needs a decision. Ask Octodus to suggest short questions for sign-off.
Set priorities by the goal of the product. If you want more completed forms, that does not mean every extra field has to go: some data may be needed to process the request.
Sample result
What should stay visible
- Can go ahead: change the button text to “Get a quote” (comment 3).
- Needs a decision: remove the phone field or make it required (comments 1 and 2 contradict each other).
- Needs clarification: what exactly “a more high-tech first screen” means (comment 4 gives no verifiable outcome).
Main caveat and checks
A tidy list can hide unresolved disagreements. Do not turn contradictory wishes into an agreed brief. The agent’s job at this stage is to make the choices visible.
Before you use the result
- Every change is linked to an original comment.
- Contradictions did not disappear when items were merged.
- Ambiguous wishes turned into questions.
- After sign-off it is clear what to change and how to accept the result.
How to repeat this on your own task
Save your review format and your team’s rules as a skill. On the next iteration, attach the new version and fresh comments. Ask the agent not to carry over already completed comments into the new list without a reason.
Try this scenario
Download the source file, copy the prompt and send both to Octodus.