Plan how Squad agents separate current tasks, summarized history, and lasting reference knowledge so each launch receives relevant context. The skill provides loading rules and prompt templates; the supporting runtime is still a design proposal.
中文简介正在准备中。当前显示英语简介。
Three-tier agent memory model (hot/cold/wiki) for context reduction per spawn
安装前可以查看交给 AI 代理的指令内容。
Status (v0.10.0): This skill describes a design proposal, not a shipped runtime. Skill files install via
squad init/upgrade, but the underlying tier scaffolding (.squad/memory/hot/,cold/,wiki/), Scribe promotion logic, and spawn-template tier-aware reads are tracked in bradygaster/squad#1264. Until those land, agents continue to load fullhistory.md+decisions.mdon every spawn.
Squad agents today load their full context history on every spawn, which grows unboundedly across sessions. The Tiered Agent Memory model proposes a three-tier separation so agents only load the bytes that are actually relevant to the current task, with older context kept available on demand.
--include-cold in spawn template or add ## Cold Memory section.--include-wiki or reference specific wiki doc paths in spawn template.| Situation | Hot | Cold | Wiki |
|---|---|---|---|
| New task, no prior context needed | ✅ | ❌ | ❌ |
| Resuming interrupted work | ✅ | ✅ | ❌ |
| Debugging a recurring issue | ✅ | ✅ | ❌ |
| Implementing against a spec/ADR | ✅ | ❌ | ✅ |
| Onboarding to unfamiliar subsystem | ✅ | ❌ | ✅ |
| Post-incident review | ✅ | ✅ | ✅ |
The default spawn prompt should include Hot tier only:
## Memory Context
### Hot (current session)
{hot_context}
Add --include-cold when the task needs history:
## Memory Context
### Hot (current session)
{hot_context}
### Cold (summarized history — load on demand)
See: .squad/memory/cold/{agent-name}.md
Add --include-wiki when the task needs domain knowledge:
## Memory Context
### Hot (current session)
{hot_context}
### Wiki (durable reference)
See: .squad/memory/wiki/{topic}.md
Scribe is the proposed memory coordinator for this system. Once the runtime lands, Scribe will:
Until then, see the Scribe charter for current behavior: .squad/agents/scribe/charter.md
.squad/memory/hot/{agent}.md)--include-cold / --include-wiki flags as needed.squad/memory/wiki/.squad/memory/cold/ with rolling TTLUse this template when spawning any Squad agent. By default it loads Hot tier only. Add optional sections as needed.
{task_description}
{why_this_matters}
Paste current session context here (~2–4KB target):
Current task: {task_description}
Active decisions: {decisions_this_session}
Last actions: {last_3_to_5_actions}
Blockers: {current_blockers_or_none}
Talking to: {current_interlocutor}
--include-cold)Load on demand. Do not inline unless specifically needed.
Summarized cross-session history is at:
.squad/memory/cold/{agent-name}.md
Include when:
To load cold memory, add this section and fetch the file before spawning:
## Cold Memory Summary
{contents_of_.squad/memory/cold/{agent-name}.md}
--include-wiki)Load on demand. Reference specific wiki docs by path.
Wiki entries are at: .squad/memory/wiki/
Include when:
To load wiki, add this section and reference the specific doc:
## Wiki Reference
{contents_of_.squad/memory/wiki/{topic}.md}
If blocked or uncertain:
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Coordinate work across AI agents with shared rules for locating team files, recording decisions and their reasons, and requesting help. It also defines who owns revisions after a reviewer rejects an artifact.
中文简介正在准备中。当前显示英语简介。
Set shared development rules for an agent team: keep specific agent names out of product code, tests, and CI configuration, verify affected tests before finishing, and record lessons learned from mistakes.
中文简介正在准备中。当前显示英语简介。
Routes requests to design, create, update, debug, or upgrade GitHub Agentic Workflows to the appropriate instructions. It helps the agent select a workflow-specific procedure and apply any additional rules defined for the repository.
中文简介正在准备中。当前显示英语简介。
Prepare architecture proposals before implementation so the team can agree on a direction. Organize evidence, technical choices, effects on existing work, risks, and the first release’s scope into a document with clear recommendations and decision owners.
中文简介正在准备中。当前显示英语简介。
Update the gh-aw-firewall version used by gh-aw, rebuild generated files, and review release notes and configuration schemas, which define valid settings. It guides related code and test updates while identifying follow-up work that remains.
中文简介正在准备中。当前显示英语简介。
Review git and gh operations in gh-aw workflows to check credential availability for each repository. Identify missing token handoffs, risky expansions of limited checkouts, and error handling needed where credentials are intentionally unavailable.
中文简介正在准备中。当前显示英语简介。