@cubis/foundry 0.3.76 → 0.3.77

package/workflows/skills/generated/skill-catalog.json

@@ -2,10 +2,10 @@
   "$schema": "cubis-foundry-skill-catalog-v1",
   "generatedAt": "1970-01-01T00:00:00.000Z",
   "summary": {
-    "totalEntries": 68,
-    "totalSkills": 68,
+    "totalEntries": 69,
+    "totalSkills": 69,
     "totalSubskills": 0,
-    "canonicalSkills": 68,
+    "canonicalSkills": 69,
     "compatibilityAliases": 0,
     "layers": [
       "core-operating",
@@ -220,6 +220,38 @@
         "databases"
       ]
     },
+    {
+      "id": "deep-research",
+      "package_id": "deep-research",
+      "catalog_id": "deep-research",
+      "kind": "skill",
+      "path": "workflows/skills/deep-research/SKILL.md",
+      "name": "deep-research",
+      "description": "Use when investigating latest vendor behavior, comparing tools or platforms, verifying claims beyond the repo, or gathering external evidence before implementation.",
+      "canonical": true,
+      "canonical_id": "deep-research",
+      "deprecated": false,
+      "replaced_by": null,
+      "aliases": [],
+      "category": "core-operating",
+      "layer": "core-operating",
+      "maturity": "incubating",
+      "tier": "experimental",
+      "tags": [
+        "core-operating",
+        "deep",
+        "deep research",
+        "deep-research",
+        "research"
+      ],
+      "triggers": [
+        "deep-research",
+        "deep research",
+        "deep",
+        "research",
+        "core-operating"
+      ]
+    },
     {
       "id": "django-drf",
       "package_id": "django-drf",
@@ -2141,5 +2173,5 @@
       ]
     }
   ],
-  "contentHash": "e308bfb0084478a8"
+  "contentHash": "b27e549d17f95efb"
 }

package/workflows/skills/skills_index.json

@@ -193,6 +193,38 @@
       "databases"
     ]
   },
