# project-board-sync

project-board-sync keeps a GitHub Projects board in step with a claude-flow agent swarm: cards, statuses, sprint metrics. Useful when several agents touch one repo.

- subagent · `type=agent` · Claude Code, Codex, Cursor · ★ 850 repo stars
- Author: ruvnet
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/ruvnet/agentic-flow/tree/HEAD/.claude/agents/github/project-board-sync.md
- Updated: 2026-10-26
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/agents/project-board-sync

## What it does

Cards are created from issues, shifted between columns as an agent task changes state, and filled in with fields such as agent count or complexity. The subagent reaches GitHub through `gh` and the swarm through `mcp__claude-flow__*` tools like `swarm_init`, `task_orchestrate` and `github_issue_track`.

Rules live in `.github/board-sync.yml`: which task status maps to which column, which agent type turns into a label, how priority lands in a project field. Views are declared separately — a kanban grouped by status, a table grouped by assigned agent, a roadmap keyed on ETA. Bulk edits, card templates and moves between boards run as `npx ruv-swarm github board-*` commands.

Pre-hooks fire first: `gh auth status`, `gh project list --owner @me`, `git status --porcelain`. An unauthenticated `gh` makes the first hook exit with an error, so nothing starts. The user check pipes through `jq`, which has to be on the machine. The `mcp__claude-flow__*` tools resolve only with the claude-flow MCP server connected.

## Requirements
- Works with: GitHub

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/agents/project-board-sync.md` — For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

### Codex

**Manually: put the files in place**
- File: `.codex/agents/project-board-sync.toml` — Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

### Cursor

**Manually: put the files in place**
- File: `.cursor/agents/project-board-sync.md` — Cursor also reads .claude/agents/

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/ruvnet/agentic-flow/tree/HEAD/.claude/agents/github/project-board-sync.md

## When to use it
- turn a labelled issue list into project cards
- move cards to the next column as agent tasks advance
- chart burndown and velocity for a sprint
- spread cards across agents by current workload
- keep the Development and QA boards in sync

## Example prompts
- Attach the Development Board project to the swarm and switch on two-way status sync
- Import open issues labelled enhancement into Backlog and assign agents to them
- Show burndown and velocity for the current sprint

## Similar
- [project-management](https://affpapa.org/en/nevibecode/skills/project-management.md) — skill · 399 installs
- [run-github-project](https://affpapa.org/en/nevibecode/skills/run-github-project.md) — skill · 829 installs
- [board-ops](https://affpapa.org/en/nevibecode/skills/board-ops.md) — skill · ★ 92149 repo stars
- [github-project-management](https://affpapa.org/en/nevibecode/skills/github-project-management.md) — skill · 1400 installs
- [sync-todos-to-github](https://affpapa.org/en/nevibecode/commands/sync-todos-to-github.md) — command · ★ 907 repo stars
- [audit-project-github](https://affpapa.org/en/nevibecode/commands/audit-project-github.md) — command · ★ 2003 repo stars

From the same set: [ruvnet/agentic-flow](https://affpapa.org/en/nevibecode/by/ruvnet/agentic-flow.md) — 76 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
