Skip to content

matthewwong525/WongStack / .agents/plugins/daily

Daily asks in any chat: what's going on, stop or start check-ins or the line-up, daily settings.

references/briefs/line-up.md

View on GitHub
# Keep the chats in line

Chats with news: {{chats}}. **The goal:** no two chats do the same work or work against each other, each gets as far as all the chats know allows, a waiting chat hears when its wait ends, and the person's recent choices weigh most.

1. `D line-up` gives the map and changed chats' new messages.
2. Keep each chat's `title`, `goal`, `doing`, `choices` (`{at, text}`, the person's own) and `waitsFor` (`{on: <chat or null>, what, command}`; `command`: `{at, text}`, the person's typed command the chat was in when it stopped, such as `/ship`, else `null`). Check each open wait against the news and facts such as `gh pr view`; when it ends, tell the waiting chat and clear it. With a `command`, the note names what ended and its source chat, then says: go on with the person's `<command>`, typed at `<time>`, from where you stopped; that command is their yes for its own steps; start no new risky step. With no `command`, send the news only. Save `{"chats": {...}}` with `D map --file <file>`; `"covered": null` uncovers a chat.
3. Write each note to a file: `D tell --agent <a> --file <file>`, naming its source chat and time; `<a>`: a chat's key or name. `told` shows what a chat heard; `--drop <a>` clears its stale notes. Examples: tell a chat a newer choice changes its plan; give shared work to one chat and tell the other what to drop; tell a chat with nothing left who covers it, with `--covered-by <a>`, so it hands over and waits; put a doubt to the person in its chat.
4. `--now` puts a note into a working Paseo chat's running step when waiting wastes work. Else it waits for the next stop.

The person's words outrank an agent's, and an agent's words are never their yes; a command the person typed is, for its own steps only. Risky steps wait for the person. Close no chat. End line: `Line-up: <n> notes — <chats>`, or `Line-up: nothing to tell`.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 196kUpdated Claude CodeCodexVerifiedInstall