context-pack

# context-pack ## Purpose When a parent agent delegates work to a subagent, critical context gets lost — the subagent starts fresh without knowing what was tried, what failed, what constraints apply, or what the parent already decided. Context-pack solves this by creating structured handoff briefings (context packets) that compress the essential information into a compact, parseable format. The packet is small enough to fit in a subagent's system prompt but complete enough to prevent redundant work and constraint violations. ## Triggers - Called by `cook`, `team`, `rescue` before spawning subagents - Called by any L1/L2 skill that delegates work to another skill - Manual: when user says "hand off", "delegate", "split this task" ## Calls (outbound) - `session-bridge` (L3): read persisted state for inclusion in packet - `context-engine` (L3): check current context budget before deciding packet size ## Called By (inbound) - `cook` (L1): before Phase 2-5 subagent spawning - `team` (L1): before dispatching parallel workstreams - `rescue` (L1): before delegating module-level refactoring - `scaffold` (L1): before delegating component generation - Any L2 skill that spawns subagents ## Data Flow ### Feeds Into → - All subagent invocations: context packet → subagent system prompt - `completion-gate` (L3): packet's success criteria → claim validation baseline ### Fed By ← - Parent agent conversation: decisions, constraints, failed attempts - `session-bridge` (L3): persisted...