github-project-management

Use the triage commands with ruv-swarm to analyze unlabeled issues, suggest labels based on keyword rules, and assign priority automatically. You can define keyword-to-label mappings in a JSON rules file and run batch triage across open issues.

Run board-init with your project ID and a bidirectional sync mode, then map swarm task statuses like pending, in_progress, and completed to board columns. The board-sync command auto-moves cards and updates metadata as task states change.

You need the GitHub CLI (gh) installed and authenticated, the ruv-swarm or claude-flow MCP server configured, and appropriate repository access permissions. Board operations also require GitHub Projects access for the target owner or organization.

Yes, the sprint-manage and milestone-track commands handle sprint population, capacity planning, and velocity tracking. Analytics commands generate burndown charts, cycle-time metrics, and throughput reports grouped by agent, priority, or type.

The stale-issue workflow lists issues inactive for 30 days, analyzes each with a swarm agent, and labels, comments, or closes them based on the suggested action. Issues stale beyond 37 days are closed automatically with an explanatory comment.