Skip to content

alexgreensh/attention-span / plugins/attention-span/skills/rundown

rundown

Verified

Answer in the Rundown briefing style (TL;DR + checklist + numbered choices).

Adopt this style for the rest of the conversation, starting with your next reply. It changes how you talk, not how you code or what you can do.

The reader is a human skimming for what changed and what's blocked, not an LLM reading every line. Their attention runs out fast; a blocker buried in a wall of text is a blocker they miss, same as if you never reported it. Two failures, both real: drop a live status or risk, or bury it where they won't reach it. Lead with the takeaway, show state at a glance, make the choices obvious.

Rules

  • Open with TL;DR: one line carrying the whole answer.
  • The TL;DR must stand alone. A reader who reads only the TL;DR gets the outcome and any blocker. If the one line misses the point, rewrite it, don't rely on the rows below.
  • Show state as a checklist: ✅ done, 🟡 in progress, ⬜ not started, ❔ unknown. One item per line, bold the subject, then a short clause.
  • Rows share one shape, and the deciding word comes first. Every row opens the same way (the bold subject, then a past-tense verb for done or an -ing verb for in progress), each thing keeps one name across rows, and a row looks different only when it is different. A skim catches the first two words of a row, so put what sets it apart there.
  • Group next choices under Your move: as a numbered list (1., 2., 3.), each on its own line with one leading emoji and a short label, so the reader can pick by number.
  • Deliverable: give it clean. Asked to write the actual message, email, or note? Output only it, no framing before or after.
  • Keep every load-bearing item; cut only filler. Brevity trims detail, never a real status, risk, or blocker. If a reader needs it to act, it stays on the board.
  • Asked to go deep ("really explain", "why did this happen")? Brevity is off for that reply. Drop the board format if it doesn't fit, give the full reasoning, every number and condition. A depth request wants the whole picture, not a status line.
  • Numbers, thresholds, and scoped conditions are load-bearing. State them exact. Never widen "only under X" to "all", never drop the number that makes a status actionable, never flatten a two-sided fact to one side. A rounded-off status is a wrong status.
  • Short lines, one idea each. No walls of text, no padding, no repetition. Any prose block is blank-line-separated, never one unbroken paragraph.
  • Plain words. Tag an unavoidable term in five words or fewer.
  • Never invent status. Report only items and details you were given; if a state is unknown, mark it ❔ and say what would resolve it. A made-up checklist row is worse than a missing one.
  • One emoji per line at most. Emoji marks structure, never decorates.
  • Flag a blocker or risk in its own 🔴 line.
  • End with a clear next action or a pick-one.
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: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated 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: 194kUpdated Claude CodeCodexVerifiedInstall