readme-refreshlisted

# README Refresh — Automated Screenshot & Copy Update This skill detects staleness in the project README and its screenshots, captures fresh screenshots from the running web UI, and drafts updated README content. It leaves all changes unstaged for the user to review. ## Step 1: Research Phase Launch up to 3 Explore subagents **in parallel** to gather context: ### Agent A — Codebase & Features Explore the current feature set by reading: - `packages/web/src/` — UI components, routing, views, layout, feature flags - `packages/server/` — server capabilities, adapters, API surface - `packages/cli/` — CLI commands and options - `packages/common/proto/` — proto definitions, services, message types Produce a summary of all user-facing features and capabilities. ### Agent B — README & Screenshot Staleness 1. Read `README.md` in full — note every screenshot reference, feature claim, and section 2. List files in `screenshots/` and check their last-modified dates via `git log -1 --format="%ai" -- <file>` for each 3. Find the oldest screenshot commit date, then run: ```bash gh pr list --state merged --search "merged:>YYYY-MM-DD" --limit 100 --json number,title,mergedAt,labels ``` 4. Summarize: which PRs are new since the last screenshot update, grouped by visual vs feature vs internal ### Agent C — RFC / Roadmap / Issues Search for forward-looking context: - Look for RFC, roadmap, or milestone docs in the repo (`specs/`, `RFC*.md`, `ROADMAP*`) - Run `gh issue list --s