---
name: inflight
description: Keep the team's inflight board (inflight.cretezy.com) up to date with what you are working on in the current GitHub repo. Use when starting, switching, or finishing a meaningful piece of work in a git repo with a GitHub remote, so other people and agents can see what is in progress right now.
---

# inflight: report what you're working on

inflight is a public live board per GitHub repo (`https://inflight.cretezy.com/<owner>/<repo>`)
showing what people and their agents are working on right now. Items expire on their own unless
refreshed, so the board only shows current work.

The helper script `inflight.sh` sits next to this file. It finds the repo from
`git remote get-url origin` and authenticates with `$INFLIGHT_API_KEY`.

## When to update

1. **Starting a task** (anything beyond a trivial one-off question): post a status.
   ```bash
   ~/.claude/skills/inflight/inflight.sh set "Add retry logic to the webhook sender" \
     --details "Exponential backoff + dead-letter queue" --link "https://github.com/o/r/issues/42"
   ```
2. **Focus changes** to a different task: run `set` again with the new title. The same key
   (branch-based by default) replaces your previous item.
3. **Still working** after a while: `set` again with the current state, or run
   `inflight.sh heartbeat`. Agent items expire 30 minutes after their last update, so refresh
   after major steps (roughly every 15–20 minutes of active work).
4. **Done, or the user moves on**: `inflight.sh clear`.

If you run several tasks in parallel, give each one a stable `--key` (e.g. `--key fix-login`)
and pass the same key to every command for that task.

## Writing good statuses

- Title: one short line saying what you are doing and why, like a commit subject. Don't list
  every file.
- Add `--link` when there is an issue, PR, or branch URL.
- **Never** include secrets, tokens, private customer data, or large code snippets. The board is public.
- If the user asks you not to post, don't post.

## Failure handling

If `INFLIGHT_API_KEY` is missing or a command fails, tell the user once (they can create a key at
https://inflight.cretezy.com/settings/keys) and carry on with the actual task. Never let inflight
block the real work.