tiered-memory

Organizes agent context into hot, cold, and wiki memory tiers to reduce spawn payload size.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/codebytes/btt --skill tiered-memory-codebytes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tiered-memory
Source: https://github.com/codebytes/btt/tree/main/.squad/templates/skills/tiered-memory
Command: npx skills add https://github.com/codebytes/btt --skill tiered-memory-codebytes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Squad agents load their full context history on every spawn, producing 34–74KB payloads where 82–96% is stale noise. This Skill defines a three-tier memory model that cuts context size by 20–55% per spawn while keeping relevant history and knowledge available on demand. ## Core Features & Use Cases - Three-Tier Memory Model: Hot tier (~2–4KB, always loaded), Cold tier (~8–12KB, on-demand cross-session summaries), and Wiki tier (durable structured knowledge like ADRs and conventions). - Spawn Template Pattern: Ready-to-use spawn prompt template that defaults to Hot-only loading with --include-cold and --include-wiki flags for selective expansion. - Scribe Integration: Automated tier promotion where the Scribe agent compresses Hot to Cold at session end and promotes Cold to Wiki after 30 days. - Use Case: When resuming interrupted debugging work, spawn an agent with Hot context plus the Cold summary from .squad/memory/cold/{agent-name}.md instead of replaying full transcripts. ## Quick Start Spawn an agent using the provided template with only the Hot memory section filled in, and add the Cold or Wiki sections only when the task requires history or domain knowledge.

Frequently Asked Questions about tiered-memory

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

FAQPage Schema
How do I reduce AI agent context size per spawn?

Split agent memory into three tiers: a small hot tier (2–4KB) loaded by default, a cold tier of summarized history loaded on demand, and a wiki tier of durable knowledge. Production measurements show 20–55% context reduction with hot-only loading.

What is the difference between hot, cold, and wiki memory tiers?

Hot holds current session context and is always loaded. Cold holds summarized cross-session history with a 30-day rolling window, loaded only when tasks need history. Wiki holds permanent structured knowledge like ADRs and conventions, loaded selectively by document path.

When should I include cold memory in an agent spawn?

Include cold memory when resuming interrupted work, debugging a recurring issue, or answering what was tried before. Add the `--include-cold` flag and load the summary from `.squad/memory/cold/{agent-name}.md`, which adds roughly 8–12KB.

How does the Scribe agent manage memory tier promotion?

Scribe compresses hot context into a cold summary at session end, keeping about 10% of session verbosity. After 30 days it promotes stable cold entries into the wiki tier, and agents can request mid-session wiki writes via `scribe:wiki-write`.

What are the limitations of hot-only memory loading?

Hot-only loading discards cross-session history, so tasks needing prior decisions or recurring-issue context will lack that information. You must explicitly add cold or wiki sections for those scenarios, which increases payload size by 2–12KB.