decommission-meta-project
Skill0 starsChanged yesterdayMITView on GitHub
Safely decommission, prune, or hibernate agent team roles (.agents/team/): performs non-destructive archiving into .agents/team/archive/, finalizes telemetry, synchronizes root AGENTS.md, and reassigns orphaned tasks without data loss.
- Deletes or force-pushes
In this repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- templates/AGENTS.mdAGENTS.md
- ground-meta-projectSkill
- init-meta-projectSkill
- manage-meta-projectSkill
- record-observationSkill
- scan-meta-projectSkill
- sync-architectureSkill
- tune-meta-projectSkill
- update-meta-projectSkill
- decommission-meta-projectSkill
- ground-meta-projectSkill
- init-meta-projectSkill
- manage-meta-projectSkill
- record-observationSkill
- scan-meta-projectSkill
- sync-architectureSkill
- tune-meta-projectSkill
- update-meta-projectSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 1 is distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 28
Before performing any file operations:
- Very specific: line 33
Read .agents/meta-project.json and enumerate every binding that references the target role, per installation.
- Very specific: line 38
Verify integrity after changes: python scripts/verify_identity.py --check must pass (0 errors) — a dangling profile_path or stale binding …
- Very specific: line 51
Ensure target directory .agents/team/archive/ exists.
- Very specific: line 54
Remove the decommissioned role's link and description from Section ## 7.
- Very specific: line 88
Leave root AGENTS.md and .agents/project_knowledge/ slices intact as the repository's permanent collective memory.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Agent Team Decommissioning and Archival (Meta-Project Decommission)
Autonomous skill for safe, non-destructive decommissioning, resizing, and archiving of specialized agent roles in .agents/team/.
Adheres to the core zero-data-loss invariant: physical deletion (rm, Remove-Item) of role workspaces is strictly prohibited. Accumulated context in private notes.md and historical telemetry in profile.md are atomically preserved via archiving into .agents/team/archive/<role_id>/.
When to invoke skill
- The user requests: "decommission team", "archive agent X", "sunset role X", "hibernate agent team", "prune inactive roles", "prepare team for re-deployment", "сверни команду", "законсервируй агентов", "выведи роль X", "удали агента X из проекта".
- Project undergoes technology deprecation (e.g., Docker decommissioned, frontend removed, or team resized to Compact Trio).
- Repository enters long-term maintenance or dormant hibernation mode.
Execution steps
Phase 0: Safety & Scope Verification
Before performing any file operations:
- Scan active role directories in
.agents/team/(excludingarchive/). - Confirm the target roles to decommission with the user (unless an explicit full reset was commanded).
- Core Invariant (Zero Data Loss): Under no circumstances may an agent execute destructive deletion (
rm -rf,Remove-Item -Recurse) on role workspaces. Workspaces must always be preserved via atomic relocation to.agents/team/archive/. - Registry-Aware Decommissioning (multi-harness model):
- Read
.agents/meta-project.jsonand enumerate every binding that references the target role, per installation. - Distinguish two different operations:
- (A) Disable ONE installation's binding (e.g. disconnecting ZCode while Antigravity keeps working): set that binding's
statusto"disabled"in the registry and archive ONLY the installation-specific profile copy (e.g..agents/team/<role_id>-<installation_suffix>/) if one exists. The shared role, other bindings, other installations' profiles, notes, and telemetry stay untouched. - (B) Archive the SHARED role: allowed ONLY when NO other
activeorplannedinstallation still references the role. If any other installation references it, REFUSE with an explicit report listing the referencing installations and offer operation (A) instead.
- (A) Disable ONE installation's binding (e.g. disconnecting ZCode while Antigravity keeps working): set that binding's
- Apply registry changes, the
AGENTS.mdSection 7 roster, and the archive relocation CONSISTENTLY in one pass; preserve memory and historical authorship (profile.mdtelemetry,notes.md) byte-for-byte. - Verify integrity after changes:
python scripts/verify_identity.py --checkmust pass (0 errors) — a danglingprofile_pathor stale binding is a failed decommission.
- Read
Scenario A: Targeted Role Sunsetting (Single Role Pruning)
Used when a single technology layer or specialization is retired from the project.
- Telemetry Closeout:
Append a closing entry to
.agents/team/<role_id>/profile.mdin the telemetry table:| <YYYY-MM-DD> | User | Decommissioning / Sunsetting | Role archived into .agents/team/archive/<role_id>/ | - Directory Archival:
- Ensure target directory
.agents/team/archive/exists. - Atomically move
.agents/team/<role_id>/to.agents/team/archive/<role_id>/.
- Ensure target directory
- Passport Synchronization (
AGENTS.md):- Remove the decommissioned role's link and description from Section
## 7. Project Agent Team & Multi-Harness Identity (.agents/team/)in rootAGENTS.md.
- Remove the decommissioned role's link and description from Section
- Orphaned Tasks Reassignment:
- Scan
.agents/project_knowledge/tasks.md. - Reassign any pending subtasks delegated to this role to the default generalist (
agent-general-worker/agent-dev-lead) or mark them as[CANCELLED].
- Scan
- Observation Logging:
- Record the role sunsetting fact into
.agents/project_knowledge/observations.mdviarecord-observation.
- Record the role sunsetting fact into
Scenario B: Team Resizing & Re-deployment Reset (Batch Archival)
Used when transitioning from a bloated team to a Scale-Adaptive Compact Trio, or rotating team structure.
- Batch Telemetry Closeout:
For every active role in
.agents/team/, append a transition entry inprofile.md:| <YYYY-MM-DD> | User | Decommissioning / Resizing | Archived during team re-deployment and sizing calibration | - Batch Archival Relocation:
- Ensure
.agents/team/archive/exists. - Move all active role directories from
.agents/team/<role_id>/into.agents/team/archive/<role_id>/. (If a role with the same ID already exists in archive, append timestamp suffix:.agents/team/archive/<role_id>-<YYYYMMDD>/).
- Ensure
- Passport Section Reset:
- In root
AGENTS.md, clear the decommissioned entries under## 6. Project Agent Team (.agents/team/)to prepare for the new synthesized team.
- In root
- Tasks Quarantine:
- In
.agents/project_knowledge/tasks.md, close or quarantine active tasks from the prior team cycle.
- In
- Report & Handoff:
- Report archival completion to the user. The repository is now clean and ready for
manage-meta-projectto materialize the new synthesized team.
- Report archival completion to the user. The repository is now clean and ready for
Scenario C: Full Repository Hibernation (Dormant Mode)
Used when active development concludes and the repository transitions into a dormant maintenance state.
- Execute Scenario B steps to archive all active roles into
.agents/team/archive/. - Leave root
AGENTS.mdand.agents/project_knowledge/slices intact as the repository's permanent collective memory. - Inform the user:
"All agent roles have been safely hibernated into
.agents/team/archive/. Static project memory and knowledge slices remain active. Re-activate anytime viaskills/manage-meta-project/SKILL.md."
Phase Final: Decommissioning Report
Upon completing any scenario, output a concise status table:
| Decommissioned Role | Archive Destination Path | Unfinished Tasks Handled | Status |
| :--- | :--- | :--- | :--- |
| `agent-deep-auditor` | `.agents/team/archive/agent-deep-auditor/` | Reassigned / None | Archived |
| `agent-qa-engineer` | `.agents/team/archive/agent-qa-engineer/` | Reassigned / None | Archived |Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

