context-bridge-dispatchlisted

# context-bridge-dispatch — Parallel Agent Context Bridge In agent dispatch, sub-agents can read files but do not have access to the live conversation context of the main session. This skill generates a session context card before dispatch and injects it into each agent prompt. ## Triggers | Phrase pattern | Situation | |---|---| | "do it in parallel" / "agent view" + 2+ tasks | Auto-triggered | | "create a context bridge" | Explicit call | | `/context-bridge-dispatch` | Explicit call | | Immediately before dispatching 2+ agents | Auto-injected | ## Context Card Format ``` [Session Context Card] Purpose: {the goal of this session / task} Completed: {what has already been decided or implemented — risk of duplication if agent doesn't know} This agent's task: {the specific task for this agent} Note: {constraints, directions, or history the agent must know before acting} ``` ## Step 1. Extract Session Context Summarize the 3 key items from the current conversation: - **Purpose**: Core goal of this session / request - **Completed**: What has already been built or decided (include file paths and commits) - **Note**: Constraints that could lead an agent in the wrong direction if unknown ## Step 2. Identify Agent List + Generate Individual Cards For each of the N agents to dispatch: - Common Context Card (Step 1 summary) - Agent-specific item (`This agent's task` field customized per agent) ## Step 3. Execute Parallel Dispatch Prepend the Context Card to each agent's promp