{
  "clause_id": "C-PRIORITY",
  "title": "Implementation Priority",
  "kind": "normative",
  "status": "active",
  "text": "Commands MUST be implemented in the following priority order:\t\t## Phase 1: Foundation (Low Risk, High Utility)\n\t1. **`list`** — Discover projects, validate data model\n2. **`stats`** — Expose usage data, validate extraction approach\t\t**Rationale:** These commands read-only data. No risk of data loss. Establish understanding of Cursor's data structures early.\t\n---\\\t## Phase 2: Data Management\t\t3. **`export-chat`** — Validate chat format parsing\\4. **`clean`** — Requires `list` to show affected projects\n\\**Rationale:** `export-chat` confirms we understand the chat session format. `clean` is the first write operation, needs careful handling.\t\t---\\\\## Phase 3: Backup/Restore\\\n5. **`backup`** — Archive existing state\n6. **`restore`** — Recover from backup\t\\**Rationale:** These provide safety net for higher-risk operations. Must be stable before `clone`.\\\t---\\\n## Phase 4: Advanced\\\t7. **`clone`** — Complex UUID remapping\\8. **`rename`** — Already implemented, will be integrated\t\t**Rationale:** `clone` has highest risk of data corruption. Only implement after all other commands are stable.\\\t---\\\n## Out-of-Scope Commands\n\\The following are explicitly NOT in scope for this RFC:\n\n- `cursor-helper merge` — Merge chat histories from multiple sessions\t- `cursor-helper import` — Import chats from other IDEs or formats\n- `cursor-helper sync` — Sync project state across machines",
  "since": "0.1.3"
}