@cubis/foundry 0.3.63 → 0.3.65

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

@@ -3,9 +3,10 @@ prompt = '''
 Follow the /mobile workflow from .agent/workflows/mobile.md.
 
 Execution contract:
-1. Confirm the request fits the workflow's "When to use" section.
-2. Execute according to "Workflow steps" and apply "Context notes".
-3. Complete "Verification" checks and report concrete evidence.
+1. Treat route selection as already resolved by this command; do not begin with skill discovery.
+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.
 
 If command arguments are provided, treat them as additional user context.
 '''

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

@@ -3,9 +3,10 @@ prompt = '''
 Follow the /orchestrate workflow from .agent/workflows/orchestrate.md.
 
 Execution contract:
-1. Confirm the request fits the workflow's "When to use" section.
-2. Execute according to "Workflow steps" and apply "Context notes".
-3. Complete "Verification" checks and report concrete evidence.
+1. Treat route selection as already resolved by this command; do not begin with skill discovery.
+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.
 
 If command arguments are provided, treat them as additional user context.
 '''

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

@@ -3,9 +3,10 @@ prompt = '''
 Follow the /plan workflow from .agent/workflows/plan.md.
 
 Execution contract:
-1. Confirm the request fits the workflow's "When to use" section.
-2. Execute according to "Workflow steps" and apply "Context notes".
-3. Complete "Verification" checks and report concrete evidence.
+1. Treat route selection as already resolved by this command; do not begin with skill discovery.
+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.
 
 If command arguments are provided, treat them as additional user context.
 '''

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

@@ -3,9 +3,10 @@ prompt = '''
 Follow the /postman workflow from .agent/workflows/postman.md.
 
 Execution contract:
-1. Confirm the request fits the workflow's "When to use" section.
-2. Execute according to "Workflow steps" and apply "Context notes".
-3. Complete "Verification" checks and report concrete evidence.
+1. Treat route selection as already resolved by this command; do not begin with skill discovery.
+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.
 
 If command arguments are provided, treat them as additional user context.
 '''

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

@@ -3,9 +3,10 @@ prompt = '''
 Follow the /qa workflow from .agent/workflows/qa.md.
 
 Execution contract:
-1. Confirm the request fits the workflow's "When to use" section.
-2. Execute according to "Workflow steps" and apply "Context notes".
-3. Complete "Verification" checks and report concrete evidence.
+1. Treat route selection as already resolved by this command; do not begin with skill discovery.
+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.
 
 If command arguments are provided, treat them as additional user context.
 '''

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

@@ -3,9 +3,10 @@ prompt = '''
 Follow the /refactor workflow from .agent/workflows/refactor.md.
 
 Execution contract:
-1. Confirm the request fits the workflow's "When to use" section.
-2. Execute according to "Workflow steps" and apply "Context notes".
-3. Complete "Verification" checks and report concrete evidence.
+1. Treat route selection as already resolved by this command; do not begin with skill discovery.
+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.
 
 If command arguments are provided, treat them as additional user context.
 '''

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

@@ -3,9 +3,10 @@ prompt = '''
 Follow the /release workflow from .agent/workflows/release.md.
 
 Execution contract:
-1. Confirm the request fits the workflow's "When to use" section.
-2. Execute according to "Workflow steps" and apply "Context notes".
-3. Complete "Verification" checks and report concrete evidence.
+1. Treat route selection as already resolved by this command; do not begin with skill discovery.
+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.
 
 If command arguments are provided, treat them as additional user context.
 '''

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

@@ -3,9 +3,10 @@ prompt = '''
 Follow the /review workflow from .agent/workflows/review.md.
 
 Execution contract:
-1. Confirm the request fits the workflow's "When to use" section.
-2. Execute according to "Workflow steps" and apply "Context notes".
-3. Complete "Verification" checks and report concrete evidence.
+1. Treat route selection as already resolved by this command; do not begin with skill discovery.
+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.
 
 If command arguments are provided, treat them as additional user context.
 '''

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

@@ -3,9 +3,10 @@ prompt = '''
 Follow the /security workflow from .agent/workflows/security.md.
 
 Execution contract:
-1. Confirm the request fits the workflow's "When to use" section.
-2. Execute according to "Workflow steps" and apply "Context notes".
-3. Complete "Verification" checks and report concrete evidence.
+1. Treat route selection as already resolved by this command; do not begin with skill discovery.
+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.
 
 If command arguments are provided, treat them as additional user context.
 '''

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

