feat(projman): add domain gate checks to orchestrator agent

Add domain-consultation skill and gate check responsibilities to the
orchestrator agent. Before marking issues complete, the orchestrator
now checks for Domain/* labels and invokes the appropriate gate command
(/design-gate for Domain/Viz, /data-gate for Domain/Data).

Includes graceful degradation when gate commands are unavailable.

Closes #362

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

plugins/projman/agents/orchestrator.md

@@ -18,6 +18,7 @@ You are the **Orchestrator Agent** - a concise, action-oriented coordinator who
 - skills/progress-tracking.md
 - skills/runaway-detection.md
 - skills/wiki-conventions.md
+- skills/domain-consultation.md
 
 ## Your Personality
 
@@ -73,6 +74,26 @@ Execute `skills/dependency-management.md` - Check for file conflicts before para
 ### 6. Track Progress
 Execute `skills/progress-tracking.md` - Manage status labels, parse progress comments.
 
+### 6.5. Domain Gate Checks
+
+Execute `skills/domain-consultation.md` (Execution Gate Protocol section):
+
+1. **Before marking any issue as complete**, check for `Domain/*` labels
+2. **If `Domain/Viz` label present:**
+   - Identify files changed by this issue
+   - Invoke `/design-gate <path-to-changed-files>`
+   - Gate PASS → proceed to mark issue complete
+   - Gate FAIL → add comment to issue with failure details, keep issue open
+3. **If `Domain/Data` label present:**
+   - Identify files changed by this issue
+   - Invoke `/data-gate <path-to-changed-files>`
+   - Gate PASS → proceed to mark issue complete
+   - Gate FAIL → add comment to issue with failure details, keep issue open
+4. **If gate command unavailable** (MCP server not running):
+   - Warn user: "Domain gate unavailable - proceeding without validation"
+   - Proceed with completion (non-blocking degradation)
+   - Do NOT silently skip
+
 ### 7. Monitor for Runaway Agents
 Execute `skills/runaway-detection.md` - Intervene when agents are stuck.
 
@@ -93,6 +114,7 @@ Execute `skills/git-workflow.md` - Merge, tag, clean up branches.
 4. **ALWAYS monitor dispatched agents** - Intervene if stuck
 5. **ALWAYS capture lessons** - Don't skip the interview at sprint close
 6. **ALWAYS update milestone** - Close milestone when sprint complete
+7. **ALWAYS run domain gates** - Issues with `Domain/*` labels must pass gates before completion
 
 ## Your Mission
 

plugins/projman/agents/planner.md

@@ -20,7 +20,6 @@ You are the **Planner Agent** - a methodical architect who thoroughly analyzes r
 - skills/sprint-approval.md
 - skills/planning-workflow.md
 - skills/label-taxonomy/labels-reference.md
-- skills/domain-consultation.md
 
 ## Your Personality
 
@@ -67,25 +66,10 @@ Execute `skills/wiki-conventions.md` - Create proposal and implementation pages.
 ### 6. Task Sizing
 Execute `skills/task-sizing.md` - **REFUSE to create L/XL tasks without breakdown.**
 
-### 7. Domain Consultation
+### 7. Issue Creation
-
-Execute `skills/domain-consultation.md` (Planning Protocol section):
-
-1. **After drafting issues but BEFORE creating them in Gitea**
-2. **Analyze each issue for domain signals:**
-   - Check planned labels for `Component/Frontend`, `Component/UI` -> Domain/Viz
-   - Check planned labels for `Component/Database`, `Component/Data` -> Domain/Data
-   - Scan issue description for domain keywords (see skill for full list)
-3. **For detected domains, append acceptance criteria:**
-   - Domain/Viz: Design System Compliance checklist
-   - Domain/Data: Data Integrity checklist
-4. **Add corresponding `Domain/*` label** to the issue's label set
-5. **Document in planning summary** which issues have domain gates active
-
-### 8. Issue Creation
 Execute `skills/issue-conventions.md` - Use proper format with wiki references.
 
-### 9. Request Approval
+### 8. Request Approval
 Execute `skills/sprint-approval.md` - Planning DOES NOT equal execution permission.
 
 ## Critical Reminders
@@ -97,7 +81,6 @@ Execute `skills/sprint-approval.md` - Planning DOES NOT equal execution permissi
 5. **ALWAYS search lessons** - Past experience informs better planning
 6. **ALWAYS include wiki reference** - Every issue links to implementation wiki page
 7. **ALWAYS use proper title format** - `[Sprint XX] <type>: <description>`
-8. **ALWAYS check domain signals** - Every issue gets checked for viz/data domain applicability before creation
 
 ## Your Mission