estimated-kanban-board

Generate Kanban status documents from GitHub issues and OpenSpec specs.

2|2|Updated Sep 20, 2023
One-click install
npx skills add https://github.com/zabiny/klabis --skill estimated-kanban-board
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: estimated-kanban-board
Source: https://github.com/zabiny/klabis/tree/main/.claude/skills/estimated-kanban-board
Command: npx skills add https://github.com/zabiny/klabis --skill estimated-kanban-board

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

What problem does it solve?

This skill creates and updates a kanban-style dashboard that compares open GitHub issues in MVP/core milestones to active OpenSpec specifications, highlighting gaps between planned work and defined requirements.

Core Features & Use Cases

  • Builds and maintains docs/implementation-status.html and docs/implementation-status.md by mapping issues to OpenSpec specs.
  • Classifies each issue into COMPLETED, IN_PROGRESS, or TODO based on spec coverage and labels.
  • Preserves user-customized HTML styling by updating only the JSON data block and header metadata.

Quick Start

Run the skill to generate or refresh docs/implementation-status.html and docs/implementation-status.md based on current issues and specs.

Frequently Asked Questions about estimated-kanban-board

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

FAQPage Schema
How do I track GitHub issues against OpenSpec specifications?

You can track GitHub issues against OpenSpec specifications by using a script that reads specs from openspec/specs/, loads issues via GitHub CLI, and maps them to produce an HTML and Markdown kanban board. This highlights gaps between planned work and requirements.

What is the best way to generate a kanban board from GitHub issues and specs?

The best way to generate a kanban board from GitHub issues and specs is using a Python-based updater script that injects data into a template. It operates on MVP/core milestones, validates data integrity, and outputs both HTML and Markdown status documents.

Can I preserve custom HTML styling when updating a GitHub issues status board?

Yes, you can preserve custom HTML styling when updating a GitHub issues status board. The script updates only the JSON data block and header metadata, ensuring your manual styling tweaks in the HTML document remain intact during refreshes.

How does issue status classification work for OpenSpec spec coverage?

Issue status classification for OpenSpec spec coverage works by applying a defined status taxonomy. Issues are classified into TODO, IN_PROGRESS, or COMPLETED statuses based on their spec coverage and labels, ensuring accurate tracking of implementation progress.

Do I need the GitHub CLI to map issues to OpenSpec specs?

Yes, you need the GitHub CLI to map issues to OpenSpec specs. The script relies on the GitHub CLI to load issues from your repository milestones, validate data integrity, and align them with active specifications for the kanban board.