Skip to content
Development
Skill

/archive

Archive the active Maestro session while preserving the shared state layout

From plugin
maestro-orchestrate
45359 skills72 agents4 hooks1 MCP
Install
$ npx -y skills add josstei/maestro-orchestrate --skill archive --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/archive

Context preview

The summary Claude sees to decide when to auto-load this skill.

Archive the active Maestro session while preserving the shared state layout

SKILL.md

archive.SKILL.md
name: archive
description: Archive the active Maestro session while preserving the shared state layout

Maestro Archive

Call `get_skill_content` with resources: ["architecture"].

Workflow

1. Check for an active session; if none exists, inform the user there is nothing to archive 2. Present a brief summary of what will be archived (session ID, task, phase progress) 3. Ask the user to confirm archival (the session may have incomplete phases) 4. Move the active session file into the state archive directory 5. Move the associated design and implementation plan files into the plans archive directory 6. Verify that no active-session file remains and report the archived paths

Constraints

  • Do not delete plan or session history
  • Preserve the existing archive directory structure
Ships withmaestro-orchestrate

Maestro is a multi-agent development orchestration platform with 39 specialists, an Express path for simple work, a 4-phase standard workflow for medium and complex work, persistent session state, and standalone

Get the whole plugin