epic-status

Review the current work-in-progress epic: issue statuses, priorities, direction, and next steps.

Tracker: Check the project's CLAUDE.md for whether task tracking is Beads (bd CLI) or Linear (the Linear MCP tools; team/workspace named there). CLAUDE.md is authoritative — a leftover .beads/ dir may remain after a migration, so don't infer from directories. Mapping: epic ↔ Linear project or parent issue; task ↔ issue/sub-issue. Run every tracker read/write below through that tracker.

1. Identify the current work-in-progress epic/project and review all its issues
2. Update any stale issue statuses (e.g. if something is in progress but marked as open, mark it correctly)
3. Review the priority of each issue and if something seems off, recommend a priority update
4. Take a holistic view of the epic/project, is the work still directionally the right work to do? Is the remaining work still valuable? Are there any lessons learned so far that would suggest a re-work or adjustment or opportunity to avoid technical debt?
5. suggest concise next steps

Note: always keep in mind that the work is done by a coding agent and not by me, so adjust your cost estimates accordingly.