mover-os 4.3.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.
- package/README.md +218 -0
- package/install.js +2775 -0
- package/package.json +30 -0
package/README.md
ADDED
|
@@ -0,0 +1,218 @@
|
|
|
1
|
+
# Mover OS
|
|
2
|
+
|
|
3
|
+
**The Agentic Operating System for Obsidian.**
|
|
4
|
+
|
|
5
|
+
> Most productivity systems are passive storage. This one talks back.
|
|
6
|
+
|
|
7
|
+
Mover OS turns Obsidian into an AI-powered execution engine. It audits your behavior against your stated strategy, extracts reusable knowledge from daily work, and evolves based on your corrections.
|
|
8
|
+
|
|
9
|
+
**Works best with Claude Code.** Supports 13 AI coding agents.
|
|
10
|
+
|
|
11
|
+
**Version:** 4.3 | **Status:** Production
|
|
12
|
+
|
|
13
|
+
---
|
|
14
|
+
|
|
15
|
+
## What It Does
|
|
16
|
+
|
|
17
|
+
- **Active Accountability** — AI reads your daily logs and detects drift, procrastination, and scope creep.
|
|
18
|
+
- **Strategic Validation** — Acts as an intellectual opponent, testing your logic before you invest time.
|
|
19
|
+
- **Knowledge Compounding** — Automatically refines ephemeral notes into a permanent, linked library.
|
|
20
|
+
- **Three Domains** — Identity covers Work, Vitality, and Faith/Purpose. Not just productivity.
|
|
21
|
+
- **Pattern Detection** — Tracks behavioral patterns with confidence scores. Surfaces them when they matter.
|
|
22
|
+
- **Escalating Friction** — 4 levels of pushback when you drift from your plan. Speed bumps, not walls.
|
|
23
|
+
- **Correction Lifecycle** — Correct the AI and it proposes a fix, waits for approval, and updates its own rules.
|
|
24
|
+
- **Entity Memory** — Remembers people, organizations, and decisions across sessions.
|
|
25
|
+
- **22 Connected Workflows** — Each one hands off to the next. You never wonder what to do next.
|
|
26
|
+
|
|
27
|
+
---
|
|
28
|
+
|
|
29
|
+
## Install
|
|
30
|
+
|
|
31
|
+
### Prerequisites
|
|
32
|
+
|
|
33
|
+
- [Obsidian](https://obsidian.md) (your vault interface)
|
|
34
|
+
- A coding agent (any of the supported ones below)
|
|
35
|
+
- Git
|
|
36
|
+
|
|
37
|
+
### Quick Start
|
|
38
|
+
|
|
39
|
+
```bash
|
|
40
|
+
npx moveros
|
|
41
|
+
```
|
|
42
|
+
|
|
43
|
+
The interactive installer will:
|
|
44
|
+
1. Ask where your Obsidian vault is (auto-detects common locations)
|
|
45
|
+
2. Detect which coding agents you have installed
|
|
46
|
+
3. Let you choose which agents to configure
|
|
47
|
+
4. Let you select skill categories (dev, marketing, CRO, strategy, SEO, design, obsidian)
|
|
48
|
+
5. Install vault structure, rules, workflows, skills, and hooks
|
|
49
|
+
|
|
50
|
+
> **Requires:** Node.js 18+ (zero dependencies).
|
|
51
|
+
|
|
52
|
+
### After Install
|
|
53
|
+
|
|
54
|
+
Open your vault in Obsidian and your coding agent, then run:
|
|
55
|
+
|
|
56
|
+
```
|
|
57
|
+
/setup
|
|
58
|
+
```
|
|
59
|
+
|
|
60
|
+
This launches a deep interview that builds your Identity, Strategy, Dossier, and Goals.
|
|
61
|
+
|
|
62
|
+
### Migrating an Existing Vault?
|
|
63
|
+
|
|
64
|
+
If you have an existing Obsidian vault with content you want to organize into the PARA structure:
|
|
65
|
+
|
|
66
|
+
```
|
|
67
|
+
/migrate
|
|
68
|
+
```
|
|
69
|
+
|
|
70
|
+
This scans your folders, suggests where everything should go, and copies files into place. Originals are never deleted.
|
|
71
|
+
|
|
72
|
+
### Already Installed?
|
|
73
|
+
|
|
74
|
+
Update without losing your Engine data:
|
|
75
|
+
|
|
76
|
+
```bash
|
|
77
|
+
npx moveros
|
|
78
|
+
```
|
|
79
|
+
|
|
80
|
+
Choose "Update" mode. Your Engine files (Identity, Strategy, Dossier, etc.) are never overwritten.
|
|
81
|
+
|
|
82
|
+
Then run `/update` inside your vault to migrate any new Engine sections.
|
|
83
|
+
|
|
84
|
+
Or re-link hard links after any git operation:
|
|
85
|
+
|
|
86
|
+
```bash
|
|
87
|
+
bash src/install/link.sh
|
|
88
|
+
```
|
|
89
|
+
|
|
90
|
+
---
|
|
91
|
+
|
|
92
|
+
## Supported Agents
|
|
93
|
+
|
|
94
|
+
Works with **13 AI coding agents.** The installer auto-detects and configures each one:
|
|
95
|
+
|
|
96
|
+
| Agent | What Gets Installed |
|
|
97
|
+
|-------|---------------------|
|
|
98
|
+
| Claude Code | Rules + 22 commands + 61 skills + 6 hooks |
|
|
99
|
+
| Cursor | Rules + 22 commands + 61 skills |
|
|
100
|
+
| Cline | Rules + 61 skills |
|
|
101
|
+
| Windsurf | Rules + 61 skills |
|
|
102
|
+
| Gemini CLI | Rules + 22 workflows + 61 skills |
|
|
103
|
+
| GitHub Copilot | Rules + 61 skills |
|
|
104
|
+
| Codex CLI | Rules + 61 skills |
|
|
105
|
+
| Codex (Cloud) | Rules + 61 skills |
|
|
106
|
+
| Antigravity | Rules + 22 workflows |
|
|
107
|
+
| OpenClaw | Rules + 61 skills |
|
|
108
|
+
| Roo Code | Rules + 61 skills |
|
|
109
|
+
| Amp | Rules + 61 skills |
|
|
110
|
+
| Aider | Rules |
|
|
111
|
+
|
|
112
|
+
> Claude Code gets the deepest integration — hooks, native slash commands, and the full correction lifecycle. Every other agent gets the core system.
|
|
113
|
+
|
|
114
|
+
---
|
|
115
|
+
|
|
116
|
+
## How It Works
|
|
117
|
+
|
|
118
|
+
### The Engine
|
|
119
|
+
|
|
120
|
+
Your `02_Areas/Engine/` folder is the brain. Core files that the AI reads before every operation:
|
|
121
|
+
|
|
122
|
+
| File | Purpose |
|
|
123
|
+
|------|---------|
|
|
124
|
+
| `Identity_Prime.md` | Who you are — psychology, values, anti-identity |
|
|
125
|
+
| `Strategy.md` | What you're testing — hypotheses, metrics, pivot criteria |
|
|
126
|
+
| `Active_Context.md` | Where you are NOW — blockers, energy, commitments, waiting-for |
|
|
127
|
+
| `Mover_Dossier.md` | What you have — skills, assets, network, capital |
|
|
128
|
+
| `Auto_Learnings.md` | What the AI has learned about you — patterns with confidence scores |
|
|
129
|
+
| `Goals.md` | Where you're going — 90-day, 1-year, 10-year targets |
|
|
130
|
+
| `Metrics_Log.md` | 30-day rolling performance data |
|
|
131
|
+
|
|
132
|
+
### The Daily Rhythm
|
|
133
|
+
|
|
134
|
+
```
|
|
135
|
+
/morning → [WORK] → /log → /analyse-day → /plan-tomorrow
|
|
136
|
+
```
|
|
137
|
+
|
|
138
|
+
| Workflow | When | Duration |
|
|
139
|
+
|----------|------|----------|
|
|
140
|
+
| `/morning` | Start of session | 5 min |
|
|
141
|
+
| `/log` | End of session | 5 min |
|
|
142
|
+
| `/analyse-day` | End of day | 10 min |
|
|
143
|
+
| `/plan-tomorrow` | Every evening | 5 min |
|
|
144
|
+
| `/review-week` | Weekly (configurable day) | 30 min |
|
|
145
|
+
|
|
146
|
+
### All Workflows
|
|
147
|
+
|
|
148
|
+
**Daily Flow:**
|
|
149
|
+
|
|
150
|
+
| Command | Purpose |
|
|
151
|
+
|---------|---------|
|
|
152
|
+
| `/morning` | Session primer — identity, energy check, pattern alerts |
|
|
153
|
+
| `/log` | Session capture — sync plan, extract wisdom |
|
|
154
|
+
| `/analyse-day` | Brutal daily audit — strategy alignment, pattern detection |
|
|
155
|
+
| `/plan-tomorrow` | Battle plan for tomorrow |
|
|
156
|
+
| `/review-week` | Weekly + monthly + quarterly review |
|
|
157
|
+
|
|
158
|
+
**Project Flow:**
|
|
159
|
+
|
|
160
|
+
| Command | Purpose |
|
|
161
|
+
|---------|---------|
|
|
162
|
+
| `/ignite` | Start a new project |
|
|
163
|
+
| `/ignite --feature` | Add a feature to an existing project |
|
|
164
|
+
| `/ignite --monetize` | Monetize a project (market validation pipeline) |
|
|
165
|
+
| `/overview` | Refresh context on a project |
|
|
166
|
+
| `/refactor-plan` | Update roadmap after a pivot |
|
|
167
|
+
| `/debrief` | Post-meeting/call capture — actions, decisions, commitments |
|
|
168
|
+
|
|
169
|
+
**System Flow:**
|
|
170
|
+
|
|
171
|
+
| Command | Purpose |
|
|
172
|
+
|---------|---------|
|
|
173
|
+
| `/setup` | Onboarding interview (Identity + Strategy + Dossier + Goals) |
|
|
174
|
+
| `/walkthrough` | Interactive guided tour after setup |
|
|
175
|
+
| `/update` | Update Mover OS and migrate Engine files |
|
|
176
|
+
| `/history` | View how your Engine files evolved over time |
|
|
177
|
+
| `/migrate` | Import existing vault content into PARA structure |
|
|
178
|
+
|
|
179
|
+
**Recovery & Strategy:**
|
|
180
|
+
|
|
181
|
+
| Command | Purpose |
|
|
182
|
+
|---------|---------|
|
|
183
|
+
| `/reboot` | Recovery after 3+ days away |
|
|
184
|
+
| `/debug-resistance` | Diagnose procrastination and avoidance |
|
|
185
|
+
| `/pivot-strategy` | Formal strategy change with logging |
|
|
186
|
+
| `/harvest` | Extract knowledge to Library |
|
|
187
|
+
| `/capture` | Quick capture and route — links, tasks, ideas, brain dumps |
|
|
188
|
+
| `/mover-report` | Generate progress report or submit feedback |
|
|
189
|
+
| `/mover-ideas` | Vault-wide brainstorm from full Engine context |
|
|
190
|
+
| `/mover-check` | Verify installation integrity |
|
|
191
|
+
|
|
192
|
+
---
|
|
193
|
+
|
|
194
|
+
## Architecture
|
|
195
|
+
|
|
196
|
+
```
|
|
197
|
+
Mover OS Bundle/
|
|
198
|
+
src/
|
|
199
|
+
workflows/ # 22 AI command handlers (markdown)
|
|
200
|
+
system/ # Global Rules + Install Manifest
|
|
201
|
+
hooks/ # 6 Claude Code lifecycle hooks
|
|
202
|
+
skills/ # 61 curated skill packs
|
|
203
|
+
install/ # link.sh (hard-link re-linker)
|
|
204
|
+
structure/ # Vault template (PARA + Engine)
|
|
205
|
+
```
|
|
206
|
+
|
|
207
|
+
**Hard-link architecture:** One file, multiple paths. Edit workflows from your editor or from `src/workflows/` — same file on disk. `link.sh` re-establishes links after git operations.
|
|
208
|
+
|
|
209
|
+
---
|
|
210
|
+
|
|
211
|
+
## Documentation
|
|
212
|
+
|
|
213
|
+
- [System Architecture](MANUAL.md) — Deep technical documentation
|
|
214
|
+
- [Install Manifest](src/system/AI_INSTALL_MANIFEST.md) — Complete file inventory
|
|
215
|
+
|
|
216
|
+
---
|
|
217
|
+
|
|
218
|
+
Built by [Asmir](https://x.com/AsmirKHAN_).
|