Implement the next phase of an rdm roadmap
Implement a phase from an rdm roadmap. $ARGUMENTS should be <roadmap-slug> [phase-number].
Read docs/principles.md before starting. It contains project conventions that should guide your work.
$ARGUMENTS.mcp__rdm__rdm_phase_list tool with project: "fbm" and roadmap: <slug>, then pick the first not-started or in-progress phase.mcp__rdm__rdm_phase_show tool with project: "fbm", roadmap: <slug>, and phase: <stem> to get full context, steps, and acceptance criteria.mcp__rdm__rdm_phase_update tool with project: "fbm", , , and .roadmap: <slug>phase: <stem>status: "in-progress"EnterPlanMode tool to switch into planning mode.ExitPlanMode tool to switch back to execution mode.Done: line in the commit message — the post-merge hook will mark the phase done and record the commit SHA.
Use the exact roadmap slug and phase stem from the rdm tools you used earlier — do NOT invent or paraphrase them:
Done: <roadmap-slug>/<phase-stem>
mcp__rdm__rdm_task_create tool with project: "fbm", a descriptive slug, title, and body.