Review implementation of an rdm phase or task
Review the implementation of an rdm phase or task. $ARGUMENTS should be <roadmap-slug> <phase-number> for a phase, or --task <task-slug> for a task.
Read docs/principles.md before starting. It contains project conventions that should guide your work.
Parse arguments: determine whether this is a phase review or task review from $ARGUMENTS.
--task, the next argument is a task slug.Read the acceptance criteria:
mcp__rdm__rdm_phase_show tool with project: "fbm", roadmap: <slug>, and phase: <number>.mcp__rdm__rdm_task_show tool with project: "fbm" and .
Extract the acceptance criteria, steps, and any other requirements from the body.task: <slug>Identify the implementation diff: use git log --oneline -20 and git diff to understand what was recently changed. Identify the commits and files relevant to this phase or task.
Dispatch parallel review agents using the Agent tool. Launch at least two agents concurrently:
Agent 1 — AC Compliance Reviewer:
Agent 2 — Code Quality Reviewer:
Collect and consolidate results from both agents into a single report:
Present the report to the user in a clear, structured format.
Offer to create rdm tasks for any actionable issues found using the mcp__rdm__rdm_task_create tool with project: "fbm", a descriptive slug, title, and body.