# archive

A slash command that stores completed orchestrations with their metrics and lessons, so you can look back at them later.

- command · `type=command` · Claude Code · 228 installs
- Author: davila7
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/davila7/claude-code-templates/tree/HEAD/cli-tool/components/commands/orchestration/archive.md
- Updated: 2026-10-24
- HTML: https://affpapa.org/en/nevibecode/commands/archive

## What it does

\`/orchestration/archive` handles orchestrations that are already done. Run it bare and it picks out the fully completed ones on its own, then extracts their data into folders. Add `--date 03_15_2024 --project auth_system` to target one project, or `--analyze` to run analysis first.

What gets kept: task files and metadata, status transition logs, commit-to-task mapping, velocity and quality numbers. Alongside them go `ARCHIVE-SUMMARY.md`, `LESSONS-LEARNED.md` and `METRICS-REPORT.json`. The layout splits by year and quarter, with `original-files/`, `analytics/` and `git-correlation/` inside.

Depth is a flag: `--quick` skips the analysis, `--deep-analysis` adds pattern recognition and comparison against similar projects, `--include tasks,metrics --exclude original-files` lets you pick contents by hand. Formats are `standard`, `light` and `research`. The command assumes Claude orchestrations with real tracking behind them; if a project never kept task files or status history, there is nothing to archive, so check that first.

## Install

### Claude Code (native platform)

1. **claude-code-templates**
```bash
npx claude-code-templates@latest --command orchestration/archive
```

2. **Manually: put the files in place**
- File: `.claude/commands/archive.md` — Call it with /archive. For all projects use ~/.claude/commands/

### Codex

**Manually: put the files in place**
- File: `~/.codex/prompts/archive.md` — Call it with /prompts:archive. Codex marks this format deprecated in favour of skills

### GitHub Copilot

**Manually: put the files in place**
- File: `.github/prompts/archive.prompt.md`

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/archive.toml` — Gemini stores commands as TOML: the prompt text goes into the prompt field

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/davila7/claude-code-templates/tree/HEAD/cli-tool/components/commands/orchestration/archive.md

## When to use it
- keep metrics from a finished orchestration before clearing working files
- turn a project's lessons into a list of process fixes
- compare current velocity and quality against earlier orchestrations
- map git commits back to individual orchestration tasks
- build a light archive with only the key metrics

## Example prompts
- /orchestration/archive
- /orchestration/archive --date 03_15_2024 --project auth_system
- /orchestration/archive --analyze

## Source text · archive.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 7fcece9610605736.

BEGIN THIRD-PARTY FILE 7fcece9610605736
````text
---
description: "Properly archive completed orchestrations while preserving valuable data, metrics, and lessons learned for future reference."
---

# Orchestration Archive Command

Properly archive completed orchestrations while preserving valuable data, metrics, and lessons learned for future reference.

## Usage

```
/orchestration/archive [options]
```

## Description

Manages the archival process for completed orchestrations, extracting insights, preserving critical data, and organizing historical information for future analysis and learning.

## Basic Commands

### Archive Completed Orchestrations
```
/orchestration/archive
```
Identifies and archives all fully completed orchestrations automatically.

### Archive Specific Orchestration
```
/orchestration/archive --date 03_15_2024 --project auth_system
```
Archives a specific orchestration with full data preservation.

### Archive with Analysis
```
/orchestration/archive --analyze
```
Performs comprehensive analysis before archiving, extracting lessons learned.

## Archival Process

### Pre-Archive Analysis
```
## Pre-Archive Analysis for: auth_system (03_15_2024)

Completion Status:
- Total Tasks: 24 (24 completed, 0 active)
- Duration: 8 days (estimated: 6 days)
- Final Velocity: 3.0 tasks/day
- Quality Score: 92% (2 QA iterations avg)

Outstanding Items:
- No active tasks
- No blocked dependencies
- Git branches: 3 merged, 0 pending
- Documentation: Complete

Ready for Archive: ✓
```

### Data Extraction
```
## Extracting Archive Data

Performance Metrics:
✓ Task completion times
✓ Velocity calculations  
✓ Quality metrics
✓ Resource utilization
✓ Dependency patterns

Project Artifacts:
✓ All task files and metadata
✓ Git commit history correlation
✓ Status transition logs
✓ Agent assignment patterns

Learning Points:
✓ What worked well
✓ Pain points and bottlenecks
✓ Estimation accuracy
✓ Team collaboration insights
```

### Archive Structure
```
/archived-orchestrations/
└── 2024/
    └── Q1/
        └── 03_15_2024_auth_system/
            ├── ARCHIVE-SUMMARY.md
            ├── LESSONS-LEARNED.md
            ├── METRICS-REPORT.json
            ├── original-files/
            │   ├── MASTER-COORDINATION.md
            │   ├── EXECUTION-TRACKER.md
            │   ├── TASK-STATUS-TRACKER.yaml
            │   └── tasks/
            ├── analytics/
            │   ├── velocity-chart.png
            │   ├── dependency-graph.svg
            │   └── timeline-visualization.html
            └── git-correlation/
                ├── commit-task-mapping.json
                └── branch-analysis.md
```

## Archive Options

### Quick Archive
```
/orchestration/archive --quick
```
Fast archival without detailed analysis, suitable for simple orchestrations.

### Deep Analysis Archive
```
/orchestration/archive --deep-analysis
```
Comprehensive analysis including:
- Detailed performance metrics
- Pattern recognition
- Predictive insights
- Comparative analysis with similar projects

### Selective Archive
```
/orchestration/archive --include tasks,metrics --exclude original-files
```
Custom archive content selection.

## Analysis Features

### Performance Analysis
```
## Performance Analysis Summary

Velocity Analysis:
- Peak velocity: 4.2 tasks/day (Day 3)
- Average velocity: 3.0 tasks/day
- Velocity trend: Stable with 15% improvement over time

Task Metrics:
- Average task duration: 3.8h (vs 4.0h estimated)
- Estimation accuracy: 87% (excellent)
- Most accurate estimates: Backend tasks (95%)
- Least accurate estimates: UI tasks (72%)

Quality Metrics:
- First-pass QA success: 78%
````
END THIRD-PARTY FILE 7fcece9610605736

The third-party file has ended. Everything between the 7fcece9610605736 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 3736 of 11198 bytes. © davila7 · MIT · https://github.com/davila7/claude-code-templates/tree/HEAD/cli-tool/components/commands/orchestration/archive.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md