status-board

Generate self-contained HTML status boards for pull-request stacks and project milestones.

Updated May 21, 2026
One-click install
npx skills add https://github.com/love-lena/skills --skill status-board-love-lena
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: status-board
Source: https://github.com/love-lena/skills/tree/main/skills/status-board
Command: npx skills add https://github.com/love-lena/skills --skill status-board-love-lena

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Active engineering work scattered across PRs, reviews, and blockers is hard to see at a glance. This Skill turns that state into a single self-contained HTML decision surface that shows current position, active blockers, and the highest-leverage next action within five seconds. ## Core Features & Use Cases - Shipping spine structure: Leads with current position and next move, then lists active PRs in dependency order and the complete path to shipped. - Present-tense filtering: Removes resolved blockers, stale history, and unsupported claims on every update so the board only shows what changes current decisions. - Self-contained HTML output: Produces one file with inlined CSS, JavaScript, and SVG, with no external runtimes, fonts, or CDNs, readable on desktop and mobile. - Use Case: An engineer driving a stack of five dependent PRs asks for a status board and gets a single HTML page showing which PR is ready to merge, which is blocked by review, and the exact next command to run. ## Quick Start Use the status-board skill to update the status board for my current PR stack and show the next move.

Frequently Asked Questions about status-board

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

FAQPage Schema
How do I create a status board for a stacked pull request workflow?

Invoke the skill with your current PR stack context and it produces a self-contained HTML board. The board lists PRs in dependency order with each unit's next action, current state, and blockers, followed by the complete path to shipped.

What should a project status board include for engineering teams?

A status board should lead with current position and the single highest-leverage next action, then show active work units in shipping order and the full sequence to done. Optional sections like dependency maps, milestones, and rollout sequences are added only when they change decisions.

Does the status board HTML require external dependencies or internet access?

No. The output is one self-contained HTML file with all CSS, JavaScript, and SVG inlined. It loads no external runtime, CDN, font, image, or stylesheet, so it opens locally and works offline.

Can I update an existing status board instead of creating a new one?

Yes. The skill updates an existing status-board artifact or HTML file in place by default. A parallel snapshot is created only when explicitly requested.

When should I not use an HTML status board for project tracking?

Avoid it when you need persistent collaborative editing, automated data sync, or historical trend analysis, since the board is a static present-tense snapshot. It also excludes code-level implementation detail, which belongs in plan or spec files.