skills.rest
valorisa
valorisaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

create-github-issues

Break down feature plans into vertical slice GitHub issues with dependencies.

4|Updated May 20, 2026
Search Tags:#spec-driven#github#agile#issues#gh-cli#task-breakdown#vertical-slices
One-click install
npx skills add https://github.com/valorisa/Claude-Skills --skill create-github-issues-valorisa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-github-issues
Source: https://github.com/valorisa/Claude-Skills/tree/main/skills/create-github-issues
Command: npx skills add https://github.com/valorisa/Claude-Skills --skill create-github-issues-valorisa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually breaking down large feature specs, PRDs, and project plans into GitHub issues is time-consuming and often results in poorly scoped, horizontally sliced tickets that can't be delivered independently. This Skill automates the breakdown process to create thin, end-to-end vertical slice issues with clear dependencies and triage labels, eliminating manual overhead and ensuring tickets are ready for immediate implementation.

Core Features & Use Cases

  • Vertical Slice Issue Generation: Automatically splits plans into tracer bullet issues that cut through all integration layers (schema, API, UI, tests) so each issue is demoable on its own.
  • Dependency & Triage Management: Automatically categorizes issues as AFK (autonomous, no human input needed) or HITL (requires human review) and maps blocker relationships between dependent slices.
  • Use Case: After your team completes a spec-driven design phase for a new user authentication feature, use this Skill to generate 6-8 granular, ready-to-publish GitHub issues that your engineering team can pick up and implement without additional context.

Quick Start

Provide your feature spec, PRD, or project plan to Claude and ask it to break the work down into GitHub issues using vertical slices.

Frequently Asked Questions about create-github-issues

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

FAQPage Schema
How do I break down a feature spec into GitHub issues using vertical slices?▼

Breaking down a feature spec into GitHub issues using vertical slices involves splitting plans into tracer bullet issues that cut through all integration layers so each issue is demoable on its own. This methodology ensures tickets are independently assignable and ready for implementation.

What is vertical slice methodology for task breakdown in agile development?▼

Vertical slice methodology for task breakdown is a technique that splits feature plans into thin, end-to-end issues encompassing schema, API, UI, and tests. It prevents horizontal layer slicing, ensuring each GitHub issue delivers an independently demoable deliverable without manual overhead.

How do I map dependencies and triage labels for GitHub issues?▼

Mapping dependencies and triage labels for GitHub issues involves categorizing tickets as autonomous or human-in-the-loop and mapping blocker relationships between dependent slices. This ensures clear dependency relationships and proper triage labels for immediate team implementation.

Does this task breakdown method require the gh CLI to publish issues?▼

Yes, this task breakdown method requires the gh CLI to publish formatted issues directly to GitHub. The Skill generates the granular, ready-to-publish tickets from your product requirements documents and uses the gh CLI for the actual publication step.

Can I use this vertical slice breakdown for spec-driven software development workflows?▼

Yes, you can use this vertical slice breakdown for spec-driven software development workflows where teams need to convert high-level plans into trackable tickets. It applies directly to product requirements documents to generate implementable issues with clear dependency relationships.

Why should I avoid horizontal layer slicing when creating GitHub issues?▼

You should avoid horizontal layer slicing when creating GitHub issues because it results in poorly scoped tickets that cannot be delivered independently. Vertical slices ensure each issue is demoable on its own by cutting through all integration layers including schema, API, and UI.

Related Skills

Explore More Software Engineering Skills→
Vivekmano27Vivekmano27

project-requirements

Generate complete project specification documents from a concise project brief.

Community
Advanced
Steve-Smith-CODESteve-Smith-CODE

speckit-taskstoissues

Convert local task lists into GitHub issues with duplicate detection.

Community
Advanced
kartikkabadikartikkabadi

to-issues

Break plans, specs, or PRDs into dependency-ordered issues with acceptance criteria.

Community
Advanced
caeziumcaezium
2

prd-to-issues

Decompose PRDs into GitHub issues with tracer-bullet vertical slices.

Community
Advanced