bb-list-issues

Aggregate open design handoffs and synchronize them with GitHub issues.

41|9|Updated May 22, 2026
One-click install
npx skills add https://github.com/amoslee2026/Babel --skill bb-list-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bb-list-issues
Source: https://github.com/amoslee2026/Babel/tree/main/.claude/skills/bb-list-issues
Command: npx skills add https://github.com/amoslee2026/Babel --skill bb-list-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scans Babel's design handoff records across designs//.handoff/.md and merges them with GitHub issues to provide a unified view of open handoffs by label.

Core Features & Use Cases

  • Scans local handoff files and filters by label and design to surface actionable items
  • Merges with gh issue lists to present a comprehensive workload view
  • Supports downstream automation by providing a consistent data contract for agents

Quick Start

Run the bb-list-issues skill and pass optional flags to filter by label or design-name to retrieve current handoffs.

Frequently Asked Questions about bb-list-issues

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

FAQPage Schema
How do I aggregate open handoffs across designs and sync them with GitHub issues?

To aggregate open handoffs across designs, you can scan local handoff metadata files and merge them with remote GitHub issues via the gh CLI. This provides a unified view of pending handoffs filtered by label for downstream automation.

Can I filter handoff records by specific design names and labels?

Yes, you can filter handoff records by passing optional flags for label and design-name. This scans local handoff files across designs/*/.handoff/*.md to surface actionable items matching your specific criteria.

What problem does merging local design handoffs with gh issue lists solve?

Merging local design handoffs with gh issue lists solves the problem of fragmented tracking by providing a comprehensive workload view. It unifies local markdown records with remote GitHub issues to present all open handoffs in one structured result.

Do I need the gh CLI installed to list and synchronize design handoffs?

Yes, you need the gh CLI installed to synchronize design handoffs with GitHub issues. The process relies on gh to fetch remote issue lists and merge them with local handoff data from your design directories.

How does the design handoff aggregation output support downstream workflow automation?

The design handoff aggregation supports downstream workflow automation by outputting a consistent data contract. This structured result allows downstream agents to programmatically consume the merged handoff and issue data for further processing.

When should I use a dedicated skill for tracking design handoffs instead of just checking GitHub issues?

You should use a dedicated skill for tracking design handoffs when you need to surface pending local handoffs by label across designs/*/.handoff directories and synchronize them with remote GitHub issues for a unified workload view.