board-overview

name	board-overview
description	Analyze open GitHub issues, group them into thematic arcs, and write a sprint file for orchestrator context. Use when deciding what to work on next, assessing board health, or updating strategic context.

Board Overview

Analyze the open issue board, identify themes and arcs, and write a sprint file the orchestrator can use for strategic planning.

Step 1: Read the Board

Fetch all open issues:

gh issue list --state open --json number,title,labels,body --limit 200

Also fetch recently closed issues (last 2 weeks) for completed-arc detection:

gh issue list --state closed --json number,title,labels,closedAt --limit 50

Step 2: Identify Arcs

Group issues into thematic arcs based on:

• Feature area: which package or subsystem they touch (daemon, CLI, control, core, auth, config, testing, docs, orchestration/skills)
• Dependency chains: issues that must be done in sequence (look for "Related", "Depends on", "Blocks" in bodies)
• Natural work sequences: issues that share context and are more efficient to do together

An arc is a cluster of 2+ related issues. Standalone issues that don't fit an arc go under "Ungrouped".

Step 3: Assess Each Arc

For each arc, determine:

• Status: active (has open issues), completed (all issues closed recently), stalled (open issues but no recent activity)
• Ready issues: which issues in the arc can be picked up now (no unresolved dependencies, no needs-clarification label)
• Blocked issues: which are waiting on other issues or human input
• Suggested ordering: dependency-respecting sequence for implementation

Step 4: Write the Sprint File

Write or update .claude/arcs.md with the following structure:

# Board Overview

> Auto-generated by /board-overview on YYYY-MM-DD. Do not edit manually.

## Active Arcs

### Arc Name
_N open issues, M ready_

| # | Title | Status | Dependencies |
|---|-------|--------|--------------|
| 123 | Issue title | ready | — |
| 124 | Another issue | blocked | #123 |

### Another Arc
...

## Ungrouped Issues

| # | Title | Labels |
|---|-------|--------|
| 200 | Standalone issue | bug |

## Recently Completed Arcs

### Arc Name (completed YYYY-MM-DD)
- #100 Issue title
- #101 Another issue

## Summary

- **Total open**: N issues
- **Ready to pick up**: M issues
- **Blocked**: K issues
- **Active arcs**: L

Step 5: Report

Output a concise summary to the conversation:

• Number of open issues and how many are ready
• Active arcs with their ready counts
• Top 3-5 recommended issues to pick up next (prefer: unblocked, no needs-clarification, issues that unblock others)
• Any stalled arcs that need attention

Guidelines

• Keep arc names short and descriptive (e.g., "Auth Overhaul", "CLI Polish", "Test Stability")
• Don't over-group — if two issues share a label but are otherwise unrelated, they're not an arc
• Issues labeled needs-clarification are never "ready"
• Prioritize issues that unblock other issues
• Note if the board looks healthy (balanced arcs, clear priorities) or needs attention (too many stalled arcs, unclear priorities, dependency tangles)