glassbox / rules

---
description: Create a new task ticket in Hot Sheet
alwaysApply: false
---
<!-- hotsheet-skill-version: 28 -->

Create a new Hot Sheet **task** ticket. General tasks to complete.

**Parsing the input:**
- If the input starts with "next", "up next", or "do next" (case-insensitive), set `up_next` to `true` and use the remaining text as the title
- Otherwise, use the entire input as the title

**Create the ticket — MCP tool (preferred when the channel is connected):**
Call the `hotsheet_create_ticket` tool with `{ "title": "<TITLE>", "category": "task", "up_next": <true|false> }`. The tool is schema-validated and routes to the channel server's `--data-dir` so there's no chance of cross-project misrouting.

**Fallback (curl):**
```bash
curl -s -X POST "http://localhost:$HOTSHEET_PORT/api/tickets" \
  -H "Content-Type: application/json" \
  -H "X-Hotsheet-Secret: $HOTSHEET_SECRET" \
  -d '{"title": "<TITLE>", "defaults": {"category": "task", "up_next": <true|false>}}'
```

Set these first. Both are machine-specific and deliberately not stored in this file (which is committed and shared with everyone on the repo):
```bash
export HOTSHEET_PORT=$(node -p "require('./.hotsheet/settings.local.json').port ?? 4174")
export HOTSHEET_SECRET=$(node -p "require('./.hotsheet/secret.json').secret")
```

If the request fails (connection refused or 403), re-read those two files — you may be connecting to the wrong Hot Sheet instance. (Older projects keep `port` and `secret` in `.hotsheet/settings.json` instead.)

Report the created ticket number and title to the user.