> For the complete documentation index, see [llms.txt](https://docs.simkl.org/how-to-use-simkl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.simkl.org/how-to-use-simkl/core-features/watchlists-and-custom-lists/how-to-use-watchlists/the-simkl-watchlist-lifecycle.md).

# The Simkl Watchlist Lifecycle

A visual guide to content states and user workflows on Simkl. Track every show and movie without losing your place.

Whether you are juggling dozens of TV Shows or trying to keep track of weekend movie recommendations, managing a massive list of things you need to keep track of can get complicated. This flowchart breaks down the entire tracking ecosystem how Simkl makes this process simple.

Ever wonder what actually happens when you hit "Plan to Watch"? This flowchart visually maps out the entire Simkl watchlist process, showing you every possible path a TV show or movie can take from discovery to completion.

```mermaid
flowchart TD
    %% Discovery
    A1([Browse])
    A2([Recommendations])
    A3([Trending])

    A1 --> A([Discover Something to Watch])
    A2 --> A
    A3 --> A

    %% Planning
    A --> B([Add to Plan to Watch])
    B --> C{Start Watching?}

    %% Direct complete from plan
    B -->|Mark as watched| J([Completed])

    C -->|Not yet| B

    %% Type split
    C -->|TV Show / Anime| D([Watching])
    C -->|Movie| E{Finished Movie?}

    %% Watching flow
    D --> F([Track Progress])
    F --> G{What Happens Next?}

    G -->|Keep watching| F
    G -->|Pause| H([On Hold])
    G -->|Drop| I([Dropped])
    G -->|Finish| J

    %% Direct complete from watching
    D -->|Mark as completed| J

    %% Returns
    H -->|Resume| D
    I -->|Restart| D

    %% Movie flow
    E -->|Yes| J
    E -->|No| I

    %% Styling
    classDef source fill:#111827,stroke:#475569,stroke-width:1.5px,color:#e5e7eb;
    classDef core fill:#0f172a,stroke:#3b82f6,stroke-width:2px,color:#eff6ff;
    classDef decision fill:#111827,stroke:#8b5cf6,stroke-width:2px,color:#f3e8ff;
    classDef pause fill:#111827,stroke:#f59e0b,stroke-width:2px,color:#fffbeb;
    classDef drop fill:#111827,stroke:#ef4444,stroke-width:2px,color:#fef2f2;
    classDef done fill:#111827,stroke:#10b981,stroke-width:2px,color:#ecfdf5;

    class A1,A2,A3 source;
    class A,B,D,F core;
    class C,E,G decision;
    class H pause;
    class I drop;
    class J done;

    linkStyle default stroke:#64748b,stroke-width:1.5px;
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.simkl.org/how-to-use-simkl/core-features/watchlists-and-custom-lists/how-to-use-watchlists/the-simkl-watchlist-lifecycle.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.