board-scanner

Scan GitHub Projects v2 boards, auto-advance statuses, and publish one dispatch event.

18|4|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/botminter/botminter --skill board-scanner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: board-scanner
Source: https://github.com/botminter/botminter/tree/main/.agents/planning/2026-03-22-console-web-ui/fixture-gen/fixtures/team-repo/coding-agent/skills/board-scanner
Command: npx skills add https://github.com/botminter/botminter --skill board-scanner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate and automate the PLAN step for GitHub Projects v2 by scanning the project board for actionable issues, handling automatic status transitions, and publishing a single dispatch event to the appropriate role hat so work is routed reliably and transparently.

Core Features & Use Cases

  • Board Scanning: Enumerates project items, reads Status field values, and prioritizes epics, stories, and content items for processing.
  • Auto-Advance & Idempotency: Performs defined status transitions (e.g., arch:sign-off → po:merge → done), skips items already at the target status, and logs all actions.
  • Dispatch & Escalation: Publishes exactly one event per scan to the correct hat based on priority tables, skips items marked error, and escalates repeatedly failing items by setting status to error and notifying maintainers.
  • Robust Error Handling & Logging: Logs scan activity to poll-log.txt, records command failures to errors-log.txt, and continues scanning other items on per-issue failures while terminating on systemic errors.
  • Use Case: A coordinator agent runs periodic scans to move triaged epics into planning, dispatch stories to implementers, and surface blocked or error-prone issues for human investigation.

Quick Start

Run a coordinator scan against the team's repo so the board is scanned, auto-advances applied, and a single dispatch event is published for the highest-priority actionable item.

Frequently Asked Questions about board-scanner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub Projects v2 board scanning and issue dispatching?

You can automate GitHub Projects v2 board scanning by running a coordinator agent that enumerates project items, reads Status field values, and publishes one dispatch event per scan cycle to route work to role-specific hats.

How does auto-advance status transition work for GitHub Projects v2 items?

Auto-advance status transition works by applying defined status flows like arch:sign-off to po:merge to done, skipping items already at the target status, and using idempotency checks to prevent duplicate item-edit operations.

Do I need gh CLI access to automate project management scans on GitHub Projects v2?

Yes, you need gh CLI access with repository context to perform item-edit operations for status transitions, cache project and field IDs, and dispatch work from the GitHub Projects v2 board.

What happens when a GitHub Projects v2 scan encounters repeatedly failing items?

When a scan encounters repeatedly failing items, it escalates them by setting the status to error, notifying maintainers, and skipping those items in subsequent dispatch cycles while continuing to scan other actionable issues.

How are scan activity and command failures logged during GitHub Projects v2 automation?

Scan activity is logged to poll-log.txt and command failures are recorded to errors-log.txt, allowing per-issue failures to be isolated while systemic errors terminate the scan cycle to protect board integrity.

Can a coordinator agent prioritize epics and stories differently during a board scan?

Yes, a coordinator agent prioritizes epics, stories, and content items for processing using priority tables, ensuring the highest-priority actionable item receives the single dispatch event published during that scan cycle.