06-reference/research

brigade skills snowflake cortex code

2026-07-05·research-brief·source: deep-research
snowflake-cortex-codeagent-brigadecafdeploymentphdata

Brigade in Cortex Code: yes — CoCo ships a Claude-Code-compatible plugin/skill/subagent model, which unblocks P3/P4

The question

"Can Brigade skills/plugins actually run inside Snowflake Cortex Code, and what does the packaging support look like?" Context: this cell was flagged unevaluated in the 2026-07-03 Hex deployment matrix and blocks CAF deployment profiles P3 (Snowflake-native) / P4 (Cowork sales org) before the next phData DSA client deployment conversation.

What we already know (from the vault)

What the web says

Convergences and contradictions

Synthesis for RDCO

Brigade CAN run inside Snowflake Cortex Code, and the packaging support is strong — effectively Claude Code plugin compatibility. The 2026-07-03 matrix cell should flip from "⚠️ unevaluated — do not assume" to "supported, with light adaptation." Cortex Code CLI packages exactly what the Brigade is made of (SKILL.md skills, ./agents/ subagents, slash commands, hooks, MCP servers) under one manifest, and it reads the Claude Code manifest path and skill/agent directories directly. The Brigade's existing LIVE Claude Code plugin is the starting artifact, not a rewrite target.

This unblocks P3 and P4 and, more importantly, simplifies them. P3 no longer has to be "an SPCS container hosting a headless Claude Code session"; the client-governed path becomes ship the Brigade plugin via a Snowflake connection profile (org-admin-published, governed distribution) and run it on a CoCo surface (CLI in SPCS, or Cloud Agents once out of private preview). The Brigade's public five-command interface maps to CoCo slash commands, Gate-A lint maps to a PreToolUse hook plus cortex plugin validate, and the rail/cellar ports still bind to Snowflake stage + table as already specced. P4's Cowork story is unchanged but gains a second option: CoCo's MCP/ACP interop means the sales-seat surface could call the Brigade rather than re-hosting it.

The one load-bearing caveat before a client conversation is C1 (egress) and model routing. If CoCo Cloud Agents serve Claude models from within Snowflake's boundary, then the single hardest objection in the matrix — external Anthropic API egress requiring client-admin approval — largely evaporates, which materially strengthens the P3 pitch to Snowflake AEs. That's the highest-value thing to confirm. The honest framing for the DSA conversation: "the Brigade packages as a native Cortex Code plugin (Claude Code-compatible manifest), distributable through a governed connection profile; the remaining spike is confirming in-boundary model routing and remapping any station subagent tools/model-IDs to CoCo's surface."

Net: this is not a non-starter and does not force a different profile. It converts P3/P4 from "gated on unverified packaging" to "gated on a small confirmation spike (egress + a portability smoke test)." Recommend a one-session spike: install the existing skill-agent-brigade plugin into a Cortex Code CLI against the phData sandbox, run cortex plugin validate, and fire one end-to-end station pass. That single test converts every "should" in this brief to "does."

Open follow-ups

Related

Sources