Problem
b0d5d0a absorbed rpi-design into RAD as /rad-research + /rad-design, but .claude/skills/rpi-design/ is still present on main and develop:
.claude/skills/rpi-design/SKILL.md
.claude/skills/rpi-design/phases/01-research.md
.claude/skills/rpi-design/phases/02-plan.md
.claude/skills/rpi-design/phases/03-implement.md
.claude/skills/rpi-design/templates/compaction-template.md
.claude/skills/rpi-design/templates/diagram-template.md
.claude/skills/rpi-design/templates/readme-template.md
A live skill whose description matches "design an agent architecture / scaffold a multi-agent workflow" competes with /rad-design for invocation, and its 03-implement.md phase describes an execution path that does not go through RAD's Gate 2. That is a correctness risk, not just clutter: a skill that can be auto-invoked and that describes implementing without an approved plan is exactly what the deliver gate exists to prevent.
.claude/skills/kickoff/ and .claude/skills/wrap/ should be audited in the same pass — confirm they are still live and still consistent with the current command set, or remove them.
Evidence / framing
HumanLayer's Skill Issue: Harness Engineering for Coding Agents names this failure mode directly: installing skills and servers speculatively and never paring them back, so every session pays context for capability nobody uses. Their "what did work" list is the inverse — carefully paring down exposed capabilities once needs are identified.
RAD is shipping this failure mode in its own tree, and every install inherits it.
Scope
- Remove
.claude/skills/rpi-design/ (salvage anything from templates/ that /rad-design should own before deleting).
- Audit
kickoff and wrap; keep, fix, or remove.
- Check
install.sh and INSTALL.md do not reference the removed paths.
- Check docs for stale rpi-design references.
Related
Problem
b0d5d0aabsorbed rpi-design into RAD as/rad-research+/rad-design, but.claude/skills/rpi-design/is still present onmainanddevelop:A live skill whose description matches "design an agent architecture / scaffold a multi-agent workflow" competes with
/rad-designfor invocation, and its03-implement.mdphase describes an execution path that does not go through RAD's Gate 2. That is a correctness risk, not just clutter: a skill that can be auto-invoked and that describes implementing without an approved plan is exactly what the deliver gate exists to prevent..claude/skills/kickoff/and.claude/skills/wrap/should be audited in the same pass — confirm they are still live and still consistent with the current command set, or remove them.Evidence / framing
HumanLayer's Skill Issue: Harness Engineering for Coding Agents names this failure mode directly: installing skills and servers speculatively and never paring them back, so every session pays context for capability nobody uses. Their "what did work" list is the inverse — carefully paring down exposed capabilities once needs are identified.
RAD is shipping this failure mode in its own tree, and every install inherits it.
Scope
.claude/skills/rpi-design/(salvage anything fromtemplates/that/rad-designshould own before deleting).kickoffandwrap; keep, fix, or remove.install.shandINSTALL.mddo not reference the removed paths.Related