diff --git a/plugins/docks/skills/engineering/refactor/SKILL.md b/plugins/docks/skills/engineering/refactor/SKILL.md
index f001e266..56f1c073 100644
--- a/plugins/docks/skills/engineering/refactor/SKILL.md
+++ b/plugins/docks/skills/engineering/refactor/SKILL.md
@@ -5,7 +5,7 @@ user-invocable: true
 metadata:
   pattern: pipeline
   updated: "2026-08-25"
-  content_hash: "082d42dc672fe8b5374559ca3f13585651d9c603288a9705bf4f759f8d897eac"
+  content_hash: "f71d5e5486566c6703275bafa0a70364dfd7fb3d3f9558c5f41950f725a1a2dc"
 ---
 
 # Refactor (cross-tool pipeline)
@@ -74,8 +74,8 @@ Phase 3 uses Phase 2a's SAFE tier to skip files about to be deleted. Phase 4 mer
 ## The plan record (IPC + deliverable)
 
 ```text
-GitHub issue #<n> labeled plan plus exactly one lifecycle label:
-plan:drafting | plan:planned | plan:ongoing | plan:blocked
+GitHub issue #<n> labeled plan, created with plan:drafting;
+plan-manager owns every later phase transition.
 ```
 
 Hand phase output to `plan-manager` as you go — do not hold all of it in context and dump it at the end. Downstream phases and a resumed run read the issue with `plan.mjs show <issue> --body` and locate prior output by grepping the headings.
diff --git a/plugins/docks/skills/engineering/security/SKILL.md b/plugins/docks/skills/engineering/security/SKILL.md
index 0855f55f..7ecb3e88 100644
--- a/plugins/docks/skills/engineering/security/SKILL.md
+++ b/plugins/docks/skills/engineering/security/SKILL.md
@@ -5,7 +5,7 @@ user-invocable: true
 metadata:
   pattern: pipeline
   updated: "2026-08-25"
-  content_hash: "f108c4f561c1c05d73670783cdc425333b867e6cc64057289d7c85a8d7e290a7"
+  content_hash: "0bc63235cff0a0e7225217ea04e230e5c80e75bff547c967d92efb0957c7d681"
 ---
 
 # Security Audit (cross-tool pipeline)
@@ -75,8 +75,8 @@ Phases 2a–2c are independent lenses over the same Phase 1 map; run them sequen
 The plan issue holds the whole run. It doubles as inter-phase memory and the final artifact.
 
 ```text
-GitHub issue #<n> labeled plan plus exactly one lifecycle label:
-plan:drafting | plan:planned | plan:ongoing | plan:blocked
+GitHub issue #<n> labeled plan, created with plan:drafting;
+plan-manager owns every later phase transition.
 ```
 
 Hand phase output to `plan-manager` as you go — do not hold all of it in context and dump it at the end. The headings above are the contract; downstream phases and a resumed run read the issue with `plan.mjs show <issue> --body` and locate prior output by grepping for them.