Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

Loslegen

rdm-tasks

Sterne0

Forks0

Aktualisiert22. März 2026 um 19:12

Work on rdm tasks

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

edpaget

edpaget/bot-showalter

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

ProjektmanagementspezialistenWirtschafts- und Finanzberufe·SOC 13-1082

SKILL.md

readonly

name	rdm-tasks
description	Work on rdm tasks
allowed-tools	["Read","Bash","Glob","Grep","Write","Edit","EnterPlanMode","ExitPlanMode","mcp__rdm__rdm_task_list","mcp__rdm__rdm_task_show","mcp__rdm__rdm_task_update"]

Work on rdm tasks. $ARGUMENTS is an optional task slug.

Principles

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

Steps

List tasks: use the mcp__rdm__rdm_task_list tool with project: "fbm" to see open and in-progress tasks.
Show details: if a task slug was provided in $ARGUMENTS, use the mcp__rdm__rdm_task_show tool with project: "fbm" and task: <slug>. Otherwise, present the task list and ask the user which task to work on.
Mark in-progress: use the mcp__rdm__rdm_task_update tool with project: "fbm", task: <slug>, 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 task into concrete implementation steps based on the task description
- 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.
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: task/<slug> line in the commit message — the post-merge hook will mark the task done and record the commit SHA. Use the exact task slug from the rdm tools you used earlier — do NOT invent or paraphrase it. If the task is also part of a roadmap phase, include a Done: <roadmap-slug>/<phase-stem> line as well (using exact slugs/stems from rdm).

Mehr aus diesem Repository

gleiches Repository

rdm-document

edpaget/bot-showalter

Generate user documentation from a completed rdm roadmap

2026-03-220

rdm-implement

edpaget/bot-showalter

Implement the next phase of an 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

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-tasks
description	Work on rdm tasks
allowed-tools	["Read","Bash","Glob","Grep","Write","Edit","EnterPlanMode","ExitPlanMode","mcp__rdm__rdm_task_list","mcp__rdm__rdm_task_show","mcp__rdm__rdm_task_update"]

Work on rdm tasks. $ARGUMENTS is an optional task slug.

Principles

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

Steps

List tasks: use the mcp__rdm__rdm_task_list tool with project: "fbm" to see open and in-progress tasks.
Show details: if a task slug was provided in $ARGUMENTS, use the mcp__rdm__rdm_task_show tool with project: "fbm" and task: <slug>. Otherwise, present the task list and ask the user which task to work on.
Mark in-progress: use the mcp__rdm__rdm_task_update tool with project: "fbm", task: <slug>, 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 task into concrete implementation steps based on the task description
- 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.
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: task/<slug> line in the commit message — the post-merge hook will mark the task done and record the commit SHA. Use the exact task slug from the rdm tools you used earlier — do NOT invent or paraphrase it. If the task is also part of a roadmap phase, include a Done: <roadmap-slug>/<phase-stem> line as well (using exact slugs/stems from rdm).