to-issues

Break PRDs, plans, or refactors into structured GitHub issues with acceptance criteria.

16|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/JCE-Joshhh77/JCE-Opencode-Tools --skill to-issues-jce-joshhh77
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/JCE-Joshhh77/JCE-Opencode-Tools/tree/main/config/skills/to-issues
Command: npx skills add https://github.com/JCE-Joshhh77/JCE-Opencode-Tools --skill to-issues-jce-joshhh77

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break PRD, plan, feature, or refactor into independently grabbable issues to streamline task creation, tracking, and milestones. It helps teams convert high-level concepts into concrete, small work items that can be assigned, tracked, and verified.

Core Features & Use Cases

  • Break PRDs, plans, or refactors into granular, independently actionable issues.
  • Create structured task breakdowns and milestones for GitHub issues and boards.
  • Use vertical slicing to scope work and manage dependencies across releases.

Quick Start

Provide a plan or PRD and I will convert it into a structured set of GitHub issues.

Frequently Asked Questions about to-issues

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

FAQPage Schema
How do I break down a PRD into actionable GitHub issues?▼

To break down a PRD into actionable GitHub issues, provide the plan to the Skill. It converts high-level concepts into independently grabbable issues containing context, scope, acceptance criteria, dependencies, and verification to reduce ambiguity.

What is vertical slicing for project management and task tracking?▼

Vertical slicing for project management is a technique to scope work into independently actionable items. It helps manage dependencies across releases and ensures each issue can be assigned, tracked, and verified on Kanban boards.

Can I use this to plan milestones for refactoring tasks on a Kanban board?▼

Yes, you can use this to plan milestones for refactoring tasks. It creates structured task breakdowns applicable across GitHub workflows and Kanban boards, ensuring each refactoring issue includes explicit guardrails and acceptance criteria.

What should be included in GitHub issues to reduce ambiguity during task tracking?▼

GitHub issues should include context, scope, acceptance criteria, dependencies, and verification to reduce ambiguity. This structure streamlines task creation and tracking by converting concepts into concrete, small work items.

Does this work for converting high-level feature plans into small work items?▼

Yes, this works for converting high-level feature plans into small work items. It breaks features into granular issues that can be assigned and tracked, specifying guardrails to ensure each item is independently actionable.