+  {
+    "id": "deep-research",
+    "package_id": "deep-research",
+    "catalog_id": "deep-research",
+    "kind": "skill",
+    "name": "deep-research",
+    "canonical": true,
+    "canonical_id": "deep-research",
+    "deprecated": false,
+    "replaced_by": null,
+    "aliases": [],
+    "category": "core-operating",
+    "layer": "core-operating",
+    "maturity": "incubating",
+    "tier": "experimental",
+    "tags": [
+      "core-operating",
+      "deep",
+      "deep research",
+      "deep-research",
+      "research"
+    ],
+    "path": ".agents/skills/deep-research/SKILL.md",
+    "description": "Use when investigating latest vendor behavior, comparing tools or platforms, verifying claims beyond the repo, or gathering external evidence before implementation.",
+    "triggers": [
+      "deep-research",
+      "deep research",
+      "deep",
+      "research",
+      "core-operating"
+    ]
+  },
   {
     "id": "django-drf",
     "package_id": "django-drf",

package/workflows/workflows/agent-environment-setup/generated/route-manifest.json

@@ -1,7 +1,7 @@
 {
   "$schema": "cubis-foundry-route-manifest-v1",
   "generatedAt": "1970-01-01T00:00:00.000Z",
-  "contentHash": "9aedd9bfd58f1f59",
+  "contentHash": "47cf8920e99d0258",
   "summary": {
     "totalRoutes": 40,
     "workflows": 18,
@@ -498,7 +498,7 @@
       ],
       "supportingSkills": [
         "database-design",
-        "architecture-doc",
+        "deep-research",
         "mcp-server-builder",
         "tech-doc",
         "prompt-engineering",
@@ -701,7 +701,7 @@
       ],
       "supportingSkills": [
         "database-design",
-        "architecture-doc",
+        "deep-research",
         "mcp-server-builder",
         "tech-doc",
         "prompt-engineering",
@@ -804,7 +804,7 @@
       "primaryAgent": "researcher",
       "supportingAgents": [],
       "primarySkills": [
-        "architecture-doc",
+        "deep-research",
         "system-design"
       ],
       "supportingSkills": [
@@ -1694,7 +1694,7 @@
         "frontend-specialist"
       ],
       "primarySkills": [
-        "architecture-doc",
+        "deep-research",
         "system-design"
       ],
       "supportingSkills": [
@@ -1756,7 +1756,7 @@
       ],
       "supportingSkills": [
         "database-design",
-        "architecture-doc",
+        "deep-research",
         "mcp-server-builder",
         "tech-doc",
         "prompt-engineering",
@@ -1815,7 +1815,7 @@
       ],
       "supportingSkills": [
         "database-design",
-        "architecture-doc",
+        "deep-research",
         "mcp-server-builder",
         "tech-doc",
         "prompt-engineering",

package/workflows/workflows/agent-environment-setup/manifest.json

@@ -1,6 +1,6 @@
 {
   "id": "agent-environment-setup",
-  "version": "1.4.0",
+  "version": "1.5.0",
   "description": "Workflow-first AI agent environment setup for Antigravity, Codex, Copilot, Claude Code, and Gemini CLI.",
   "platforms": {
     "antigravity": {
@@ -55,6 +55,7 @@
         "code-review",
         "csharp-best-practices",
         "database-design",
+        "deep-research",
         "django-drf",
         "docker-compose-dev",
         "drizzle-orm",
@@ -199,6 +200,7 @@
         "code-review",
         "csharp-best-practices",
         "database-design",
+        "deep-research",
         "django-drf",
         "docker-compose-dev",
         "drizzle-orm",
@@ -323,6 +325,7 @@
         "code-review",
         "csharp-best-practices",
         "database-design",
+        "deep-research",
         "django-drf",
         "docker-compose-dev",
         "drizzle-orm",
@@ -467,6 +470,7 @@
         "code-review",
         "csharp-best-practices",
         "database-design",
+        "deep-research",
         "django-drf",
         "docker-compose-dev",
         "drizzle-orm",
@@ -536,6 +540,27 @@
           "type": "conductor-reference",
           "optional": true,
           "description": "If Conductor artifacts exist, workflows can reference them as supporting context."
+        },
+        {
+          "type": "template",
+          "event": "UserPromptSubmit",
+          "file": "README.md",
+          "optional": true,
+          "description": "Usage guide for the Claude route/research hook templates."
+        },
+        {
+          "type": "template",
+          "event": "UserPromptSubmit",
+          "file": "settings.snippet.json",
+          "optional": true,
+          "description": "Settings snippet that wires the route/research reminder hook into Claude Code."
+        },
+        {
+          "type": "template",
+          "event": "UserPromptSubmit",
+          "file": "route-research-guard.mjs",
+          "optional": true,
+          "description": "Hook script template that reinforces explicit-route honoring and research escalation."
         }
       ]
     },
@@ -568,6 +593,7 @@
         "code-review",
         "csharp-best-practices",
         "database-design",
+        "deep-research",
         "django-drf",
         "docker-compose-dev",
         "drizzle-orm",

package/workflows/workflows/agent-environment-setup/platforms/antigravity/agents/orchestrator.md

@@ -5,7 +5,7 @@ tools: Read, Grep, Glob, Bash, Write, Edit
 model: inherit
 maxTurns: 30
 memory: project
-skills: system-design, api-design, database-design, architecture-doc, mcp-server-builder, tech-doc, prompt-engineering, skill-creator, typescript-best-practices, javascript-best-practices, python-best-practices
+skills: system-design, api-design, database-design, deep-research, mcp-server-builder, tech-doc, prompt-engineering, skill-creator, typescript-best-practices, javascript-best-practices, python-best-practices
 handoffs:
   - agent: "validator"
     title: "Validate Results"
@@ -31,8 +31,8 @@ Your only permitted actions:
 
 ## Skill Loading Contract
 
-- Do not call `skill_search` for `system-design`, `api-design`, `database-design`, `architecture-doc`, `mcp-server-builder`, `tech-doc`, `prompt-engineering`, or `skill-creator` when the task is clearly multi-stream coordination, planning, architecture design, contract design, research, or skill package work.
-- Use `system-design` when the coordination problem is really a design tradeoff problem, `api-design` when integration contracts are the coordination bottleneck, `database-design` when the shared dependency is a data-model or migration concern, `architecture-doc` when the coordination risk is stale or conflicting external information, `mcp-server-builder` for MCP-specific streams, `tech-doc` for OpenAI-doc verification streams, `prompt-engineering` for instruction-quality streams, and `skill-creator` when the coordinated changes are in skills, mirrors, routing, or packaging.
+- Do not call `skill_search` for `system-design`, `api-design`, `database-design`, `deep-research`, `mcp-server-builder`, `tech-doc`, `prompt-engineering`, or `skill-creator` when the task is clearly multi-stream coordination, planning, architecture design, contract design, research, or skill package work.
+- Use `system-design` when the coordination problem is really a design tradeoff problem, `api-design` when integration contracts are the coordination bottleneck, `database-design` when the shared dependency is a data-model or migration concern, `deep-research` when the coordination risk is stale or conflicting external information, `mcp-server-builder` for MCP-specific streams, `tech-doc` for OpenAI-doc verification streams, `prompt-engineering` for instruction-quality streams, and `skill-creator` when the coordinated changes are in skills, mirrors, routing, or packaging.
 - Prefer platform-native delegation features when available, but keep the orchestration contract stable even when execution stays in a single track.
 - Use `skill_validate` before `skill_get`, and use `skill_get_reference` only for the specific sidecar file needed by the current coordination step.
 
@@ -45,7 +45,7 @@ Load on demand. Do not preload all references.
 | `system-design` | Coordination depends on resolving system design or interface tradeoffs first.                             |
 | `api-design`          | The critical shared dependency is an API contract or integration boundary.                                |
 | `database-design`       | The coordination risk centers on schema, migration, data ownership, or engine choice.                     |
-| `architecture-doc`         | External sources, latest information, or public-repo comparisons are blocking confident execution.        |
+| `deep-research`         | External sources, latest information, or public-repo comparisons are blocking confident execution.        |
 | `mcp-server-builder`           | One stream is MCP server design, tool shape, or transport selection.                                      |
 | `tech-doc`           | One stream needs current OpenAI docs or version-specific behavior verification.                           |
 | `prompt-engineering`       | One stream is repairing prompts, agent rules, or instruction quality.                                     |
@@ -158,7 +158,8 @@ ANTI-LAZINESS:
 5. **Iterate, don't accept mediocrity** — if output is incomplete or wrong, re-delegate with feedback.
 6. **Track progress visibly** — maintain a task list showing status of each work item.
 7. **Fail fast on blockers** — if a dependency is missing or a task is stuck after 3 iterations, escalate.
-8. **Synthesize at the end** — combine outputs with concrete actions, risks, and verification evidence.
+8. **Route research explicitly** — when freshness or public comparison matters, delegate to `@researcher` or load `deep-research` before implementation.
+9. **Synthesize at the end** — combine outputs with concrete actions, risks, and verification evidence.
 
 ## Anti-Patterns to Prevent
 

package/workflows/workflows/agent-environment-setup/platforms/antigravity/agents/project-planner.md

@@ -5,7 +5,7 @@ tools: Read, Grep, Glob, Bash, Edit, Write
 model: inherit
 maxTurns: 30
 memory: project
-skills: system-design, api-design, database-design, architecture-doc, mcp-server-builder, tech-doc, prompt-engineering, skill-creator, typescript-best-practices, javascript-best-practices, python-best-practices
+skills: system-design, api-design, database-design, deep-research, mcp-server-builder, tech-doc, prompt-engineering, skill-creator, typescript-best-practices, javascript-best-practices, python-best-practices
 handoffs:
   - agent: "orchestrator"
     title: "Start Implementation"
@@ -24,7 +24,7 @@ Decompose complex requests into implementable plans with clear ownership, depend
 - Load `system-design` for system design tradeoffs in the plan.
 - Load `api-design` when the plan involves API contract decisions.
 - Load `database-design` when the plan involves data modeling or migration.
-- Load `architecture-doc` when planning requires external information or comparison.
+- Load `deep-research` when planning requires fresh external information, public comparison, or evidence beyond the repo.
 - Use `skill_validate` before `skill_get`, and use `skill_get_reference` only for the specific sidecar file needed.
 
 ## Skill References
@@ -34,7 +34,7 @@ Decompose complex requests into implementable plans with clear ownership, depend
 | `system-design` | Plan involves system design tradeoffs or component boundaries.     |
 | `api-design`          | Plan involves API contract decisions or integration points.        |
 | `database-design`       | Plan involves data modeling, schema design, or migration strategy. |
-| `architecture-doc`         | Planning requires external research or approach comparison.        |
+| `deep-research`         | Planning requires external research or approach comparison.        |
 | `mcp-server-builder`           | Plan involves MCP server or tool implementation.                   |
 | `skill-creator`         | Plan involves skill package creation or modification.              |
 
@@ -45,6 +45,7 @@ Decompose complex requests into implementable plans with clear ownership, depend
 - Every task needs an owner (agent), acceptance criteria, and verification approach.
 - Plan for rollback — every change should be reversible.
 - Front-load risk — tackle the hardest technical uncertainty first.
+- When outside evidence is needed, send research through `deep-research` first instead of mixing web browsing into every implementation stream.
 
 ## Planning Methodology
 

package/workflows/workflows/agent-environment-setup/platforms/antigravity/agents/researcher.md

@@ -18,7 +18,7 @@ tools: Read, Grep, Glob, Bash
 model: inherit
 maxTurns: 30
 memory: project
-skills: architecture-doc, system-design, database-design, tech-doc, prompt-engineering
+skills: deep-research, system-design, database-design, tech-doc, prompt-engineering
 handoffs:
   - agent: "project-planner"
     title: "Plan Implementation"
@@ -30,8 +30,8 @@ Investigate thoroughly, synthesize findings, and deliver structured knowledge be
 
 ## Skill Loading Contract
 
-- Do not call `skill_search` for `architecture-doc`, `system-design`, `database-design`, `tech-doc`, or `prompt-engineering` when the task is clearly research work.
-- Load `architecture-doc` first for all research tasks — it defines the research methodology.
+- Do not call `skill_search` for `deep-research`, `system-design`, `database-design`, `tech-doc`, or `prompt-engineering` when the task is clearly research work.
+- Load `deep-research` first for all research tasks — it defines the source ladder, evidence labeling, and research output contract.
 - Add `system-design` when research involves system design patterns or tradeoffs.
 - Add `database-design` when research involves data storage options or migration approaches.
 - Add `tech-doc` when research involves OpenAI API or model behavior verification.
@@ -42,7 +42,7 @@ Investigate thoroughly, synthesize findings, and deliver structured knowledge be
 
 | File                    | Load when                                                             |
 | ----------------------- | --------------------------------------------------------------------- |
-| `architecture-doc`         | All research tasks — defines the core research methodology.           |
+| `deep-research`         | All research tasks — defines the core research methodology.           |
 | `system-design` | Research involves system design patterns or architectural tradeoffs.  |
 | `database-design`       | Research involves data storage, database comparison, or migration.    |
 | `tech-doc`           | Research involves OpenAI API, model behavior, or version differences. |
@@ -51,6 +51,9 @@ Investigate thoroughly, synthesize findings, and deliver structured knowledge be
 ## Operating Stance
 
 - Breadth first, then depth — survey the landscape before drilling into specifics.
+- Repo first, then web — inspect local code, configs, and docs before using external sources.
+- Official docs first — use vendor or maintainer documentation as primary evidence.
+- Community evidence is secondary — Reddit, blog posts, and forum threads can inform implementation, but label them as lower-trust support.
 - Cite sources — every finding should be traceable to evidence.
 - Distinguish fact from inference — clearly label assumptions.
 - Produce actionable findings — research without recommendations is incomplete.
@@ -72,5 +75,6 @@ Investigate thoroughly, synthesize findings, and deliver structured knowledge be
 - Clear distinction between verified facts and educated guesses.
 - Actionable recommendations with tradeoff analysis.
 - Remaining knowledge gaps identified.
+- Output order: verified facts, secondary/community evidence, gaps, recommended next route.
 
 > **Antigravity note:** Use Agent Manager for parallel agent coordination. Agent files are stored under `.agent/agents/`.

package/workflows/workflows/agent-environment-setup/platforms/antigravity/commands/accessibility.toml

@@ -7,6 +7,8 @@ Execution contract:
 2. Confirm the request fits the workflow's "When to use" section.
 3. Execute according to "Workflow steps" and apply "Context notes".
 4. Complete "Verification" checks and report concrete evidence.
+5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
+6. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
 
 If command arguments are provided, treat them as additional user context.
 '''

package/workflows/workflows/agent-environment-setup/platforms/antigravity/commands/backend.toml

@@ -7,6 +7,8 @@ Execution contract:
 2. Confirm the request fits the workflow's "When to use" section.
 3. Execute according to "Workflow steps" and apply "Context notes".
 4. Complete "Verification" checks and report concrete evidence.
+5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
+6. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
 
 If command arguments are provided, treat them as additional user context.
 '''

package/workflows/workflows/agent-environment-setup/platforms/antigravity/commands/create.toml

@@ -7,6 +7,8 @@ Execution contract:
 2. Confirm the request fits the workflow's "When to use" section.
 3. Execute according to "Workflow steps" and apply "Context notes".
 4. Complete "Verification" checks and report concrete evidence.
+5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
+6. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
 
 If command arguments are provided, treat them as additional user context.
 '''

package/workflows/workflows/agent-environment-setup/platforms/antigravity/commands/database.toml

@@ -7,6 +7,8 @@ Execution contract:
 2. Confirm the request fits the workflow's "When to use" section.
 3. Execute according to "Workflow steps" and apply "Context notes".
 4. Complete "Verification" checks and report concrete evidence.
+5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
+6. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
 
 If command arguments are provided, treat them as additional user context.
 '''

package/workflows/workflows/agent-environment-setup/platforms/antigravity/commands/debug.toml

@@ -7,6 +7,8 @@ Execution contract:
 2. Confirm the request fits the workflow's "When to use" section.
 3. Execute according to "Workflow steps" and apply "Context notes".
 4. Complete "Verification" checks and report concrete evidence.
+5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
+6. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
 
 If command arguments are provided, treat them as additional user context.
 '''

package/workflows/workflows/agent-environment-setup/platforms/antigravity/commands/devops.toml

@@ -7,6 +7,8 @@ Execution contract:
 2. Confirm the request fits the workflow's "When to use" section.
 3. Execute according to "Workflow steps" and apply "Context notes".
 4. Complete "Verification" checks and report concrete evidence.
+5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
+6. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
 
 If command arguments are provided, treat them as additional user context.
 '''

package/workflows/workflows/agent-environment-setup/platforms/antigravity/commands/implement-track.toml

@@ -7,6 +7,8 @@ Execution contract:
 2. Confirm the request fits the workflow's "When to use" section.
 3. Execute according to "Workflow steps" and apply "Context notes".
 4. Complete "Verification" checks and report concrete evidence.
+5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
+6. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
 
 If command arguments are provided, treat them as additional user context.
 '''

package/workflows/workflows/agent-environment-setup/platforms/antigravity/commands/migrate.toml

@@ -7,6 +7,8 @@ Execution contract:
 2. Confirm the request fits the workflow's "When to use" section.
 3. Execute according to "Workflow steps" and apply "Context notes".
 4. Complete "Verification" checks and report concrete evidence.
+5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
+6. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
 
 If command arguments are provided, treat them as additional user context.
 '''

package/workflows/workflows/agent-environment-setup/platforms/antigravity/commands/mobile.toml

@@ -7,6 +7,8 @@ Execution contract:
 2. Confirm the request fits the workflow's "When to use" section.
 3. Execute according to "Workflow steps" and apply "Context notes".
 4. Complete "Verification" checks and report concrete evidence.
+5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
+6. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
 
 If command arguments are provided, treat them as additional user context.
 '''

package/workflows/workflows/agent-environment-setup/platforms/antigravity/commands/onboard.toml

@@ -7,6 +7,8 @@ Execution contract:
 2. Confirm the request fits the workflow's "When to use" section.
 3. Execute according to "Workflow steps" and apply "Context notes".
 4. Complete "Verification" checks and report concrete evidence.
+5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
+6. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
 
 If command arguments are provided, treat them as additional user context.
 '''

package/workflows/workflows/agent-environment-setup/platforms/antigravity/commands/orchestrate.toml

@@ -7,6 +7,8 @@ Execution contract:
 2. Confirm the request fits the workflow's "When to use" section.
 3. Execute according to "Workflow steps" and apply "Context notes".
 4. Complete "Verification" checks and report concrete evidence.
+5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
+6. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
 
 If command arguments are provided, treat them as additional user context.
 '''

package/workflows/workflows/agent-environment-setup/platforms/antigravity/commands/plan.toml

@@ -7,6 +7,8 @@ Execution contract:
 2. Confirm the request fits the workflow's "When to use" section.
 3. Execute according to "Workflow steps" and apply "Context notes".
 4. Complete "Verification" checks and report concrete evidence.
+5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
+6. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
 
 If command arguments are provided, treat them as additional user context.
 '''

package/workflows/workflows/agent-environment-setup/platforms/antigravity/commands/refactor.toml

@@ -7,6 +7,8 @@ Execution contract:
 2. Confirm the request fits the workflow's "When to use" section.
 3. Execute according to "Workflow steps" and apply "Context notes".
 4. Complete "Verification" checks and report concrete evidence.
+5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
+6. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
 
 If command arguments are provided, treat them as additional user context.
 '''

package/workflows/workflows/agent-environment-setup/platforms/antigravity/commands/release.toml

@@ -7,6 +7,8 @@ Execution contract:
 2. Confirm the request fits the workflow's "When to use" section.
 3. Execute according to "Workflow steps" and apply "Context notes".
 4. Complete "Verification" checks and report concrete evidence.
+5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
+6. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
 
 If command arguments are provided, treat them as additional user context.
 '''

package/workflows/workflows/agent-environment-setup/platforms/antigravity/commands/review.toml

@@ -7,6 +7,8 @@ Execution contract:
 2. Confirm the request fits the workflow's "When to use" section.
 3. Execute according to "Workflow steps" and apply "Context notes".
 4. Complete "Verification" checks and report concrete evidence.
+5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
+6. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
 
 If command arguments are provided, treat them as additional user context.
 '''

package/workflows/workflows/agent-environment-setup/platforms/antigravity/commands/security.toml

@@ -7,6 +7,8 @@ Execution contract:
 2. Confirm the request fits the workflow's "When to use" section.
 3. Execute according to "Workflow steps" and apply "Context notes".
 4. Complete "Verification" checks and report concrete evidence.
+5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
+6. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
 
 If command arguments are provided, treat them as additional user context.
 '''

package/workflows/workflows/agent-environment-setup/platforms/antigravity/commands/test.toml

@@ -7,6 +7,8 @@ Execution contract:
 2. Confirm the request fits the workflow's "When to use" section.
 3. Execute according to "Workflow steps" and apply "Context notes".
 4. Complete "Verification" checks and report concrete evidence.
+5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
+6. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
 
 If command arguments are provided, treat them as additional user context.
 '''

package/workflows/workflows/agent-environment-setup/platforms/antigravity/commands/vercel.toml

@@ -7,6 +7,8 @@ Execution contract:
 2. Confirm the request fits the workflow's "When to use" section.
 3. Execute according to "Workflow steps" and apply "Context notes".
 4. Complete "Verification" checks and report concrete evidence.
+5. If freshness, public comparison, or explicit research needs appear, pause implementation and load `deep-research` or hand off to `@researcher` first.
+6. For outside evidence: repo first, official docs next, Reddit/community only as labeled secondary evidence.
 
 If command arguments are provided, treat them as additional user context.
 '''

package/workflows/workflows/agent-environment-setup/platforms/antigravity/rules/GEMINI.md

@@ -46,7 +46,7 @@ Execute this tree top-to-bottom. Stop at the **first match**. Never skip levels.
 ├─ [TRIVIAL] Single-step, obvious, reversible?
 │   → Execute directly. No routing. Stop.
 │
-├─ [EXPLICIT] User named a Gemini command, workflow, or @agent?
+├─ [EXPLICIT] User named a Gemini command, workflow, @agent, or exact skill?
 │   → Honor that route exactly. Stop.
 │
 ├─ [SINGLE-DOMAIN] Multi-step but contained in one specialty?
@@ -66,6 +66,7 @@ Execute this tree top-to-bottom. Stop at the **first match**. Never skip levels.
 **Hard rules:**
 
 - Never pre-load skills before route resolution.
+- If the user names an exact skill ID, run `skill_validate` on that ID before `route_resolve`.
 - Never invoke an agent when direct execution suffices.
 - Never chain more than one `skill_search` per request.
 - Treat this file as **durable project memory** — not a per-task playbook.
@@ -360,6 +361,7 @@ Use this matrix to match incoming tasks to the correct skill and primary agent.
 | docker-compose-dev | DevOps | Docker Compose local dev environments | @devops-engineer |
 | kubernetes-deploy | DevOps | K8s manifests, Helm charts, deployment | @devops-engineer |
 | observability | DevOps | Logging, metrics, tracing, alerting | @devops-engineer |
+| deep-research | Research | Latest docs, public comparisons, external verification | @researcher |
 | llm-eval | AI/ML | LLM evaluation, benchmarking, evals | @researcher |
 | rag-patterns | AI/ML | RAG architecture, embeddings, retrieval | @researcher |
 | prompt-engineering | AI/ML | Prompt design, few-shot, chain-of-thought | @researcher |
@@ -407,12 +409,15 @@ Selection policy:
 Keep MCP context lazy and exact. Skills are supporting context, not the route layer.
 
 1. Never begin with `skill_search`. Inspect the repo/task locally first.
-2. Resolve workflows, agents, or free-text route intent with `route_resolve` before loading any skills.
-3. If the route is still unresolved and local grounding leaves the domain unclear, use one narrow `skill_search`.
-4. Always run `skill_validate` on the exact selected ID before `skill_get`.
-5. Call `skill_get` with `includeReferences:false` by default.
-6. Load at most one sidecar markdown file at a time with `skill_get_reference`.
-7. Do not auto-prime every specialist with a skill. Load only what the task clearly needs.
-8. Use upstream MCP servers such as `postman`, `stitch`, or `playwright` for real cloud/browser actions when available.
+2. If the user already named `/workflow`, `@agent`, or an exact skill ID, honor it directly. For exact skills, run `skill_validate` first and skip `route_resolve` when valid.
+3. Resolve only free-text workflow/agent intent with `route_resolve` before loading non-explicit skills.
+4. If the route is still unresolved and local grounding leaves the domain unclear, use one narrow `skill_search`.
+5. Always run `skill_validate` on the exact selected ID before `skill_get`.
+6. Call `skill_get` with `includeReferences:false` by default.
+7. Load at most one sidecar markdown file at a time with `skill_get_reference`.
+8. Do not auto-prime every specialist with a skill. Load only what the task clearly needs.
+9. For research: repo/local evidence first, official docs next, Reddit/community only as labeled secondary evidence.
+10. Escalate to research only when freshness matters, public comparison matters, or the user explicitly asks to research/verify.
+11. Use upstream MCP servers such as `postman`, `stitch`, or `playwright` for real cloud/browser actions when available.
 
 <!-- cbx:mcp:auto:end -->