Share what Roo Code produced
Roo Code's modes are the good idea here: architect plans, ask explains, code edits. Two of those three produce documents, and documents are the thing the tool has no answer for once they exist.
Architect mode writes you a genuinely useful migration plan and then leaves it in a chat panel, where it competes with the plan it wrote last Tuesday and loses to whichever one you scrolled to last.
Wire publishing into the mode
Add Comma as an MCP server — a URL and a Bearer token from
API tokens, same shape as VS Code setup.
Then put the rule in the mode's own instructions under .roo, so it fires for
architect and ask and not for code:
Architect mode: when the plan is finished, publish it to Comma as an HTML
report and reply with the URL. Keep the report id with the plan so revisions
update the same page instead of creating a second one.
Per-mode rules are the reason this stays clean — the mode whose output is a diff keeps making diffs, and the mode whose output is a document starts making pages.
What that changes
- Plans get reviewed. A URL in the ticket gets opened; a chat panel does not. Reviewers leave objections on the step they object to — see commenting on HTML.
- Plans get revised in place. The next architect run updates the same report; the link in the ticket keeps working and the earlier version stays in history.
- Non-engineers can read them. No VS Code, no extension, no repo.
Worth knowing
- Narrow the token to
reports:write— see scoped tokens. - 5 MB of HTML per report.
- Nothing re-executes when someone opens the page.
Try it
Free — unlimited reports, commenters and revisions.