> For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt.

# Release readiness check

:::info

**Goal:** Find release problems early, while there is still time to fix them.

:::

## What it does

Before each release window, a schedule verifies the checklist: migrations are clean, feature flags are set correctly, the changelog is drafted, and the docs are up to date. Running it ahead of the release means problems surface early, while there is still time to fix them.

## The plugin

[`tessl/release-check`](https://tessl.io/registry/tessl/release-check) walks your release checklist against the changes since the last release and reports what is missing. Install it with:

```bash
tessl install tessl/release-check
```

## Define the schedule

Run it every Thursday at 10:00 UTC, ahead of a Friday release. Add this entry to the `schedules` block in your project's `tessl.json`, and keep any other entries already in that block. Replace `production` with the name of your environment (see the [Schedules overview](/schedules/overview.md) for the prerequisites).

<div class="gb-stepper">

<div class="gb-step">

**Add the schedule entry**

```json
{
  "schedules": {
    "release-check": {
      "action": {
        "skill": "tessl/release-check",
        "environment": "production"
      },
      "schedule": "weekly on thursday at 10:00"
    }
  }
}
```

</div>

<div class="gb-step">

**Validate and push**

Signed out, validation checks the local file only. Signed in, with a `name` that identifies your project, it also runs the checks Tessl applies when the file syncs and when a run starts. Commit and push the change, then confirm Tessl applied the schedule in your workspace before checking its run history.

```bash
tessl schedule validate
git add tessl.json
git commit -m "chore(docs): add release check schedule"
git push
```

</div>

<div class="gb-step">

**Check the runs**

Open the schedule in the web app, or run `tessl schedule runs <id>` to see its run history.

</div>

</div>

## Customize with instructions

Match your own checklist by adding `instructions` inside the same entry's `action`. Keep all other entries in the `schedules` block:

```json
{
  "schedules": {
    "release-check": {
      "action": {
        "skill": "tessl/release-check",
        "environment": "production",
        "instructions": "Check that all migrations have a rollback and every new flag has a default"
      },
      "schedule": "weekly on thursday at 10:00"
    }
  }
}
```

## Create your own

Want a different checklist? [Create your own plugin](/creating-skills-and-plugins/create-a-plugin.md) that walks your release checklist and reports what is missing.