# Rundown

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

- Repository: https://github.com/alexgreensh/attention-span (1522 stars)
- Category: Engineering
- License: AGPL-3.0
- Last updated: 2026-10-30
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add alexgreensh/attention-span --skill rundown -g -a claude-code -y`
Codex: `npx skills add alexgreensh/attention-span --skill rundown -g -a codex -y`
Cursor: `npx skills add alexgreensh/attention-span --skill rundown -g -a cursor -y`
Gemini CLI: `npx skills add alexgreensh/attention-span --skill rundown -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add alexgreensh/attention-span`

## Description

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

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

<!-- attention-span v0.12 · check for updates: https://github.com/alexgreensh/attention-span -->
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

The rest: https://github.com/alexgreensh/attention-span/blob/HEAD/plugins/attention-span/skills/rundown/SKILL.md