Before you start#
Rovara v0.3.4 includes the native workflow. This page follows the inspected mainline source, which may include later changes. Deployment settings and feature flags still apply. Release and coverage details →
You need access to a registered project and its Slack channel, or a coding-tool connection. Choose Full when behavior, interfaces or implementation choices need discussion. Full changes planning depth; it does not relax project-required checks or reviews.
1. Choose Full at task start#
Start the request with full: in the bound channel:
@AgentX full: Add password reset to the account page.
Keep existing sign-in behavior.
Without a prefix, a larger change gets a card suggesting Full, with Start, Use Quick instead and Just answer. From a coding tool, ask it to call agentx_start_workflow with workflow_path: "full" for your project.
2. Agree on requirements#
Inspect intended behavior, constraints, non-goals and acceptance scenarios. On the task page, each of the document’s decisions shows AgentX’s recommendation already picked; choose another option where you disagree, and comment on any claim. Approve the current document when it represents the work you want.
For password reset, discuss expiry, error messages and existing authentication behavior here, not after implementation.
3. Review the design#
The design is written from the approved requirements. Inspect the proposed interfaces, component boundaries, dependencies and failure behavior. Ask for alternatives or corrections before approving this version.
4. Approve the coding plan#
The coding plan is written from the approved design. Review the implementation steps and check choices. Required project checks stay on; add the project’s optional checks you want. Approve this version to start coding.
5. Review the work#
Coding, checks and reviews run as in Quick, and AgentX opens a draft PR when they pass. PR feedback follows the same owner-controlled proposal and fix loop.
What happens after approval →When a document changes#
Request changes needs at least one comment or a note. AgentX writes the next version and answers each comment you sent under it. Comments you send with an Approve are answered by the next document, for example “Done in the coding plan: …”.
Each comment stays on the same claim, decision or check if it is still there, marked “from v1”; otherwise it moves under “Removed claims”. An approval applies only to the version it names. Task page guide →