c1-squire-dispatch

name

c1-squire-dispatch

description

c1-specific values for the general squire dispatch protocols defined in squire-env-management. Provides the c1 gate bundle's contents, the task-family table for c1 work, the c1 always-actives, and the list of c1 skills that should NOT be spent on a squire env. Use when about to spawn a squire env to execute c1 work, when writing a brief for a remote c1 agent, or when filing a c1 bead intended for squire dispatch. Triggers: c1 squire dispatch, c1 squire brief, c1 remote work, c1 ephemeral env, c1 fire-and-forget.

c1 squire dispatch

The c1-specific instantiation of the protocols now defined in the sqfan skill (originally in squire-env-management, since folded into sqfan). The host skill provides the shape — gate bundle pattern, brief-templates concept, beads manifest format, failure debrief protocol. This skill provides the c1 content that fills those shapes.

Read sqfan for the protocol mechanics. Read this skill for what to plug into them. squire-env-management retains the single-env reference content (Core Commands, OpenCode API Protocol, etc.) but its multi-env orchestration sections are deprecated in favor of sqfan.

Pairs with c1-dev-stack-in-squire (the env shape for tasks that need a running c1 backend).

c1 Always-Actives

Every c1 squire brief implicitly loads these on top of the task-family row:

• security-patterns — MUST when touching auth, authz, context propagation, sensitive data
• pgdb-index-coverage — MUST when adding WHERE clauses or proto indexes
• go-conventions — when writing Go in pkg/ or cmd/
• code-search — for navigation

c1 Gate Bundle

Resolves Gates: standard for c1. The remote agent expands to the relevant subset based on file types changed in the diff.