AI workflow
Give your agent the whole picture.
Your coding agent can make the change. Give it the comments and decisions to get started.
Through MCP, your agent gets the feedback, discussion and page-element details. Decide what matters, agree on the changes and keep building in your own project.
See a reviewBring your agent the feedback and discussion. Agree on the change before it edits your code.
Start with the request. Work towards a decision.
The comment and discussion
- Where: the “Contact us” button on a services page.
- Client: change the label to “Book a call”.
- Designer: give the button more space.
- Project lead: use “Book a call”, keep the current destination and increase the spacing.
The wording is agreed. The exact spacing still needs an answer.
Ask your agent
Read this review and its discussion. Separate agreed changes from open questions and show which page elements they concern. Propose a change plan before editing the code.
Analysis
Ready: change “Contact us” to “Book a call”. Keep the link.
Needs a decision: how much extra spacing to add.
Your decision
Make the wording change. Keep the link and leave the spacing unchanged for now.
Contact us → Book a call
Before
Same destination · same spacing
After the agreed change
Same destination · same spacing
The destination stays the same.
Spacing stays unchanged until it is agreed.
Make the agreed change. Leave the open question open.
Your coding agent makes the change in your project. You check the result before closing the feedback.
The comments, the page and the decision are ready for your agent. You can focus on the change.
A clear starting point for your agent.
What the user said
Do I have to invite my team before I can try this?
What the team decided
Solo use is supported. Add “You can invite teammates later.”
What you ask the agent to do
Read the feedback and discussion for the invite step. Separate the user’s question from the team’s decision. Propose the agreed copy change before editing code. Do not change the invite flow.
Agent plan
- Add “You can invite teammates later.” near the invite step.
- Keep the existing invite flow.
- Check the explanation on the actual screen before closing the item.
Work with the agent you already use.
Connect through MCP. Give your agent access to the right project, then ask it to read the feedback and discussion before proposing changes.
You decide what changes. Your agent works in your codebase.
The connection is called MCP.
It lets your agent work with the feedback and page-element context from the projects you authorize. MCP is included in every plan; your external agent is separate.
Depending on the permissions and supported tools, your agent can read feedback, reply in a thread and close an item. Review the available actions before granting access.
Keep the work moving.
Find open feedback, read the discussion and reply through your agent. Check the work before closing the item.
Working with a developer instead?
Discuss the feedback, then export it as Markdown. Your developer gets the context and keeps their own way of working.
Working with a developer?
Discuss feedback and export it as Markdown. Your developer gets the same context, without an AI workflow.
An agent’s proposal is not a product decision. A closed comment is not proof that code was deployed.
Start your next change with the context it needs.
Collect feedback. Agree on what matters. Get to work.