diff --git a/agents/connector.md b/agents/connector.md
index 8475a57..afaaa93 100644
--- a/agents/connector.md
+++ b/agents/connector.md
@@ -57,6 +57,29 @@ When you detect work that another agent should handle, include a `### Suggested
 For the full orchestration protocol, see `.claude/references/agent-orchestration.md`.
 For the agent registry, see `.claude/references/agents-registry.md`.
 
+### When to suggest a new agent
+
+If you detect that the user needs functionality that NO existing agent provides, include a `### Suggested new agent` section in your output. The dispatcher will consider invoking the Architect to create a custom agent.
+
+**When to signal this:**
+- The user repeatedly asks for something outside any agent's capabilities
+- The task requires a specialized workflow that none of the current agents handle
+- The user explicitly says they wish an agent existed for a specific purpose
+
+**Output format:**
+
+```markdown
+### Suggested new agent
+- **Need**: {what capability is missing}
+- **Reason**: {why no existing agent can handle this}
+- **Suggested role**: {brief description of what the new agent would do}
+```
+
+**Do NOT suggest a new agent when:**
+- An existing agent can handle the task (even imperfectly)
+- The user is asking something outside the vault's scope entirely
+- The task is a one-off that does not warrant a dedicated agent
+
 ---
 
 ## Analysis Modes
diff --git a/agents/librarian.md b/agents/librarian.md
index 5972bbd..4d8cb98 100644
--- a/agents/librarian.md
+++ b/agents/librarian.md
@@ -63,6 +63,29 @@ If the vault still has a `Meta/agent-messages.md` file from the old messaging sy
 For the full orchestration protocol, see `.claude/references/agent-orchestration.md`.
 For the agent registry, see `.claude/references/agents-registry.md`.
 
+### When to suggest a new agent
+
+If you detect that the user needs functionality that NO existing agent provides, include a `### Suggested new agent` section in your output. The dispatcher will consider invoking the Architect to create a custom agent.
+
+**When to signal this:**
+- The user repeatedly asks for something outside any agent's capabilities
+- The task requires a specialized workflow that none of the current agents handle
+- The user explicitly says they wish an agent existed for a specific purpose
+
+**Output format:**
+
+```markdown
+### Suggested new agent
+- **Need**: {what capability is missing}
+- **Reason**: {why no existing agent can handle this}
+- **Suggested role**: {brief description of what the new agent would do}
+```
+
+**Do NOT suggest a new agent when:**
+- An existing agent can handle the task (even imperfectly)
+- The user is asking something outside the vault's scope entirely
+- The task is a one-off that does not warrant a dedicated agent
+
 ---
 
 ## Audit Modes
diff --git a/agents/postman.md b/agents/postman.md
index 82d310b..60fc2a6 100644
--- a/agents/postman.md
+++ b/agents/postman.md
@@ -67,6 +67,29 @@ When you detect work that another agent should handle, include a `### Suggested
 For the full orchestration protocol, see `.claude/references/agent-orchestration.md`.
 For the agent registry, see `.claude/references/agents-registry.md`.
 
+### When to suggest a new agent
+
+If you detect that the user needs functionality that NO existing agent provides, include a `### Suggested new agent` section in your output. The dispatcher will consider invoking the Architect to create a custom agent.
+
+**When to signal this:**
+- The user repeatedly asks for something outside any agent's capabilities
+- The task requires a specialized workflow that none of the current agents handle
+- The user explicitly says they wish an agent existed for a specific purpose
+
+**Output format:**
+
+```markdown
+### Suggested new agent
+- **Need**: {what capability is missing}
+- **Reason**: {why no existing agent can handle this}
+- **Suggested role**: {brief description of what the new agent would do}
+```
+
+**Do NOT suggest a new agent when:**
+- An existing agent can handle the task (even imperfectly)
+- The user is asking something outside the vault's scope entirely
+- The task is a one-off that does not warrant a dedicated agent
+
 ---
 
 ## Philosophy
diff --git a/agents/scribe.md b/agents/scribe.md
index 7eff0fb..5975833 100644
--- a/agents/scribe.md
+++ b/agents/scribe.md
@@ -58,6 +58,29 @@ When you detect work that another agent should handle, include a `### Suggested
 For the full orchestration protocol, see `.claude/references/agent-orchestration.md`.
 For the agent registry, see `.claude/references/agents-registry.md`.
 
+### When to suggest a new agent
+
+If you detect that the user needs functionality that NO existing agent provides, include a `### Suggested new agent` section in your output. The dispatcher will consider invoking the Architect to create a custom agent.
+
+**When to signal this:**
+- The user repeatedly asks for something outside any agent's capabilities
+- The task requires a specialized workflow that none of the current agents handle
+- The user explicitly says they wish an agent existed for a specific purpose
+
+**Output format:**
+
+```markdown
+### Suggested new agent
+- **Need**: {what capability is missing}
+- **Reason**: {why no existing agent can handle this}
+- **Suggested role**: {brief description of what the new agent would do}
+```
+
+**Do NOT suggest a new agent when:**
+- An existing agent can handle the task (even imperfectly)
+- The user is asking something outside the vault's scope entirely
+- The task is a one-off that does not warrant a dedicated agent
+
 ---
 
 ## Core Philosophy
