Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Browser & automation

context-pack

Creates structured handoff briefings between agents. Use when delegating complex work to subagents that would otherwise lose context. Packages task context, constraints, and progress into a compact packet that subagents can consume without re-reading the full conversation. Prevents the 'lost context' problem in multi-agent delegation.

Rune-kit · AI review on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add Rune-kit/rune --skill context-pack

About this skill


name: context-pack description: "Creates structured handoff briefings between agents. Use when delegating complex work to subagents that would otherwise lose context. Packages task context, constraints, and progress into a compact packet that subagents can consume without re-reading the full conversation. Prevents the 'lost context' problem in multi-agent delegation." user-invocable: false metadata: author: runedev version: "0.3.0" layer: L3 model: haiku group: state tools: "Read, Glob, Grep"

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 state from prior sessions
  • plan (L2): phase files with task breakdowns

Workflow

  1. COLLECT — Gather context from the current conversation:

    • Task description and user intent (verb-led behavioral phrasing)
    • Decisions already made (and WHY)
    • Constraints and hard-stops
    • Failed attempts (what NOT to do)
    • Files already read or modified
    • Current progress state
    • Type Surface — types / function signatures / contracts that callers cross. These are the durable spine of the brief.
  2. COMPRESS — Reduce to essential information:

    • Strip conversational noise
    • Deduplicate repeated context
    • Prioritize by relevance to the delegated task
    • Target: <500 tokens for simple tasks, <1500 tokens for complex
  3. STRUCTURE — Format as a context packet (v2 — see Output Format and references/brief-template.md)

  4. VALIDATE — Check packet completeness:

    • Does it include the task goal?
    • Does it include constraints that could cause failure?
    • Does it include what was already tried?
    • Does it include ### Out of scope? (mandatory)
    • Does it include ### Type Surface (mandatory if task >= 300 tokens)?
    • Is it small enough for the target agent's context budget?
  5. PHASE 4.5 — SMELL TESTS — Run mechanical regex gates before emit. See references/durability-rules.md.

    RegexTierReason
    \b\S+\.[a-z]{1,4}:\d+\bBLOCKfile:line reference (e.g., login.ts:42) — line numbers go stale
    ^- \S*[\\/]\S+\.(ts|js|py|go|rs|java)\b outside ### Files TouchedBLOCKPath-only bullet in narrative
    \b(line |on line )\d+\bBLOCK"line 42" / "on line 100"
    \b(src|lib|app)/\S+ in narrative paragraphsWARNPath mention; verify it belongs in Files Touched section
  6. EMIT — Send the validated packet to the receiving agent.

Output Format (v2)

## Context Packet

**Task**: [One-line behavioral description, verb-led]
**Parent**: [delegating skill]
**Scope**: [type names / module names — NOT file paths]

### Decisions Made
- [Decision]: chose [X] over [Y] because [reason]

### Constraints
- MUST: [behavioral assertion]
- MUST NOT: [behavioral prohibition]
- BLOCKED BY: [contract dependency, not file path]

### Already Tried
- [approach] — [observable failure mode]

### Type Surface (durable)
- `TypeName { field: type }` — [what it represents]
- `Module.method(input: T): Result<O, E>` — [contract]

### Files Touched (locator-only, may rename)
- `path/to/file.ts` (TypeName, Module.method) — [behavioral hint]

### Acceptance Criteria
- [ ] [verb-led testable statement starting with: accepts, rejects, produces, notifies, persists, retries, times-out, validates, returns, dispatches, redirects, throws, logs, increments, decrements, retrieves, emits, caches, invalidates, authenticates]
- [ ] ...

### Out of scope
- [Thing the receiver should NOT do]
- (or "(none)" if explicitly empty)

### Progress
- [partial state if mid-handoff — omit if fresh start]

Full template + worked examples: references/brief-template.md.

Variant: Agent Brief (Async / Durable Handoff)

The standard packet (above) is for immediate sub-agent dispatch in the same session. When the handoff target is async — issue tracker, scheduled cron agent, rune:autopilot (Pro) for multi-session work, or any receiver that may execute hours or days

Read the complete source ↗