name	rdm-implement
description	Implement the next phase of an rdm roadmap
allowed-tools	["Read","Bash","Glob","Grep","Write","Edit","EnterPlanMode","ExitPlanMode","mcp__rdm__rdm_phase_list","mcp__rdm__rdm_phase_show","mcp__rdm__rdm_phase_update","mcp__rdm__rdm_task_create"]

Implement a phase from an rdm roadmap. $ARGUMENTS should be <roadmap-slug> [phase-number].

Principles

Read docs/principles.md before starting. It contains project conventions that should guide your work.

Steps

Parse arguments: extract the roadmap slug and optional phase number from $ARGUMENTS.
Find the phase: if no phase number was given, use the mcp__rdm__rdm_phase_list tool with project: "fbm" and roadmap: <slug>, then pick the first not-started or in-progress phase.
Read the phase: use the mcp__rdm__rdm_phase_show tool with project: "fbm", roadmap: <slug>, and phase: <stem> to get full context, steps, and acceptance criteria.
Mark in-progress: use the mcp__rdm__rdm_phase_update tool with project: "fbm", roadmap: <slug>, phase: <stem>, and status: "in-progress".
Enter plan mode: use the EnterPlanMode tool to switch into planning mode.
Create an implementation plan using the planning tool. The plan should:
- Break the phase into concrete implementation steps based on the phase description and acceptance criteria
- Include a final step: "Review changes with user and commit"
Wait for user approval: the user will review the plan and either accept or request changes. Do not proceed until the plan is accepted.
Exit plan mode: use the ExitPlanMode tool to switch back to execution mode.
Execute the plan: implement each step, following the plan and the phase's acceptance criteria.
Review with user: present a summary of the changes and ask the user to confirm they are ready to finalize.
Finalize: on user acceptance, commit the implementation changes with a 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>
```
Handle side-work: if you discover bugs or unrelated improvements, create tasks using the mcp__rdm__rdm_task_create tool with project: "fbm", a descriptive slug, title, and body.

Más de este repositorio

mismo repositorio

rdm-document

edpaget/bot-showalter

Generate user documentation from a completed rdm roadmap

2026-03-220

rdm-review

edpaget/bot-showalter

Review implementation of an rdm phase or task

2026-03-220

rdm-roadmap

edpaget/bot-showalter

Create an rdm roadmap with phases for a topic

2026-03-220

rdm-tasks

edpaget/bot-showalter

Work on rdm tasks

2026-03-220

fbm

edpaget/bot-showalter

Run fantasy baseball projection commands — predict, evaluate, compare systems, look up player projections/valuations, manage cached datasets, evaluate keeper league trades and optimization, run draft boards and mock drafts, and use Yahoo Fantasy integration for rosters, draft tracking, and keeper cost derivation. Use this when the user asks to run projections, compare systems, evaluate accuracy, look up a player, check valuations, manage/rebuild cached datasets, evaluate keeper league decisions/trades/optimization, view draft boards, run mock drafts, sync Yahoo league data, or manage Yahoo-derived keeper costs.

2026-03-110

experiment-breakout-bust

edpaget/bot-showalter

Run an autonomous feature-engineering experiment loop on the breakout-bust classification model. Tests candidate features against P(breakout) and P(bust) probability targets using marginal-value with auto-logging. Use when the user asks to "experiment on breakout-bust", "improve breakout-bust", or "explore features for breakout".

2026-03-060

name	rdm-implement
description	Implement the next phase of an rdm roadmap
allowed-tools	["Read","Bash","Glob","Grep","Write","Edit","EnterPlanMode","ExitPlanMode","mcp__rdm__rdm_phase_list","mcp__rdm__rdm_phase_show","mcp__rdm__rdm_phase_update","mcp__rdm__rdm_task_create"]

Implement a phase from an rdm roadmap. $ARGUMENTS should be <roadmap-slug> [phase-number].

Principles

Read docs/principles.md before starting. It contains project conventions that should guide your work.

Steps

Parse arguments: extract the roadmap slug and optional phase number from $ARGUMENTS.
Find the phase: if no phase number was given, use the mcp__rdm__rdm_phase_list tool with project: "fbm" and roadmap: <slug>, then pick the first not-started or in-progress phase.
Read the phase: use the mcp__rdm__rdm_phase_show tool with project: "fbm", roadmap: <slug>, and phase: <stem> to get full context, steps, and acceptance criteria.
Mark in-progress: use the mcp__rdm__rdm_phase_update tool with project: "fbm", roadmap: <slug>, phase: <stem>, and status: "in-progress".
Enter plan mode: use the EnterPlanMode tool to switch into planning mode.
Create an implementation plan using the planning tool. The plan should:
- Break the phase into concrete implementation steps based on the phase description and acceptance criteria
- Include a final step: "Review changes with user and commit"
Wait for user approval: the user will review the plan and either accept or request changes. Do not proceed until the plan is accepted.
Exit plan mode: use the ExitPlanMode tool to switch back to execution mode.
Execute the plan: implement each step, following the plan and the phase's acceptance criteria.
Review with user: present a summary of the changes and ask the user to confirm they are ready to finalize.
Finalize: on user acceptance, commit the implementation changes with a 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>
```
Handle side-work: if you discover bugs or unrelated improvements, create tasks using the mcp__rdm__rdm_task_create tool with project: "fbm", a descriptive slug, title, and body.