diff --git a/agents/seeker.md b/agents/seeker.md
index 5d94d8d..5cffce6 100644
--- a/agents/seeker.md
+++ b/agents/seeker.md
@@ -59,6 +59,29 @@ The Seeker is often the agent that discovers unexpected things while searching.
 For the full orchestration protocol, see `.claude/references/agent-orchestration.md`.
 For the agent registry, see `.claude/references/agents-registry.md`.
 
+### When to suggest a new agent
+
+If you detect that the user needs functionality that NO existing agent provides, include a `### Suggested new agent` section in your output. The dispatcher will consider invoking the Architect to create a custom agent.
+
+**When to signal this:**
+- The user repeatedly asks for something outside any agent's capabilities
+- The task requires a specialized workflow that none of the current agents handle
+- The user explicitly says they wish an agent existed for a specific purpose
+
+**Output format:**
+
+```markdown
+### Suggested new agent
+- **Need**: {what capability is missing}
+- **Reason**: {why no existing agent can handle this}
+- **Suggested role**: {brief description of what the new agent would do}
+```
+
+**Do NOT suggest a new agent when:**
+- An existing agent can handle the task (even imperfectly)
+- The user is asking something outside the vault's scope entirely
+- The task is a one-off that does not warrant a dedicated agent
+
 ---
 
 ## Search & Retrieval Modes
diff --git a/agents/sorter.md b/agents/sorter.md
index 3cc5fb8..d5af6ff 100644
--- a/agents/sorter.md
+++ b/agents/sorter.md
@@ -58,6 +58,29 @@ Always include your proposed solution and what you did in the meantime. Then **c
 For the full orchestration protocol, see `.claude/references/agent-orchestration.md`.
 For the agent registry, see `.claude/references/agents-registry.md`.
 
+### When to suggest a new agent
+
+If you detect that the user needs functionality that NO existing agent provides, include a `### Suggested new agent` section in your output. The dispatcher will consider invoking the Architect to create a custom agent.
+
+**When to signal this:**
+- The user repeatedly asks for something outside any agent's capabilities
+- The task requires a specialized workflow that none of the current agents handle
+- The user explicitly says they wish an agent existed for a specific purpose
+
+**Output format:**
+
+```markdown
+### Suggested new agent
+- **Need**: {what capability is missing}
+- **Reason**: {why no existing agent can handle this}
+- **Suggested role**: {brief description of what the new agent would do}
+```
+
+**Do NOT suggest a new agent when:**
+- An existing agent can handle the task (even imperfectly)
+- The user is asking something outside the vault's scope entirely
+- The task is a one-off that does not warrant a dedicated agent
+
 ---
 
 ## Triage Modes
diff --git a/agents/transcriber.md b/agents/transcriber.md
index 11429c3..030c1b4 100644
--- a/agents/transcriber.md
+++ b/agents/transcriber.md
@@ -60,6 +60,29 @@ When you detect work that another agent should handle, include a `### Suggested
 For the full orchestration protocol, see `.claude/references/agent-orchestration.md`.
 For the agent registry, see `.claude/references/agents-registry.md`.
 
+### When to suggest a new agent
+
+If you detect that the user needs functionality that NO existing agent provides, include a `### Suggested new agent` section in your output. The dispatcher will consider invoking the Architect to create a custom agent.
+
+**When to signal this:**
+- The user repeatedly asks for something outside any agent's capabilities
+- The task requires a specialized workflow that none of the current agents handle
+- The user explicitly says they wish an agent existed for a specific purpose
+
+**Output format:**
+
+```markdown
+### Suggested new agent
+- **Need**: {what capability is missing}
+- **Reason**: {why no existing agent can handle this}
+- **Suggested role**: {brief description of what the new agent would do}
+```
+
+**Do NOT suggest a new agent when:**
+- An existing agent can handle the task (even imperfectly)
+- The user is asking something outside the vault's scope entirely
+- The task is a one-off that does not warrant a dedicated agent
+
 ---
 
 ## Intake Interview