work-items-to-issues

Split a plan-wide work-items file into per-repo GitHub issues.

198|19|Updated May 7, 2026
One-click install
npx skills add https://github.com/testdouble/han --skill work-items-to-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work-items-to-issues
Source: https://github.com/testdouble/han/tree/main/han-github/skills/work-items-to-issues
Command: npx skills add https://github.com/testdouble/han --skill work-items-to-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Break a work-items.md file (produced by /plan-work-items) into independently-grabbable GitHub issues, one per slice, in each slice's target repo. This enables deterministic publishing of work items as implementation tickets and keeps cross-repo work organized without manually creating issues.

Core Features & Use Cases

  • Split and publish: transform a plan's work-items into per-repo issues, each with its own body and references.
  • Cross-repo mapping: derive the SYM→repo assignments from the plan and corroborate with per-slice references.
  • Automate the publish pipeline: upload design screenshots, create issues, and wire blockers between issues.

Quick Start

Use the skill on a plan's work-items.md to publish all slices as issues to their respective repos.

Frequently Asked Questions about work-items-to-issues

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

FAQPage Schema
How do I publish work items from a plan as GitHub issues?

You can publish work items as GitHub issues by using this skill to split a plan-wide work-items.md file into per-repo slices, creating a GitHub issue for each slice, and updating the source file with the resulting issue numbers.

How does cross-repo issue mapping work when publishing slices?

Cross-repo issue mapping works by deriving SYM-to-repo assignments from the plan and corroborating them with per-slice references, ensuring each slice is published to the correct target GitHub repository.

Do I need gh and jq installed to automate creating issues from a plan?

Yes, you need both gh and jq installed to automate creating issues from a plan, as these command-line dependencies are required to run the scripts that orchestrate the upload and publish flow.

Can I establish cross-slice dependencies between GitHub issues automatically?

Yes, you can establish cross-slice dependencies between GitHub issues automatically, as the skill orchestrates the publish flow by running scripts to wire blockers between newly created issues.

How do I maintain traceability after splitting a work-items file into issues?

To maintain traceability after splitting a work-items file into issues, the skill updates the source work-items.md file with the resulting issue numbers, keeping the original plan synchronized with the published tickets.

What is the best way to upload design assets alongside GitHub issue creation?

The best way to upload design assets alongside GitHub issue creation is to use this skill's orchestrated publish flow, which runs scripts to upload design screenshots, publish issues, and establish dependencies in sequence.