board

Renders the open-work board from NEXT.md and BACKLOG.md with alarms, deployments, and branch audit.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/diy-accounting-uk/submit.diyaccounting.co.uk --skill board-diy-accounting-uk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: board
Source: https://github.com/diy-accounting-uk/submit.diyaccounting.co.uk/tree/main/.claude/skills/board
Command: npx skills add https://github.com/diy-accounting-uk/submit.diyaccounting.co.uk --skill board-diy-accounting-uk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a live, accurate picture of open work across a repository is hard when items are scattered across NEXT.md, BACKLOG.md, GitHub alarm issues, AWS deployments, and stale branches. This Skill renders a single consistent board so the operator always knows what is in flight, ready, or blocked. ## Core Features & Use Cases - Unified work table: Renders every open NEXT.md item plus backlog Tier 1 rows, deduplicated and ordered by state, tier, and change size, with model tier and status annotations. - Alarm triage: Groups open GitHub alarm issues by family, checks whether each alarm still exists, and recommends an action such as close as stale, fix, tune, or investigate. - Deployment and branch audit: Lists live ci and prod CloudFormation deployment sets with teardown timing, and classifies every local and origin branch as open, unique, or stale with operator-ready cleanup commands. - Use Case: An operator asks "what's in flight?" and receives the mode line (cool-down and monitor status), the prioritized work table, alarm families with recommended actions, deployment lifecycles, and a branch audit, with NEXT.md written back to match. ## Quick Start Ask the assistant to render the board showing all open items, alarms, deployments, and branches.

Frequently Asked Questions about board

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

FAQPage Schema
How do I render the open-work board for this repository?▼

Invoke the board skill or ask "what's in flight". It reads NEXT.md and BACKLOG.md fresh, then prints a mode line, the prioritized work table, alarm families, deployments, and a branch audit in five fixed parts.

How are board rows ordered and classified?▼

In-flight rows come first, then machine-only, machine-ask, human-driven, and blocked groups. Within a group rows sort by tier, then by estimated file count, and NEXT.md is reorganized into matching sections as part of the write-back.

Does the board skill modify GitHub issues during a render?▼

No. A render is strictly read-and-report: it never closes, labels, or comments on issues while rendering. Recommended actions are printed for the operator, and any label fixes happen after the render completes.

What happens if there is no AWS SSO session for the deployments part?▼

The deployments section is rendered as "unverified: no SSO session" and the render moves on. Alarm existence checks that need CloudWatch are likewise marked unverified until the operator runs aws sso login.

Can the board skill delete stale branches or worktrees itself?▼

No. Branch and worktree deletion is denied to the session. The skill prints one fenced block with the full cleanup commands prefixed with ! so the operator can run them manually.