Manages GitHub Project board operations through serialized gh CLI reads and writes.
npx skills add https://github.com/whinchman/midi-man-mk3 --skill board-man-whinchman
Please help me install this Agent Skill. Skill: board-man Source: https://github.com/whinchman/midi-man-mk3/tree/main/.claude/skills/board-man Command: npx skills add https://github.com/whinchman/midi-man-mk3 --skill board-man-whinchman
gh project and gh issue operations behind a single subagent that caches board IDs, serializes writes with a lock file, and returns structured JSON results. ## Core Features & Use Cases - Board Reads: List column items, open PRs, tracked issue markers, and fetch the next available task with parallel-safe operations. - Serialized Writes: Create issues, post plan comments, set column status, and apply labels under a flock-style lock to prevent concurrent write conflicts. - ID Caching & Recovery: Cache project, status field, and option IDs in .workflow/temp/ and regenerate them automatically on 422 errors or via refresh-cache. - Use Case: A coordinator agent needs the next READY task while a coder agent marks its issue IN-PROGRESS; both delegate to board-man, which serves the read immediately and serializes the status write safely. ## Quick Start Ask the board-man subagent to run the operation "next-task <repo>" and use the returned JSON issue details to begin work.High-intent search queries and answers about installing and using this skill.
Delegate every board operation to the board-man subagent with a single-line operation string such as "list-column READY" or "set-status 42 IN-PROGRESS". It executes the gh CLI calls and returns a JSON object with the results or an error and exit code.
Serialize all writes through one interface that acquires a lock file before mutating state. board-man uses a flock-style lock at .workflow/temp/.board-man.lock, polling every 2 seconds and timing out after 30 seconds with exit code 5.
Yes, read operations like list-column, next-task, find-issue-by-marker, and download-plan are parallel-safe because they do not mutate board state. Only writes such as create-issue, set-status, and apply-label require the serialization lock.
A 422 error means the cached status option ID no longer matches the board, usually after columns are renamed or recreated. board-man detects this and regenerates the cache via refresh-cache before retrying the operation.
Only other agents such as coordinator, architect, manager, coder, github-triage, and pull-request invoke it when workflow.backend is github_project in agent.yaml. It is not a user-facing skill and should not be called directly by end users.
EdgeVectorManage Kanban board cards in LastDB via a CLI.
declanshanaghyPull the next GitHub Project board item and dispatch the design-build-validate chain.
dyad-shResolves GitHub pull request review comments and failing CI checks automatically.
apacheParse Markdown security findings and create tracker issues in 'Needs triage'.