Skip to content

t1k:status-checklist

FieldValue
Modulet1k-plane
Version2.13.24
Effortlow
Tools—

Keywords: discord status, milestone post, progress post, status checklist, status post, status thread, step checklist

/t1k:status-checklist
[init|set|post|templates] <slug>

Turns a plan, a SPEC or a kit template into a numbered checklist, posts it to the project’s Discord status thread and re-posts it at each milestone. The script renders and counts; you post. Obligation and cadence live in rules/project-status-thread.md; this skill is the procedure.

A multi-step task in a project with discord.threads.status in .claude/t1k-project-links.json. Skip a trivial one-shot, an opted-out project, a missing thread. Only the orchestrating session posts: sub-agents never do.

Script: bun .claude/scripts/status-checklist.cjs <verb> (global install: ~/.claude/scripts/).

  1. Init (once per task, kebab <slug>): templates lists what is installed (every kit ships its own; core ships feature). Then exactly one of init <slug> --template <id>, init <slug> --from-plan <plan dir> (one step per phase-XX.md), or init <slug> --from-steps '["a","b","c"]' (a SPEC’s steps; a JSON file path also works). --title overrides the title. State lands in .claude/status/<slug>.json.
  2. Start post: render <slug>, send it to the thread (discord.threads.status, also stored in the state file) with discord-mcp messages_send, then record-post <slug> --message-id <id>. Layout rules: t1k-discord-message when installed. The owner tag comes from the links file automatically.
  3. At each milestone (step done, blocked, unblocked): set <slug> <step-id|index> <todo|doing|done|blocked> [--detail ".."] [--note ".."], render <slug>, post it as a NEW message (an edit never notifies), record-post. A blocked step needs --note saying what blocks; it never replaces AskUserQuestion.
  4. Cadence: at most one post per 5 minutes; blocked, unblocked and done bypass it, a completed step does not. Never post secrets, env values or raw logs.
  5. Done: mark the last step done only once the work is merged (an open PR is in flight, not done); the final post carries what shipped and the PR links.

render prints one message. If the text would pass 2000 chars it prints numbered parts separated by a line <<<PART-BREAK>>>: post each part as its own message (render --json gives {"parts":[...]}). Progress is always the real count of done steps; never type it.

Exit codes: 0 ok, 2 usage or invalid data (duplicate template id, bad template), 3 slug, step, state or template not found, 4 SPEC/STATES doc missing. A failed post warns and the work continues.

Game build or engine port (SPEC + STATES, mandatory)

Section titled “Game build or engine port (SPEC + STATES, mandatory)”

Building a game or porting it between engines: use a template with requiresDocs (steps 1 and 2 are spec and states) and init <slug> --template <id> --spec docs/SPEC.md --states docs/STATES.md; write both docs first (exit 4 otherwise). At each state you see running: state <slug> <S-id> <verified|failed|unreachable|todo> [--note ..], then render and post. The post carries a States verified: n/m block and a -# status:<slug> line. Hook status-post-guard BLOCKS any status-thread post that is not the script render (free text, stale render, no checklist). Details, hook rules, escape: references/game-build-port.md.

A kit adds one by shipping status-templates/<id>.json plus a fragment t1k-status-templates-<kit>.json; the script merges fragments from the project and global .claude dirs at runtime. Shapes and merge rules: docs/project-status-thread.md § “Status checklist”.