project-status-thread
Project Status Thread — Say What You Are Doing, How Far, and When It Is Done
Section titled “Project Status Thread — Say What You Are Doing, How Far, and When It Is Done”A project linked to Discord has a status thread (discord.threads.status in .claude/t1k-project-links.json). On a multi-step task, the orchestrating session keeps it current: (1) Start: ONE post: what you are doing, 0/N steps (0%), the steps. (2) Update at milestones only (step/phase done, blocked, state change): edit or append, done/total steps (pct%); when blocked, say what blocks. (3) Done: a final post: what shipped, PR links; DONE only once merged, an open PR is in flight. Every post, not only Done, tags the owner <@discord.tagUserId> (links file) in its top matter (title, Needs or subtext line); an edit never notifies, so append a new post on a state change.
Cadence: done/total from a real count (state the denominator); total unknown → steps: unknown total, never invent N. Max one update per 5 min (blocked/unblocked/done bypass). Never post secrets, tokens, env values, config or raw logs; a blocked post never replaces AskUserQuestion. Skip a trivial one-shot, an opt-out, a missing thread. Sub-agents never post. A failed post warns and continues.
A visual change (player-visible; audio excluded) posts to the ui/art thread, tagged the same way, before done: old + new image, or new alone when no old capture exists, never faked. The PR links the post or carries visual-notice-waiver: <reason> or visual-notice-old: first-capture|unavailable (<reason>). Protocol: visual-change-discord-notice.md.
Procedure: skill t1k-status-checklist. Samples: docs/project-status-thread.md.