diff --git a/plugins/os-sdlc/reference/pipeline-stages.md b/plugins/os-sdlc/reference/pipeline-stages.md
index 3f1443e..10e21c6 100644
--- a/plugins/os-sdlc/reference/pipeline-stages.md
+++ b/plugins/os-sdlc/reference/pipeline-stages.md
@@ -64,8 +64,11 @@ per-example granularity was a DeltaRefinery downside being deliberately dropped.
   cc-os naming convention before anything ships.
 - Whether a cheap tests-vs-spec review should run *before* the programmer stage in later
   versions, to catch misaligned tests before paying for implementation.
-- Whether Pocock's `implement` skill is adopted as a thin router over these stages, or
-  redesigned from scratch.
+- Shape settled 2026-07-16: `/implement` (or our custom successor) is a *skill acting as
+  orchestrator* — slash commands are the user-invocable layer, agents aren't. The skill
+  triggers the agent pipeline, watches over it, adjusts to surprises, and keeps the user
+  in the loop on progress/results. Remaining question: how much of Pocock's `implement`
+  wording survives vs. a from-scratch orchestrator prompt.
 
 ## Sources