Roomote is built for the work that constantly pulls teams out of focus: questions, planning, investigations, bugfixes, chores, review follow-up, and backlogged improvements. Teams usually start with codebase questions and small chores, then move into bugfixes, PR review, and more complex implementation work once the workflow feels natural.Documentation Index
Fetch the complete documentation index at: https://docs.newmote.dev/llms.txt
Use this file to discover all available pages before exploring further.
Good first handoffs
Start with tasks that are scoped, visible, and easy to verify:- explain how a part of the codebase works
- investigate a failing test, flaky preview, or confusing error
- make a small UI or API change
- draft a plan for a larger feature
- review a pull request for regressions
- apply feedback from a GitHub or Linear thread
- clean up a repeated chore that keeps falling off the backlog
Who uses it
Roomote is meant for the whole team, not just engineers sitting in an IDE.| Teammate | Good uses |
|---|---|
| Engineers | Start implementation, fix bugs, investigate failures, review diffs, resolve conflicts |
| PMs and founders | Ask codebase questions, draft plans, turn backlog ideas into scoped tasks |
| Designers | Request UI fixes, verify previews, ask how a flow is implemented |
| Support and ops | Investigate customer-reported issues, attach logs, ask for plain-English explanations |
| Marketing and GTM | Ask product-data or site questions, request small content or tracking changes |
What makes a task reviewable
Roomote should leave you with enough evidence to decide what happens next:- the transcript of what it did and why
- commands, tests, or checks it ran
- logs and terminal output when relevant
- screenshots or live previews for UI work
- code diffs and artifacts
- a pull request or clear next step when code changed