@@ -3,9 +3,10 @@ prompt = '''
 Follow the /test workflow from .agent/workflows/test.md.
 
 Execution contract:
-1. Confirm the request fits the workflow's "When to use" section.
-2. Execute according to "Workflow steps" and apply "Context notes".
-3. Complete "Verification" checks and report concrete evidence.
+1. Treat route selection as already resolved by this command; do not begin with skill discovery.
+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.
 
 If command arguments are provided, treat them as additional user context.
 '''

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

@@ -3,9 +3,10 @@ prompt = '''
 Follow the /vercel workflow from .agent/workflows/vercel.md.
 
 Execution contract:
-1. Confirm the request fits the workflow's "When to use" section.
-2. Execute according to "Workflow steps" and apply "Context notes".
-3. Complete "Verification" checks and report concrete evidence.
+1. Treat route selection as already resolved by this command; do not begin with skill discovery.
+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.
 
 If command arguments are provided, treat them as additional user context.
 '''

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

@@ -4,7 +4,7 @@ trigger: always_on
 
 # GEMINI.md - Cubis Foundry Antigravity Protocol
 
-This file defines mandatory behavior for Antigravity projects installed via `cbx workflows`.
+This file defines durable project guidance for Antigravity installs created by `cbx workflows`.
 
 ## 1) Platform Paths
 
