rune-context-pack

Creates structured context packets for delegating tasks between agents without losing decisions or constraints.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/dangvu008/VietTruyen --skill rune-context-pack-dangvu008
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rune-context-pack
Source: https://github.com/dangvu008/VietTruyen/tree/main/.agents/skills/rune-context-pack
Command: npx skills add https://github.com/dangvu008/VietTruyen --skill rune-context-pack-dangvu008

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When a parent agent delegates work to a subagent, critical context gets lost — the subagent starts fresh without knowing what was tried, what failed, or which constraints apply. This Skill compresses task context, decisions, and constraints into a compact, parseable handoff packet that subagents can consume without re-reading the full conversation. ## Core Features & Use Cases - Structured Handoff Packets: Collects task goals, decisions, constraints, failed attempts, and type surfaces, then compresses them into a packet under 2000 tokens. - Durability Enforcement: Runs regex-based smell tests that block stale file:line references and require durable type/contract names, a mandatory Out of scope section, and behavior-verb acceptance criteria. - Use Case: Before a cook or team workflow spawns subagents for parallel workstreams, generate a context packet so each subagent knows the goal, the constraints, and what was already tried — preventing repeated mistakes and constraint violations. ## Quick Start Create a context packet for handing off the login rate-limiting task to a subagent, including decisions made, constraints, and acceptance criteria.

Frequently Asked Questions about rune-context-pack

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I hand off a task to a subagent without losing context?

Generate a context packet that compresses the task goal, decisions made, constraints, failed attempts, and type surface into a structured markdown brief under 2000 tokens. The packet is injected into the subagent's system prompt so it starts with full context.

What should a context packet for agent delegation include?

A valid packet includes a verb-led task description, decisions with reasons, MUST/MUST NOT constraints, already-tried approaches, a Type Surface of durable contracts, annotated files touched, behavior-verb acceptance criteria, and a mandatory Out of scope section.

Why are file:line references blocked in handoff briefs?

File paths and line numbers go stale after refactors, causing subagents to grep for moved code or hallucinate edits. Regex smell tests block patterns like login.ts:42 and require durable type and function names instead.

When is the Type Surface section optional in a context packet?

Type Surface is optional only for single-cycle short tasks under 300 tokens and fewer than 3 files, where the brief lives for one cycle. For any task at or above 300 tokens, the section is mandatory and missing it blocks emission.

What are the limitations of context packets for delegation?

Packets must stay under 2000 tokens and cannot include full file contents, so very large tasks require aggressive compression. The skill only produces handoff briefs — it does not implement code, run tests, or modify files.