team-memory-maintenance
Merge accepted Squad decisions through the active state backend with exact verification
- License 许可
- MIT
- 所属仓库
- github/squad
- 最近更新
- 2026-11-15
- Stars
- ★ 3.4k
- Forks
- 520
01 前言 Front Matter
- name
- team-memory-maintenance
- domain
- squad-internals, decision-management
- source
- retained pre-recast procedure, narrowed to the current Scribe contract
- confidence
- high
- description
- Merge accepted Squad decisions through the active state backend with exact verification
03 SKILL.md 正文
Team Memory Maintenance
Use this skill only for accepted durable decisions. The current Scribe role does not maintain session logs, orchestration logs, specialist histories, onboarding records, or general team memory.
Scope
- Allowed targets:
.squad/decisions/inbox/and.squad/decisions.md. - Use the active state backend for mutable Squad state.
- Preserve decision authorship, rationale, and accepted scope.
- Use archival-integrity procedures whenever accepted records are moved or compacted.
Procedure
- Resolve the supplied team root and configured state backend.
- List and read every candidate inbox entry before acting.
- Merge only decisions that have explicit acceptance evidence.
- Deduplicate exact decision headings without rewriting unrelated decisions.
- Normalize nested headings while preserving relative hierarchy and fenced code blocks.
- Re-read
.squad/decisions.mdand verify the merged content before deleting an inbox entry. - Refetch after deletion and verify the exact inbox entry is absent.
- Stop on any mismatch and report the incomplete operation.
Stop Conditions
- Stop if the team root, active backend, acceptance evidence, or required read-back capability is unavailable.
- Stop if merged content or deletion cannot be verified exactly.
- Do not manufacture a durable record for a tentative request, onboarding observation, or unaccepted recommendation.
Anti-Patterns
- Writing session logs or specialist histories.
- Bypassing the state backend with branch switching, note-ref pushes, resets, or manual persistence.
- Deleting inbox content before verifying the canonical merge.
- Expanding a decision-only maintenance request into product or repository cleanup.
04 同仓库更多 Skills
windows-compatibility
Cross-platform path handling and command patterns
versioning-policy
SemVer rules for Squad's stable, preview, insider, and local package versions
tiered-memory
Three-tier agent memory model (hot/cold/wiki) for context reduction per spawn
test-discipline
Design assertions that prove the actual contract and fail on realistic regressions
squad
Squad's command catalog and interactive menu. Invoke via /squad (slash command) or natural language ("squad commands", "what can squad do", "show me squad options"). Presents categorized operations (Install & Upgrade, Team Management, Issues & PRs, Plugins & Skills, Model & Cost, Sessions & State) as an interactive picker. Routes to the right squad CLI command or the Squad coordinator agent.
squad-version-check
Internals of how @bradygaster/squad-cli stamps its version, how `squad upgrade` works (what it preserves vs overwrites), and how to probe the npm registry for the latest version from a coordinator prompt.