olympus-ai 4.2.0 → 4.4.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "olympus-ai",
3
- "version": "4.2.0",
3
+ "version": "4.4.0",
4
4
  "description": "Olympus: Multi-agent orchestration for Claude Code. Summon the gods of code.",
5
5
  "author": {
6
6
  "name": "mikev10",
package/README.md CHANGED
@@ -27,7 +27,7 @@ Olympus is a multi-agent orchestration system for [Claude Code](https://docs.ant
27
27
  - 📋 **Todo Management** - Tracks progress with real-time updates
28
28
  - 🔄 **Background Execution** - Long-running tasks run async with notifications
29
29
  - 🎯 **Continuation Enforcement** - Never stops until all tasks are complete
30
- - 💬 **19 Slash Commands** - `/ultrawork`, `/plan`, `/ascent`, `/continue`, `/review`, and more
30
+ - 💬 **20 Slash Commands** - `/ultrawork`, `/plan`, `/ascent`, `/continue`, `/review`, and more
31
31
  - 🔮 **AI-DLC Workflow** - Inception → Construction → Operations pipeline for structured development
32
32
  - 🌐 **Language Agnostic** - Works with any tech stack: Python, .NET, Go, Rust, Java, and more
33
33
  - 🔮 **Magic Keywords** - Natural language triggers for enhanced modes
@@ -69,7 +69,7 @@ Olympus transforms Claude Code from a single agent into a **pantheon of speciali
69
69
 
70
70
  - **Zero Configuration** - Works out-of-the-box with sensible defaults
71
71
  - **Works Everywhere** - Not tied to any language or framework — orchestrates across .NET, Python, Go, Rust, Java, and any codebase
72
- - **Slash Commands** - 19 slash commands (`/ultrawork`, `/plan`, `/ascent`, `/continue`)
72
+ - **Slash Commands** - 20 slash commands (`/ultrawork`, `/plan`, `/ascent`, `/continue`)
73
73
  - **Magic Keywords** - Natural language triggers for enhanced modes
74
74
 
75
75
  ### 📊 Olympus vs. Manual Claude Usage
@@ -168,6 +168,7 @@ claude
168
168
  | `/deepsearch <query>` | Thorough multi-strategy codebase search |
169
169
  | `/analyze <target>` | Deep analysis and investigation |
170
170
  | `/complete-plan [path]` | Verify and complete a plan after implementation |
171
+ | `/archive [id\|--all]` | Archive completed AI-DLC workflows to aidlc-docs/completed/ |
171
172
  | `/continue` | Resume an active AI-DLC workflow from last checkpoint |
172
173
  | `/retro` | Run a guardrail retrospective on the current AI-DLC workflow |
173
174
  | `/workflow-status` | View all active structured workflows and their status |
@@ -24,7 +24,7 @@ export declare const HOOKS_DIR: string;
24
24
  export declare const SETTINGS_FILE: string;
25
25
  export declare const VERSION_FILE: string;
26
26
  /** Current version - MUST match package.json */
27
- export declare const VERSION = "4.2.0";
27
+ export declare const VERSION = "4.4.0";
28
28
  /** Installation result */
29
29
  export interface InstallResult {
30
30
  success: boolean;
@@ -40,7 +40,7 @@ export const HOOKS_DIR = join(CLAUDE_CONFIG_DIR, 'hooks');
40
40
  export const SETTINGS_FILE = join(CLAUDE_CONFIG_DIR, 'settings.json');
41
41
  export const VERSION_FILE = join(CLAUDE_CONFIG_DIR, '.olympus-version.json');
42
42
  /** Current version - MUST match package.json */
43
- export const VERSION = '4.2.0';
43
+ export const VERSION = '4.4.0';
44
44
  /**
45
45
  * Read a content file from the resources/ directory.
46
46
  *
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "olympus-ai",
3
- "version": "4.2.0",
3
+ "version": "4.4.0",
4
4
  "description": "Olympus: Multi-agent orchestration for Claude Code. Summon the gods of code.",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",
@@ -0,0 +1,65 @@
1
+ ---
2
+ description: Archive completed AIDLC workflows to aidlc-docs/completed/
3
+ ---
4
+
5
+ # Archive Completed Workflows
6
+
7
+ $ARGUMENTS
8
+
9
+ Archive completed AIDLC workflows by moving them from `aidlc-docs/{workflowId}/` to `aidlc-docs/completed/{workflowId}/`.
10
+
11
+ ## Step 1: Scan for Workflows
12
+
13
+ List all directories under `aidlc-docs/` (excluding the `completed/` directory). For each directory that contains a `checkpoint.json`, read the checkpoint and classify:
14
+
15
+ - **Archivable**: `status` is `"complete"` AND the workflow is NOT already inside `aidlc-docs/completed/`
16
+ - **Active**: `status` is NOT `"complete"` and NOT `"archived"`
17
+ - **Already archived**: Located in `aidlc-docs/completed/` or has `archived_path` set
18
+
19
+ ## Step 2: Parse Arguments
20
+
21
+ - **No arguments**: List all archivable workflows and ask the user which to archive (or offer `--all`)
22
+ - **`--all`**: Archive all archivable workflows without prompting
23
+ - **`<workflow-id>`**: Archive only the specified workflow (must be archivable)
24
+
25
+ If no archivable workflows are found, report: "No completed workflows to archive. Active workflows must reach completion before archiving."
26
+
27
+ ## Step 3: Archive Each Selected Workflow
28
+
29
+ For each workflow to archive:
30
+
31
+ 1. **Create target directory**: `aidlc-docs/completed/{workflowId}/`
32
+ 2. **Read the checkpoint**: Load `aidlc-docs/{workflowId}/checkpoint.json`
33
+ 3. **Stamp archival metadata** on the checkpoint:
34
+ - Set `archived_at` to current ISO 8601 timestamp
35
+ - Set `archived_path` to `aidlc-docs/completed/{workflowId}`
36
+ 4. **Write the updated checkpoint** back to the source location
37
+ 5. **Move the entire workflow directory** from `aidlc-docs/{workflowId}/` to `aidlc-docs/completed/{workflowId}/`
38
+ 6. **Update master plan** (best-effort): If `.olympus/plans/{workflowId}-plan.md` exists, append a note:
39
+ ```
40
+ ---
41
+ _This workflow was archived to `aidlc-docs/completed/{workflowId}/` on {archived_at}_
42
+ ```
43
+ 7. **Update CLAUDE.md** (best-effort): If the project `.claude/CLAUDE.md` references this workflow as the active workflow, remove or comment out that reference since it is no longer active.
44
+
45
+ ## Step 4: Report Results
46
+
47
+ Display a summary table:
48
+
49
+ ```
50
+ Archived workflows:
51
+ | Workflow | Feature | Archived To |
52
+ |----------|---------|-------------|
53
+ | {id} | {name} | aidlc-docs/completed/{id}/ |
54
+
55
+ {count} workflow(s) archived successfully.
56
+ ```
57
+
58
+ If any archival failed, report the error but continue with remaining workflows.
59
+
60
+ ## Edge Cases
61
+
62
+ - **Workflow not found**: Report "Workflow '{id}' not found in aidlc-docs/"
63
+ - **Workflow not complete**: Report "Workflow '{id}' has status '{status}' — only completed workflows can be archived"
64
+ - **Already archived**: Report "Workflow '{id}' is already archived at aidlc-docs/completed/{id}/"
65
+ - **Move failure on Windows**: If the move fails with EBUSY, suggest closing any open files in the workflow directory