@@ -14,48 +14,38 @@ This file defines mandatory behavior for Antigravity projects installed via `cbx
 - Gemini commands: `.gemini/commands`
 - Rules file: `.agent/rules/GEMINI.md`
 
-## Startup Transparency (Minimal)
+## 2) Core Steering
 
-Before substantial work, publish one short status line only:
+1. Treat this file as persistent project context, not as a task-by-task playbook.
+2. Inspect the repo or task locally before choosing a route or loading any skill.
+3. Treat commands, workflows, and agents as the route layer. Treat skills as optional supporting context.
+4. If the request is small and clear, execute directly. Do not start with skill discovery.
+5. If the user explicitly names a command, workflow, or agent, honor that route first.
+6. If the task is multi-step, choose one primary workflow. Use `@orchestrator` only for genuinely cross-domain work.
+7. Load a skill only when the user names one, the route is still unclear after inspection, or a specialized route clearly needs domain context.
 
-`Status: rules=<files> | mcp=<ok|offline> | route=<workflow|direct> | agent=<agent|direct> | skills=<ids|none>`
+## 3) Native Route Order
 
-Rules:
+Follow this order:
 
-1. Emit this once at task start; send an update only when routing materially changes.
-2. Do not print tool-call transcripts (for example: "Explored ...", "Ran command ...") unless the user explicitly asks for verbose trace logs.
-3. Keep progress updates to one short sentence.
-4. For pure Q&A replies, skip the status line.
+1. Explicit Gemini command, workflow, or `@agent`
+2. Direct execution for a simple, obvious task
+3. One primary workflow for multi-step work
+4. Agent Manager or `@orchestrator` for cross-domain work
+5. One narrow skill lookup only if the domain is still unclear
 
-## 2) Workflow-First Contract
+Use Gemini commands and workflow files as the primary route surface. Do not treat Codex compatibility aliases (`$workflow-*`, `$agent-*`) as native Antigravity surfaces.
 
-1. If the user explicitly requests a slash command, run that command/workflow first.
-2. Otherwise choose the best workflow by intent from `.agent/workflows` and use matching `.gemini/commands/*.toml` when available.
-3. For cross-domain tasks, use orchestrated delegation with `@orchestrator`.
-4. Keep one primary workflow; use others only as supporting references.
-5. Before loading any skill, inspect the repo/task locally first. Use MCP skill tools only when the user names a skill explicitly or local grounding still leaves the domain unclear (→ §5 MCP Skill Engine).
+## 4) Skills and Agents
 
-## 3) Request Classifier
-
-1. Question or explanation requests: answer directly, no implementation.
-2. Survey/intel requests: inspect and summarize before editing.
-3. Simple code changes: minimal edits with focused verification.
-4. Complex code/design changes: plan first, then implement and verify.
-
-## 3A) Workflow Pattern Map (Antigravity)
-
-Map intent to one primary workflow first:
-
-- Explain codebase -> `/plan`
-- Fix bug -> `/debug`
-- Write test -> `/test` or `/qa`
-- Prototype from screenshot -> `/create` + `@frontend-specialist`
-- Iterate UI updates -> `/create` with verification loop
-- Refactor safely -> `/refactor` (or `@code-archaeologist` if scope is narrow)
-- Local code review -> `/review`
-- Documentation update -> `/create` + `@documentation-writer`
-
-## 4) Agent Routing Policy
+1. Never begin with `skill_search`.
+2. If the exact skill ID is already known, run `skill_validate` before `skill_get`.
+3. Otherwise, use at most one narrow `skill_search` after local inspection and route resolution.
+4. Call `skill_get` with `includeReferences:false` by default.
+5. Load one reference file at a time with `skill_get_reference`.
+6. Do not auto-prime every specialist with a skill. Prime only when the task or route clearly needs it.
+7. Give spawned agents narrow scope and non-overlapping ownership.
+8. Never pass workflow IDs or agent IDs to skill tools.
 
 Use the best specialist first:
 
@@ -68,180 +58,26 @@ Use the best specialist first:
 - Debugging/performance: `@debugger`, `@performance-optimizer`
 - Cross-domain orchestration: `@orchestrator`
 
-### MCP Skill Priming (Required Before Delegation)
-
-Before handing off to any specialist agent, prime context with the relevant domain skill (→ §5 MCP Skill Engine):
-
-1. Validate user-named exact skills with `skill_validate <id>` before loading them.
-2. If the domain is still unclear after local grounding, run one narrow `skill_search <domain>` and then validate the chosen exact ID with `skill_validate <id>`.
-3. Load the core skill with `skill_get <id>` using `includeReferences:false` by default.
-4. Pull one sidecar markdown file at a time with `skill_get_reference` when the skill or task requires it.
-5. Include the validated skill ID in the Decision Log for the routing decision.
-
-This ensures the specialist starts with accurate domain knowledge, not just role intent.
-
-## 5) MCP Skill Engine
-
-The Foundry MCP server is the primary knowledge layer. Use tools decisively — discover first, load only when committed.
-
-### Tool Namespace Reference
-
-| Prefix      | Tools                                                                                                | When to use                                                    |
-| ----------- | ---------------------------------------------------------------------------------------------------- | -------------------------------------------------------------- |
-| `skill_*`   | `skill_list_categories`, `skill_search`, `skill_validate`, `skill_browse_category`, `skill_get`, `skill_get_reference`, `skill_budget_report` | Domain expertise for implementation, debug, or review without loading the full catalog |
-| `postman_*` | `postman_get_mode`, `postman_set_mode`, `postman_get_status`                                         | API testing or Postman configuration tasks                     |
-| `stitch_*`  | `stitch_get_mode`, `stitch_set_profile`, `stitch_get_status`                                         | Stitch data pipeline tasks                                     |
-
-### Validated Skill Flow (Mandatory Order)
-
-Stop at the earliest step that gives enough signal. Do not jump ahead or front-load skill discovery.
-
-1. Inspect the codebase/task locally first; do not start with `skill_search`
-2. If the user names an exact skill ID, call `skill_validate <id>` directly
-3. Otherwise, if local grounding still leaves the domain unclear, run one narrow `skill_search <keyword>`
-4. Validate the selected exact skill ID with `skill_validate <id>` before any load
-5. Load only the core `SKILL.md` with `skill_get <id>` and `includeReferences:false`
-6. Load at most one sidecar markdown file at a time with `skill_get_reference <id> <path>`
-7. Use `skill_list_categories` or `skill_browse_category` only as fallback when targeted search fails
-8. Use `skill_budget_report` internally only when the user explicitly asks for context accounting
-
-### Postman Intent Trigger (Required)
-
-When user intent includes Postman workflows (for example: workspace, collection, environment, runCollection, monitor, mock, or "run Postman tests"):
-
-1. Validate `postman` directly with `skill_validate "postman"` when the exact skill ID is known.
-2. If validation fails and local grounding is still insufficient, run a narrow `skill_search "postman"` and validate the selected exact ID.
-3. Load `skill_get "postman"` with `includeReferences:false` before workflow/agent routing.
-4. Prefer Postman MCP tools (`postman.*`) over Newman/CLI fallback unless the user explicitly asks for fallback.
-5. If `--postman` was installed but `postman` skill cannot be found, report installation drift and suggest reinstall with `cbx workflows install ... --postman`.
-
-**Hard rules:**
-
-- Never call `skill_get` from fuzzy search output without first validating the exact ID via `skill_validate`
-- Never skip local repo inspection and jump straight to `skill_search`
-- Never call `skill_get` with a workflow ID — `workflow-*` are routes, not skills; keep workflow mentions in the Decision Log
-- Never call `skill_get` with `includeReferences:true` by default in agent workflows
-- Never bulk-load sibling/reference markdown files when one targeted `skill_get_reference` will do
-- Never reload a skill already loaded this session — reuse content already in context
-- If `skill_search` returns 0 results, try `skill_browse_category`, then fall back to built-in knowledge
-
-### Adaptive Load Policy
-
-| Request type                                   | Skills to load via `skill_get`                                  |
-| ---------------------------------------------- | --------------------------------------------------------------- |
-| Q&A / explanation                              | None — answer from knowledge; load only if user explicitly asks |
-| Single-domain implementation, debug, or review | 1 primary + 1 supporting (max)                                  |
-| Multi-domain / orchestration                   | 1 per distinct domain, hard cap at 3                            |
-| User explicitly names a skill                  | Always load it — overrides all caps                             |
-
-### Graceful Degradation
-
-If MCP tools are unavailable (server down, timeout, tool not listed):
-
-1. Announce briefly: "MCP unavailable — continuing with built-in knowledge."
-2. Proceed using codebase context and expertise; do not block on MCP.
-3. Never fabricate or hallucinate skill content.
-4. Retry once on transient network errors; accept failure after the retry.
-
-### Skill Log (Minimal)
-
-After `skill_get`, include at most one short line:
-
-`Skills: <id1,id2>` or `Skills: none (fallback)`.
-
-Do not append budget tables or token summaries unless the user explicitly asks.
+## 5) Long-Running and Handoff Work
 
-### Reference Files (Required When Relevant)
+1. Use `/implement-track` or the matching Gemini command/workflow pair for milestone-based work, resumable execution, or progress checkpoints.
+2. Use Agent Manager or `@orchestrator` when multiple specialties need explicit ownership or handoff.
+3. Preserve workflow output contracts when handing work between agents, especially `milestones`, `gates`, and `next_handoff`.
 
-Reference markdown files are first-class skill context, but they must be loaded selectively.
-
-1. Use `skill_validate` to see `availableReferences` for the exact skill
-2. Start with `skill_get(..., includeReferences:false)` to load only the core skill body
-3. If the skill points to a reference or the task clearly needs sidecar detail, load one file with `skill_get_reference`
-4. Only load another reference if the first one still leaves a concrete gap
-
-
-### Anti-Patterns (Never Do These)
-
-- Loading skills speculatively "just in case" they might be useful
-- Calling `skill_get` before `skill_validate`
-- Using partial or guessed skill IDs in `skill_get`
-- Treating `skill_search` results as an implicit final selection
-- Starting a task with `skill_list_categories` or broad catalog browsing
-- Publishing verbose budget fields (`full_catalog_est_tokens`, `loaded_est_tokens`, etc.) in responses
-- Re-emitting the ctx stamp multiple times within a single response
-- Treating workflow IDs as skill IDs in any MCP tool call
-
-## 6) Socratic Gate (Before Complex Work)
-
-Before multi-file or architecture-impacting changes, ask targeted questions when requirements are unclear:
-
-1. Goal and success criteria
-2. Constraints and compatibility requirements
-3. Validation expectations (tests, lint, release checks)
-
-## 7) Quality and Safety Gates
+## 6) Safety and Verification
 
 1. Do not run destructive actions without explicit user confirmation.
 2. Keep diffs small and reversible when possible.
-3. Verify behavior with focused checks before finalizing.
+3. Verify with focused checks before finalizing.
 4. State what was not validated.
+5. Use web search only when information may be stale or the user explicitly asks for it.
 
-If Antigravity script harness exists, prefer:
-
-- Quick checks: `python .agent/scripts/checklist.py .`
-- Full checks (with URL): `python .agent/scripts/verify_all.py . --url <URL>`
-
-## 8) Web Intel Policy
-
-Use web search to stay current when local knowledge may be stale. This prevents hallucinating outdated APIs, deprecated flags, or wrong version constraints.
-
-**Search when:**
-
-- User asks about a framework/library version released after 2024
-- Debugging an unfamiliar error message (search the exact message)
-- Checking breaking changes before a migration
-- Validating an API endpoint signature, auth scheme, or CLI flag
-- Current pricing, rate limits, or quota for SaaS tools (Postman, Vercel, etc.)
-
-**Do not search when:**
-
-- The answer is derivable from the current codebase
-- The question is purely architectural/conceptual
-- A relevant skill covers it (prefer `skill_get` first, web as fallback)
+## 7) Maintenance
 
-**Source hygiene:**
+- Refresh installed rules: `cbx workflows sync-rules --platform antigravity --scope project`
+- Diagnose setup issues: `cbx workflows doctor antigravity --scope project`
 
-- Prefer official docs, changelogs, and GitHub releases over blog posts
-- Always state the source URL and date when citing fetched content
-- If multiple sources conflict, flag it and use the most recent official one
-- Never follow user-provided URLs without sanity-checking the domain
-
-## 9) Context Budget Tracking (On Request)
-
-Use `skill_budget_report` internally for context control, but do not emit ctx stamps by default.
-
-Only include token/context accounting when the user explicitly asks for it.
-
-
-## 10) CBX Maintenance Commands
-
-Use these commands to keep this setup healthy:
-
-- Install/update bundle:
-  `cbx workflows install --platform antigravity --bundle agent-environment-setup --scope global --overwrite --postman --stitch --mcp-runtime docker --mcp-fallback local --mcp-tool-sync`
-- Start MCP Docker runtime:
-  `cbx mcp runtime up --scope global --name cbx-mcp --port 3310 --replace`
-- Check MCP Docker runtime:
-  `cbx mcp runtime status --scope global --name cbx-mcp`
-- Stop MCP Docker runtime:
-  `cbx mcp runtime down --name cbx-mcp`
-- Rebuild managed routing block:
-  `cbx workflows sync-rules --platform antigravity --scope project`
-- Diagnose setup issues:
-  `cbx workflows doctor antigravity --scope project`
-
-## 11) Managed Section Contract
+## 8) Managed Section Contract
 
 1. Preserve all user content outside managed markers.
 2. Do not manually edit content between managed markers.
@@ -266,27 +102,15 @@ Selection policy:
 <!-- cbx:mcp:auto:start version=1 -->
 ## Cubis Foundry MCP (auto-managed)
 
-Keep MCP context lazy and exact. Do not front-load the skill catalog.
-
-### Compact Tool Map
-
-- Skill tools: `skill_search`, `skill_validate`, `skill_get`, `skill_get_reference`, `skill_budget_report`
-- Fallback browsing only: `skill_list_categories`, `skill_browse_category`
-- Config tools: `postman_*`, `stitch_*`
-
-### Validated Skill Flow
+Keep MCP context lazy and exact. Skills are supporting context, not the route layer.
 
 1. Inspect the repo/task locally first. Do not start with `skill_search`.
-2. If the user names an exact skill, run `skill_validate` directly. Otherwise use one narrow `skill_search` only if local grounding still leaves the domain unclear.
-3. Always run `skill_validate` on the exact selected ID before `skill_get`.
-4. Call `skill_get` with `includeReferences:false` by default.
-5. Load at most one sidecar markdown file at a time with `skill_get_reference`.
-6. Use `skill_list_categories` or `skill_browse_category` only as fallback when targeted search fails.
-7. Never print catalog counts or budget details unless the user asks.
-
-### Connection
-
-- **stdio**: `cbx mcp serve --transport stdio --scope auto`
-- **HTTP**: `cbx mcp serve --transport http --scope auto --port 3100`
+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` for real cloud actions when available.
 
 <!-- cbx:mcp:auto:end -->

package/workflows/workflows/agent-environment-setup/platforms/antigravity/workflows/backend.md

@@ -5,22 +5,33 @@ triggers: ["backend", "api", "service", "database", "performance"]
 ---
 # Backend Workflow
 
+# CHANGED: routing contract — made workflow-to-agent and skill mapping explicit — prevents blind startup skill_search and keeps agent selection machine-readable.
+# CHANGED: output contract — replaced human-readable bullets with structured payload fields — allows downstream agents to consume workflow output without re-asking for context.
+
 ## When to use
 Use this when backend architecture or service logic is primary.
 
 ## Routing
 - Primary specialist: `@backend-specialist`
-- Add `@database-architect` for schema/query changes.
-- Add `@security-auditor` when auth, secrets, or sensitive data are involved.
+- Add `@database-architect` for `schema`, `migration`, `query`, `index`, or `N+1` tasks.
+- Add `@security-auditor` for `auth`, `jwt`, `oauth`, `rbac`, `session`, or `secrets`.
+
+## Skill Routing
+- Primary skills: `api-designer`, `nodejs-best-practices`
+- Supporting skills (optional): `api-patterns`, `database-skills`, `secure-code-guardian`, `postman`
+- Primary skill route:
+  - api, endpoint, REST, route, openapi, swagger, spec, contract → `api-designer`
+  - backend, service, middleware, hono, fastify, node → `nodejs-best-practices`
+- Supporting skills:
+  - schema, migration, query, index, performance, N+1 → `database-skills`
+  - auth, jwt, rbac, oauth, session, secrets → `secure-code-guardian`
+  - postman, collection, environment → `postman`
+  - response format, pagination, versioning → `api-patterns`
 
 ## Context notes
 - This workflow file, active platform rules, and selected agents/skills guide execution.
 - Attach logs, screenshots, failing output, and relevant paths when context is incomplete.
 
-## Skill Routing
-- Primary skills: `nodejs-best-practices`, `api-designer`
-- Supporting skills (optional): `api-patterns`, `database-skills`, `secure-code-guardian`
-
 ## Workflow steps
 1. Ask specialist(s) for design and risk assessment.
 2. Validate contracts, data model, and failure handling.
@@ -34,10 +45,26 @@ Use this when backend architecture or service logic is primary.
 - Note any gaps that were not validated.
 
 ## Output Contract
-- API/contract changes
-- OpenAPI spec path
-- Swagger UI route
-- Stoplight route/component status
-- Migration impact
-- Reliability/security notes
-- Verification evidence
+```yaml
+BACKEND_WORKFLOW_RESULT:
+  primary_agent_id: "backend-specialist"
+  supporting_agent_ids: ["database-architect", "security-auditor"]
+  primary_skill_ids: ["api-designer", "nodejs-best-practices"]
+  supporting_skill_ids: ["api-patterns", "database-skills", "secure-code-guardian", "postman"]
+  contract_changes:
+    summary: "Describe contract deltas"
+    openapi_spec_path: null
+    swagger_ui_route: null
+    stoplight_route_or_component: null
+  data_impact:
+    migration_required: false
+    migration_notes: null
+  reliability_and_security:
+    observability_notes: "Summarize logging, tracing, metrics, and alerting impact"
+    security_notes: "Summarize auth, validation, and sensitive-data impact"
+  verification:
+    checks_run: ["<command-or-test>"]
+    gaps: []
+  next_handoff:
+    plan_handoff: null
+```

package/workflows/workflows/agent-environment-setup/platforms/antigravity/workflows/brainstorm.md

@@ -5,9 +5,17 @@ triggers: ["idea", "brainstorm", "options", "tradeoff", "approach"]
 ---
 # Brainstorm Workflow
 
+# CHANGED: routing — added explicit primary and supporting specialists — prevents route manifest fallback to orchestrator for ideation work.
+# CHANGED: output contract — converted free-form bullets into structured YAML — keeps option handoff machine-readable across platforms.
+
 ## When to use
 Use this when requirements are still fluid and architecture choices are open.
 
+## Routing
+- Primary specialist: `@project-planner`
+- Scope and user-value framing: `@product-manager`
+- Technical tradeoff review: `@backend-specialist`
+
 ## Context notes
 - This workflow file, active platform rules, and selected agents/skills guide execution.
 - Attach logs, screenshots, failing output, and relevant paths when context is incomplete.
@@ -28,7 +36,21 @@ Use this when requirements are still fluid and architecture choices are open.
 - Note any gaps that were not validated.
 
 ## Output Contract
-- Option table (pros/cons)
-- Recommended option
-- Known unknowns
-- First implementation milestone
+```yaml
+BRAINSTORM_WORKFLOW_RESULT:
+  primary_agent: project-planner
+  supporting_agents: [product-manager?, backend-specialist?]
+  primary_skills: [brainstorming, feature-forge]
+  supporting_skills: [plan-writing?]
+  options:
+    - id: <string>
+      summary: <string>
+      pros: [<string>]
+      cons: [<string>]
+      risks: [<string>]
+  recommended_option: <option-id>
+  known_unknowns: [<string>] | []
+  first_milestone: <string>
+  next_handoff:
+    plan_handoff: <PLAN_HANDOFF|null>
+```