Search for related/duplicate issues before creating a new issue

.changeset/search-related-issues.md

@@ -0,0 +1,5 @@
+---
+"@automattic/radical-pipelines": patch
+---
+
+Before creating an issue, the orchestrator searches the tracker for related or duplicate issues and presents them with the draft so the owner can proceed, modify the existing issue, or link it.

skills/radical-pipelines/reference/manage-issues.md

@@ -40,7 +40,11 @@ Make a single open invitation for anything else worth telling the agents — a h
 
 When the owner offers a direction or belief, record it under Assumptions and say so plainly — for example: "I'll note that as something to explore, not a requirement; the agents may confirm or revise it." This keeps the issue as the owner's _best current understanding, not ground truth_: downstream phases must either satisfy the stated intent or surface evidence that a premise is false, never silently substitute a different goal.
 
-### 5. Draft, confirm, write
+### 5. Search for related issues
+
+When creating, search the tracker (through the **Issues** convention) for existing issues related to the draft's goal, and present any matches alongside the draft — distinguishing possible duplicates from issues worth linking. The owner decides: proceed, modify the existing issue instead, or link the related issue in the draft's Context.
+
+### 6. Draft, confirm, write
 
 Render the issue in the format above (omitting empty sections) and show it to the owner. On approval, create the new issue — or apply the modification — through the **Issues** convention.