Individual skill
state-management
Managing shared context, memory, and state across multiple agents.
gemini-extension/design-agent-orchestration/skills/state-management/SKILL.md
Source commit f41b650435b62dec6d5b1dc3598ac4679f8b7ae7
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 7, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 202
- Repository last updated
- Jun 9, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 6,168 bytes
Read excerpt
# State Management
In a multi-agent system, state is the shared truth about what's happened, what's in progress, and what's been decided. Without state management, agents work with stale or conflicting information — and the user pays the cost in repeated questions, contradictory answers, and lost progress.
State management is the *plumbing* skill of multi-agent design. Get it wrong and every other skill in this plugin gets harder.
## Types of state
- **Task state**: where the overall task is in its lifecycle. Which subtasks are complete, in progress, or pending.
- **Context state**: what each agent knows. What has been shared, summarised, or dropped.
- **User state**: preferences, history, and current emotional state.
- **Decision state**: decisions made, options considered, options rejected (and why).
- **Error state**: what has failed, been retried, been escalated.
## State architecture patterns