diff --git a/server/src/routes/access.ts b/server/src/routes/access.ts
index 908fc104ba3..73516c2855c 100644
--- a/server/src/routes/access.ts
+++ b/server/src/routes/access.ts
@@ -141,7 +141,7 @@ function readSkillMarkdown(skillName: string): string | null {
     normalized !== "paperclip" &&
     normalized !== "paperclip-create-agent" &&
     normalized !== "paperclip-create-plugin" &&
-    normalized !== "paperclip-plan" &&
+    normalized !== "paperclip-converting-plans-to-tasks" &&
     normalized !== "para-memory-files"
   )
     return null;
@@ -2865,8 +2865,8 @@ export function accessRoutes(
           path: "/api/skills/paperclip-create-agent"
         },
         {
-          name: "paperclip-plan",
-          path: "/api/skills/paperclip-plan"
+          name: "paperclip-converting-plans-to-tasks",
+          path: "/api/skills/paperclip-converting-plans-to-tasks"
         }
       ]
     });
diff --git a/skills/paperclip-plan/SKILL.md b/skills/paperclip-converting-plans-to-tasks/SKILL.md
similarity index 77%
rename from skills/paperclip-plan/SKILL.md
rename to skills/paperclip-converting-plans-to-tasks/SKILL.md
index 068e90f50ac..6b95b4d1665 100644
--- a/skills/paperclip-plan/SKILL.md
+++ b/skills/paperclip-converting-plans-to-tasks/SKILL.md
@@ -1,16 +1,18 @@
 ---
-name: paperclip-plan
+name: paperclip-converting-plans-to-tasks
 description: >
-  The Paperclip way of planning. Use whenever you are asked to plan, scope, or
-  break down work inside a Paperclip company. Industry-agnostic guidance on how
-  to plan so that Paperclip's executor can pick up the work — it does not
-  prescribe a plan format. Pair with the `paperclip` skill, which covers the
-  mechanics of writing the plan document and reassigning the issue.
+  The Paperclip way of converting a plan into executable tasks. Use whenever
+  you are asked to plan, scope, or break down work inside a Paperclip company.
+  Industry-agnostic guidance on how to translate a plan into assigned issues
+  with the right specialty, dependencies, and parallelization so Paperclip's
+  executor can pick up the work — it does not prescribe a plan format. Pair
+  with the `paperclip` skill, which covers the mechanics of writing the plan
+  document and reassigning the issue.
 ---
 
-# Paperclip Plan
+# Paperclip — Converting Plans to Tasks
 
-A companion skill for planning. It does **not** dictate a plan structure — bring whatever format fits the work and the user's preference. It tells you _how_ to plan so that the rest of Paperclip works for you.
+A companion skill for turning a plan into executable Paperclip work. It does **not** dictate a plan structure — bring whatever format fits the work and the user's preference. It tells you _how_ to translate that plan into issues so that the rest of Paperclip works for you.
 
 For the **mechanics** of recording a plan (issue document with key `plan`, comment links, approval gating, who to reassign back to), follow the _Planning_ section of the `paperclip` skill. This skill covers planning method, not the API surface.
 
diff --git a/skills/paperclip/SKILL.md b/skills/paperclip/SKILL.md
index 4a3c06de777..94f55f9f77d 100644
--- a/skills/paperclip/SKILL.md
+++ b/skills/paperclip/SKILL.md
@@ -276,8 +276,6 @@ Submitted CTO hire request and linked it for board review.
 
 ## Planning (Required when planning requested)
 
-For _how_ to plan — depth, assignment, dependencies, parallelization — use the companion skill `paperclip-plan`. The rest of this section covers only the mechanics.
-
 If you're asked to make a plan, create or update the issue document with key `plan`. Do not append plans into the issue description anymore. If you're asked for plan revisions, update that same `plan` document. In both cases, leave a comment as you normally would and mention that you updated the plan document. Plans-as-issue-documents is the norm: don't make plans as files in the repo unless you're specifically asked.
 
 When you mention a plan or another issue document in a comment, include a direct document link using the key:
@@ -291,6 +289,8 @@ If you're asked to make a plan, _do not mark the issue as done_. Re-assign the i
 
 If the plan needs explicit approval before implementation, update the `plan` document, create a `request_confirmation` issue-thread interaction bound to the latest plan revision, and wait for acceptance before creating implementation subtasks. See `references/api-reference.md` for the interaction payload.
 
+When asked to convert a plan into executable Paperclip tasks — depth, assignment, dependencies, parallelization — use the companion skill `paperclip-converting-plans-to-tasks`.
+
 Recommended API flow:
 
 ```bash