to-issues

Converts an approved implementation plan into dependency-ordered GitHub issues via the gh CLI.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/scoots31/engineering-playbook --skill to-issues-scoots31
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/scoots31/engineering-playbook/tree/main/skills/to-issues
Command: npx skills add https://github.com/scoots31/engineering-playbook --skill to-issues-scoots31

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an approved implementation plan into trackable work items is tedious and error-prone — issues get created out of order, lack context, or miss dependencies. This Skill converts an approved phased plan into self-contained GitHub issues, each carrying its design reference, process anchor, data anchor, done criteria, and dependency links. ## Core Features & Use Cases - Self-contained issue generation: Each slice becomes a GitHub issue with a structured body covering what it builds, design reference, process anchor, data anchor, acceptance criteria, and dependencies. - Dependency-ordered creation: Issues are created blockers-first using the gh CLI so dependent issues can reference real issue numbers. - Phase labeling and reporting: Applies Phase, Ready, Infrastructure, and Blocked labels, then reports a summary mapping slices to issue numbers. - Use Case: After approving a phased plan for a player search feature, run this Skill to create issues like "[SL-001] Player Search" with full context, labeled Phase 1 and Ready, with SL-002 correctly referencing its dependency on SL-001. ## Quick Start Convert my approved implementation plan into GitHub issues in dependency order using the gh CLI.

Frequently Asked Questions about to-issues

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

FAQPage Schema
How do I convert an implementation plan into GitHub issues?

Approve the phased plan first, then create one GitHub issue per slice using gh issue create. Each issue body includes what it builds, design reference, process anchor, data anchor, done criteria, and dependencies, created blockers-first so dependents can reference real issue numbers.

How do I create GitHub issues in dependency order with the gh CLI?

Create blocking issues first with gh issue create, note the returned issue numbers, then reference those numbers in the Depends on field of dependent issues. This ensures every dependency link points to an existing issue.

What should a self-contained GitHub issue for a build slice include?

A self-contained issue includes a title like [SL-001] Slice Name, a one-sentence description, design reference, process anchor, data anchor, acceptance criteria under Done looks like, and a Depends on section. A builder should start work from the issue alone.

Does this work without the GitHub CLI installed?

No, the workflow requires the gh CLI authenticated against a GitHub repository. If gh is not authenticated, run gh auth login and follow the prompts before creating any issues.

When should I not create issues from a plan?

Do not create issues before the plan is explicitly approved, and skip Deferred slices — only Ready slices become issues. Infrastructure slices not yet in the backlog must be added there first before issue creation.