From rdr
Use to implement a locked (Final) RDR into working, spec-verified code (e.g. "implement RDR 45", "$rdr-implement 0045" in Codex, "/rdr-implement 0045" in Claude). Runs Stage 8 of the RDR flow — dispatches into prompts/implementation/launch.md as the orchestrator. Re-entrant across days from status.md. Terminates at COMPLETE/INCOMPLETE; a contract-level spec defect routes back to the RDR, never patches the code. Pairs with $rdr-finalize in Codex or /rdr-finalize in Claude (must precede it). Also exposes `--launch-prompt-path` so wrappers get the orchestrator prompt's location from the engine instead of reconstructing its internal layout.
How this skill is triggered — by the user, by Claude, or both
Slash command
/rdr:rdr-implementThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Turn the locked RDR into working, spec-verified code — the flow's true terminus.
Turn the locked RDR into working, spec-verified code — the flow's true terminus.
Implementation is the last filter: tests built from the spec prove the design holds,
or surface the contract defect that sends it back. Dispatches into the
orchestrator prompt launch.md — it does not redefine
it. The orchestrator never reads the RDR, source, or test files; phase sub-agents
do. Do not loosen those orchestrator rules.
Codex: $rdr-implement <NNNN>
Claude: /rdr-implement <NNNN>
Codex: $rdr-implement --launch-prompt-path # print the orchestrator prompt path, then stop
Claude: /rdr-implement --launch-prompt-path # print the orchestrator prompt path, then stop
--launch-prompt-path — the prompt-location contract (query mode)A consumer that orchestrates Stage 8 itself (e.g. /rdr-implement-triage) needs
launch.md's location but must not hardcode the engine's internal layout.
This flag is that contract: the engine owns where its prompt lives and reports it.
Short-circuit — run only rdr-common §seam-bind, then print and stop. Take
no RDR argument; run none of the entry-contract gates below (no Final /
predecessor / resume checks — nothing is implemented):
# §seam-bind has bound $RDR_HOME (fast path or resolver — see rdr-common)
echo "$RDR_HOME/prompts/implementation/launch.md"
That canonical path is stable even though this skill references launch.md as a
sibling symlink. The prompt body still carries {RDR_PATH} / {RDR_RESOURCES}
placeholders — the caller fills them per run. If $RDR_HOME is unbound
(stale marker) → stopped:no-rdr-flow-home (/rdr-init to refresh).
Refuse with the named code if any is false (the RDR is not ready — return to
/rdr-finalize or /rdr-reconcile):
stopped:not-final).REQ-MVV (stopped:mvv-deferred).**Predecessors**: entry's
{ARTIFACT_DIR}/status.md reads COMPLETE (stopped:predecessor-incomplete:<id>).rdr-common.md; run §seam-bind + §rdr-resolve
to bind $RDR_RESOURCES, RDR_PATH, {ARTIFACT_DIR} (= <RDR_RECORDS>/<RDR_SLUG>/artifacts/).{ARTIFACT_DIR}/status.md; if it names a phase, resume at the next one. A reader
returning days later runs the same skill against the same RDR — the on-disk
artifacts, not the session, carry state. If status.md already reads
COMPLETE, do not re-run — report it (the flow is done; point at Close /
post-mortem) rather than re-implementing a finished RDR (stopped:already-complete).launch.md
with {RDR_PATH} / {RDR_RESOURCES} filled; it writes the artifacts under
{ARTIFACT_DIR} (req-list.md, coverage.md, verification.md,
deviations.md, status.md).status.md == COMPLETE — every REQ-N has ≥1 green test, no coverage orphans,
REQ-MVV output recorded, no open needs-author-decision deviations. → Close:
set the RDR's terminal status and write the post-mortem
(post-mortem/).status.md == INCOMPLETE — it names the blocker. A precondition failure is a
halt: fix the named condition and re-run; resume picks up at the next phase.SPEC-DEFECT, or an unresolvable SPEC-UNDER) —
the locked RDR is wrong. Do not edit the RDR or patch the code. Abandon
implementation and re-enter the flow at the stage the defect dictates
(/rdr-propose / /rdr-refine / /rdr-resolve), re-lock via /rdr-finalize,
then re-run this. The flow's only backward edge out of Final, and it is deliberate.<slug>/{req-list,coverage,verification,deviations,status}.md),
if autocommit is on. Code commits stay with the orchestrator's feat(...) contract — §commit never touches source./rdr-implement NNNN./rdr-status NNNN to re-orient.Creates bite-sized, testable implementation plans from specs or requirements, with file structure and task decomposition. Activates before coding multi-step tasks.
npx claudepluginhub cwensel/rdr --plugin rdr