board-doctor

Validate project boards and developer completion claims before advancing work.

4|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/vmobifystudio/app-dev-team --skill board-doctor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: board-doctor
Source: https://github.com/vmobifystudio/app-dev-team/tree/main/skills/board-doctor
Command: npx skills add https://github.com/vmobifystudio/app-dev-team --skill board-doctor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents inconsistent project boards from silently causing tickets to be skipped, misassigned, stranded, or falsely reported as complete.

Core Features & Use Cases

  • Board Validation: Detects malformed rows, duplicate IDs, invalid statuses, missing or unspawnable owners, broken dependencies, cycles, stranded tickets, review-integrity issues, and invalid cycle counts.
  • DONE Verification: Checks developer branches, commits, changed files, and test outcomes before work advances to review.
  • Generated and Legacy Board Support: Distinguishes event-log drift from graph-level problems and provides a manual fallback when Node.js or the validation script is unavailable.
  • Use Case: Run the Skill before spawning agents or moving a developer's DONE claim forward to ensure the board is coherent and the reported implementation is verifiable.

Quick Start

Run the board doctor against docs/31-board.md before spawning agents or accepting a developer's DONE claim.

Frequently Asked Questions about board-doctor

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

FAQPage Schema
How do I validate project boards to prevent hidden or stranded tickets?

Project board validation detects malformed rows, duplicate IDs, broken dependencies, and stranded tickets. Running validation checks board structure, ownership, and dependency graphs to ensure tickets are not skipped, misassigned, or falsely reported as complete.

How do I verify developer completion claims before moving tickets to review?

Verifying developer completion claims requires checking developer branches, commits, changed files, and test outcomes. This ensures the reported implementation is verifiable before advancing work to the review stage.

Can I validate sprint boards when Node.js or validation scripts are unavailable?

Sprint board validation provides a manual fallback when Node.js or the validation script is unavailable. This allows you to distinguish event-log drift from graph-level problems and check board coherence manually.

What causes cycle limits and broken dependency graphs in sprint management?

Cycle limits and broken dependency graphs in sprint management are caused by invalid workflow states and malformed board rows. Detecting these issues requires checking board structure, ownership, dependency graphs, and invalid cycle counts.

When should I run board validation during agent orchestration and sprint execution?

Board validation should run before spawning agents or moving a developer's completion claim forward. This ensures the board is coherent, prevents unverified work from advancing, and applies to sprint execution and agent spawning workflows.

Does board validation work with legacy Markdown boards and generated event-log boards?

Board validation supports both legacy Markdown boards and generated event-log boards. It distinguishes event-log drift from graph-level problems to prevent inconsistent project boards from causing tickets to be skipped or stranded.