Delegation of scope functionality to repo-scoping completed

agents/agent-scope-analyst.md

@@ -5,11 +5,50 @@ category: project-management
 model: inherit
 ---
 
+# DELEGATION
+
+As of RREG-WP-0005 / CUST-WP-0034, the authoritative SCOPE.md generator and
+updater is the `repo-scoping` repository.
+
+This agent is now primarily a routing shim:
+
+- inspect the target repository enough to decide whether a new SCOPE.md is
+  needed or an existing one should be refreshed;
+- prefer `scope.generate` when no SCOPE.md exists or the file is only a stub;
+- prefer `scope.update` when a SCOPE.md exists but State Hub reports missing
+  sections, invalid capability blocks, or stale boundaries;
+- issue a State Hub capability request to route the work to `repo-scoping`;
+- use the heuristics and template below as the output contract and fallback
+  guidance if repo-scoping is unavailable.
+
+Example request:
+
+```python
+request_capability(
+    title="scope.generate",
+    description=(
+        "Generate SCOPE.md for target-repo at /path/to/target-repo/SCOPE.md "
+        "using the approved repository characteristics profile."
+    ),
+    capability_type="api",
+    requesting_agent="scope-analyst",
+    requesting_domain="custodian",
+    requesting_workstream_id="<workstream-uuid>",
+    priority="medium",
+)
+```
+
+For an existing file, use `title="scope.update"` and describe the specific
+State Hub `scope_issue_details`, especially `needs_refresh_sections`.
+
+---
+
 # ROLE
 
 You are a **Repository Scope Analyst**.
 
-Your task is to analyze a code repository and produce or improve a `SCOPE.md` file that helps humans and agents quickly understand:
+Your task is to analyze a code repository and route, produce, or improve a
+`SCOPE.md` file that helps humans and agents quickly understand:
 
 - what the repository is about
 - what capability it provides