Agent Project Board Sync
Mirror AI swarm tasks and progress onto GitHub Projects boards so solo builders get visual kanban-style tracking without leaving the agent workflow.
Overview
agent-project-board-sync is an agent skill most often used in Build (also Ship launch, Operate iterate) that syncs Claude-Flow swarms with GitHub Projects for visual task management and coordinated progress tracking.
Install
npx skills add https://github.com/ruvnet/ruflo --skill agent-project-board-syncWhat is this skill?
- Synchronizes AI swarms with GitHub Projects for visual task management and progress tracking
- Pre-hooks validate gh auth, project list access, git context, and GitHub API user login
- Integrates Claude-Flow swarm_init, task_orchestrate, github_pr_manage, github_issue_track, and workflow_create/execute
- Post-hooks surface recent projects, issues, current branch, and repo metadata for quick sanity checks
- Coordination-type skill with TodoWrite and standard repo read/write tooling
Adoption & trust: 643 installs on skills.sh; 58.5k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your agents execute tasks in parallel but your GitHub Project board falls out of date, so you cannot see real progress at a glance.
Who is it for?
Solo builders using GitHub Projects plus Claude-Flow who want agent swarms and kanban-style boards to reflect the same task state.
Skip if: Teams on Jira/Linear-only PM stacks, repos without GitHub Projects enabled, or workflows that disallow gh API and swarm MCP tools.
When should I use this skill?
Invoke with $agent-project-board-sync when you need to synchronize AI swarms with GitHub Projects for visual task management, progress tracking, and team coordination.
What do I get? / Deliverables
Swarm work stays linked to GitHub Projects and issues with validated auth and post-run snapshots of projects, issues, branch, and repo context for the next orchestration step.
- Updated alignment between swarm tasks and GitHub Project/issue state
- Post-sync snapshot of projects, issues, branch, and repo metadata
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Project boards are where implementation work gets prioritized during build; the same sync supports shipping checkpoints and ongoing iteration tracking. pm is the canonical shelf because the skill’s purpose is visual task management and swarm-to-board synchronization, not low-level git or API coding.
Where it fits
Initialize a swarm and mirror spawned tasks onto your @me GitHub Project for the current sprint.
Use github_issue_track and workflow_execute so board cards move when agent tasks complete.
Align launch checklist items on the project board with PR and issue state before release.
Post-run hooks list open issues and projects so you can reprioritize the next agent batch.
How it compares
Use instead of manual card updates after every agent spawn when you want orchestration hooks tied to GitHub Projects and issues.
Common Questions / FAQ
Who is agent-project-board-sync for?
Indie developers and small agent-native teams who manage delivery in GitHub Projects while running ruflo/Claude-Flow swarms for implementation.
When should I use agent-project-board-sync?
During Build while planning and tracking swarm tasks on a project board; during Ship launch when aligning release tasks with board columns; and during Operate iterate when refreshing issue and project state after agent runs.
Is agent-project-board-sync safe to install?
It uses gh, git, file edits, and multiple GitHub MCP helpers—check the Security Audits panel on this page and limit project/repo scope before granting agent access.
Workflow Chain
Then invoke: skill ruvnet ruflo agent github modes
SKILL.md
READMESKILL.md - Agent Project Board Sync
--- name: project-board-sync description: Synchronize AI swarms with GitHub Projects for visual task management, progress tracking, and team coordination type: coordination color: "#A8E6CF" tools: - Bash - Read - Write - Edit - Glob - Grep - LS - TodoWrite - mcp__claude-flow__swarm_init - mcp__claude-flow__agent_spawn - mcp__claude-flow__task_orchestrate - mcp__claude-flow__swarm_status - mcp__claude-flow__memory_usage - mcp__claude-flow__github_repo_analyze - mcp__claude-flow__github_pr_manage - mcp__claude-flow__github_issue_track - mcp__claude-flow__github_metrics - mcp__claude-flow__workflow_create - mcp__claude-flow__workflow_execute hooks: pre: - "gh auth status || (echo 'GitHub CLI not authenticated' && exit 1)" - "gh project list --owner @me --limit 1 >$dev$null || echo 'No projects accessible'" - "git status --porcelain || echo 'Not in git repository'" - "gh api user | jq -r '.login' || echo 'API access check'" post: - "gh project list --owner @me --limit 3 | head -5" - "gh issue list --limit 3 --json number,title,state" - "git branch --show-current || echo 'Not on a branch'" - "gh repo view --json name,description" --- # Project Board Sync - GitHub Projects Integration ## Overview Synchronize AI swarms with GitHub Projects for visual task management, progress tracking, and team coordination. ## Core Features ### 1. Board Initialization ```bash # Connect swarm to GitHub Project using gh CLI # Get project details PROJECT_ID=$(gh project list --owner @me --format json | \ jq -r '.projects[] | select(.title == "Development Board") | .id') # Initialize swarm with project npx ruv-swarm github board-init \ --project-id "$PROJECT_ID" \ --sync-mode "bidirectional" \ --create-views "swarm-status,agent-workload,priority" # Create project fields for swarm tracking gh project field-create $PROJECT_ID --owner @me \ --name "Swarm Status" \ --data-type "SINGLE_SELECT" \ --single-select-options "pending,in_progress,completed" ``` ### 2. Task Synchronization ```bash # Sync swarm tasks with project cards npx ruv-swarm github board-sync \ --map-status '{ "todo": "To Do", "in_progress": "In Progress", "review": "Review", "done": "Done" }' \ --auto-move-cards \ --update-metadata ``` ### 3. Real-time Updates ```bash # Enable real-time board updates npx ruv-swarm github board-realtime \ --webhook-endpoint "https:/$api.example.com$github-sync" \ --update-frequency "immediate" \ --batch-updates false ``` ## Configuration ### Board Mapping Configuration ```yaml # .github$board-sync.yml version: 1 project: name: "AI Development Board" number: 1 mapping: # Map swarm task status to board columns status: pending: "Backlog" assigned: "Ready" in_progress: "In Progress" review: "Review" completed: "Done" blocked: "Blocked" # Map agent types to labels agents: coder: "🔧 Development" tester: "🧪 Testing" analyst: "📊 Analysis" designer: "🎨 Design" architect: "🏗️ Architecture" # Map priority to project fields priority: critical: "🔴 Critical" high: "🟡 High" medium: "🟢 Medium" low: "⚪ Low" # Custom fields fields: - name: "Agent Count" type: number source: task.agents.length - name: "Complexity" type: select source: task.complexity - name: "ETA" type: date source: task.estimatedCompletion ``` ### View Configuration ```javascript // Custom board views { "views": [ { "name": "Swarm Overview", "type": "board", "groupBy": "status", "filters": ["is:open"], "sort": "priority:desc" }, { "name": "Agent Workload", "type": "table", "groupBy": "assignedAgent", "columns": ["title", "status", "priority