菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| 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. |
Analyze the open issue board, identify themes and arcs, and write a sprint file the orchestrator can use for strategic planning.
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
Group issues into thematic arcs based on:
An arc is a cluster of 2+ related issues. Standalone issues that don't fit an arc go under "Ungrouped".
For each arc, determine:
needs-clarification label)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
Output a concise summary to the conversation:
needs-clarification, issues that unblock others)needs-clarification are never "ready"Sprint lifecycle: plan, run, review, retro. The top-level orchestrator for autonomous issue resolution. Use for "run a sprint", "plan the sprint", "sprint review", "sprint retro", "/sprint", "/sprint plan", "/sprint review", "/sprint retro", or any variant.
Step back and interrogate the frame instead of executing it. `/why <subject>` GENERATES the sharp questions that should have been asked about a request, plan, artifact, or your own intended action — it does NOT answer them. Use when handed an assignment that smells mis-scoped, when about to loosen a constraint to silence a signal (bump a timeout, widen a threshold, disable a check, narrow scope to the measurable half), when triaging borderline/unfiltered backlog issues, or when a user is frustrated that the obvious framing is wrong. Triggers: /why, /why nsfw.
Build an autonomous sprint skill for a target project. Explores the project's workflows, constraints, and tooling, then produces a tailored sprint skill that lets Claude orchestrate parallel implementation sessions end-to-end. Use when setting up auto-sprint in a new repo, or when adapting sprint orchestration to a project with different workflows. Trigger on "bootstrap sprint", "set up auto-sprint", "build sprint skill for <project>", or "make <project> sprintable".
Audit and garbage-collect a committed Claude-memory store (MEMORY.md + per-fact files). Evidence-based, parallel, then a gated apply. Use when MEMORY.md has grown large, after several sprints, when memory has drifted from CLAUDE.md, or when the user says "/memory-gc", "clean up memory", "audit memory", "the memory is huge", or notices memory diffs/orphans.
Extract actionable lessons from sprint history. Buckets every Claude Code session into the sprint it ran in, builds a deterministic per-session digest (tokens, duration, errors, orchestration signals, evidence), then runs a multi-agent Workflow that classifies each session (orchestrator vs worker), scans for tool errors / autoclassifier rejections / user interventions, summarizes it, aggregates per-sprint, per-10-sprint window, and over time — ending in ranked, concrete actions. Use for "extract sprint lessons", "what can we learn from sprint history", "/sprint-lessons", or a retro deep-dive.
Author, refine, or migrate a doing-it-wrong architectural rule, and harvest recurring mistakes from merged PRs. Routes on its argument — `harvest` (mine PR review comments for recurring author mistakes), `init` (bootstrap the rule engine into a repo), `add` (author a rule), or no arg (overview + "is this a good rule?" triage). Use when the user wants to "write a rule", "add a lint rule", "should we lint for this", "make a rule for X", "migrate a check-*.ts into the rule engine", "harvest rules", "what should we lint for", "reduce review churn", "mine PR comments for rules", or judging whether a proposed invariant is worth a rule.