to-issues

Name: to-issues
Availability: InStock
Author: danielcopper

Convert project plans into granular GitHub issues and publish them via GitHub CLI.

3|Updated Jul 30, 2023

Search Tags:#automation #workflow #project management #productivity #github #issue tracking

Ready to run

npx skills add https://github.com/danielcopper/dotfiles --skill to-issues-danielcopper

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/danielcopper/dotfiles/tree/main/claude/.claude/skills/to-issues
Command: npx skills add https://github.com/danielcopper/dotfiles --skill to-issues-danielcopper

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh.

What problem does it solve?

This skill solves the friction of translating high-level project plans or product requirements into actionable, well-structured GitHub issues, ensuring consistent project tracking and clear implementation paths.

Core Features & Use Cases

Vertical Slicing: Automatically breaks down complex tasks into tracer-bullet issues that cut through all layers of the stack.
GitHub Project Integration: Seamlessly publishes issues to your GitHub Project board and sets their status to Ready.
Dependency Management: Automatically links issues using native GitHub dependency tracking to ensure the correct implementation order.

Quick Start

Ask the assistant to break the current plan into GitHub issues and publish them to your configured project board.

Frequently Asked Questions about to-issues

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

FAQPage Schema

How do I convert project plans into structured GitHub issues automatically?▼

To convert project plans into structured GitHub issues, this skill analyzes your requirements, breaks them into vertically-sliced tracer-bullet tasks, and publishes them directly to GitHub Projects via the GitHub CLI.

What is vertical slicing and how does it work for GitHub issue tracking?▼

Vertical slicing for GitHub issue tracking breaks complex tasks into tracer-bullet issues that cut through all layers of the stack, ensuring clear implementation paths and consistent project tracking from start to finish.

Do I need the GitHub CLI to publish issues to GitHub Projects?▼

Yes, you need the GitHub CLI installed and authenticated to publish issues to GitHub Projects, as the skill relies on it to set issue status to Ready and link dependencies automatically.

Can I link GitHub issues with dependency tracking automatically?▼

You can link GitHub issues with dependency tracking automatically by using this skill to analyze project context and apply native GitHub dependency tracking, ensuring the correct implementation order.

What's the best way to automate workflow creation from product requirements?▼

The best way to automate workflow creation from product requirements is to generate granular GitHub issues from high-level plans, setting their project board status to Ready and managing dependencies automatically.

Why does publishing GitHub issues require a pre-configured project board mapping?▼

Publishing GitHub issues requires a pre-configured project board mapping because the skill uses this configuration to route generated tracer-bullet tasks to the correct GitHub Projects columns and set their status accurately.