scaffold-sub-issues-gh

Converts PLAN-*.md files into a GitHub Issues parent and child sub-issue tree.

Updated May 20, 2026
One-click install
npx skills add https://github.com/semanticpixel/abc --skill scaffold-sub-issues-gh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scaffold-sub-issues-gh
Source: https://github.com/semanticpixel/abc/tree/main/plugins/abc/skills/scaffold-sub-issues-gh
Command: npx skills add https://github.com/semanticpixel/abc --skill scaffold-sub-issues-gh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It converts PLAN-*.md task breakdowns into a consistent GitHub Issues parent-plus-children structure, including dependency wiring and label conventions, so you don’t have to manually recreate tracker semantics.

Core Features & Use Cases

  • GitHub issue tree scaffolding from plans: Reads one or more PLAN-*.md files and generates a parent issue plus child issues using a managed Sub-issues task-list pattern.
  • Dependency and state semantics via labels: Assigns repo routing labels and blocks/blocked-by labels derived from plan ST dependencies, and supports Linear-style status emulation through status:* labels.
  • Guardrailed write workflow: Requires explicit user confirmation before any issue creation, prevents silent label creation, and asks for reconciliation when multiple plans conflict.

Quick Start

Use scaffold-sub-issues-gh to create GitHub issues from your most recent PLAN-*.md by running the command exactly as triggered in Claude Code, such as when you say “/scaffold-sub-issues-gh” in the project folder after running /abc:plan.

Frequently Asked Questions about scaffold-sub-issues-gh

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

FAQPage Schema
How do I convert a markdown plan into GitHub sub-issues?

You can convert a markdown plan into GitHub sub-issues by parsing PLAN-*.md files to generate a parent issue and child issues. This creates a structured GitHub issue tree with dependency wiring and label conventions automatically applied.

How do I map task dependencies to GitHub issue labels?

Map task dependencies to GitHub issue labels by deriving blocks and blocked-by labels from plan ST dependencies. The tool assigns repo routing labels and Linear-style status emulation through status:* labels during sequential issue creation.

Can I add child issues to an existing GitHub parent issue task-list?

Yes, you can add child issues to an existing parent issue task-list using existing-parent mode. This patches the placeholder task-list of an already created parent issue instead of generating a new hub repo structure.

Do I need GitHub CLI authentication to generate issue trees?

Yes, GitHub CLI authentication is required to generate issue trees. The workflow enforces gh authentication pre-flight and gh version gating before parsing plans and creating issues to ensure safe repository access.

What happens if my GitHub repository is missing required labels for issue tracking?

If your repository is missing required labels for issue tracking, the workflow uses strict non-silent handling. It prevents silent label creation and prompts for reconciliation when multiple plans conflict or labels are absent.

What is the best way to scaffold a dependency graph for GitHub project planning?

The best way to scaffold a dependency graph for GitHub project planning is converting structured PLAN-*.md files into a parent and child issue tree. This automatically applies correct label conventions and dependency mappings without manual tracker recreation.