skills.rest
Jmarques
JmarquesCOMMUNITY
Explore all skills by this author →
GitHub

to-issues

Create trackable issues from plans, specs, or PRDs using vertical slicing techniques.

Updated Jul 3, 2026
Search Tags:#project management#issue tracking#issue creation#vertical slicing#plan conversion
One-click install
npx skills add https://github.com/Jmarques/orford-sur-le-lac_embarcations --skill to-issues-jmarques
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/Jmarques/orford-sur-le-lac_embarcations/tree/main/.agents/skills/to-issues
Command: npx skills add https://github.com/Jmarques/orford-sur-le-lac_embarcations --skill to-issues-jmarques

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the creation of independently-grabbable issues from plans, specs, or PRDs, simplifying project management and issue tracking.

Core Features & Use Cases

  • Automated Issue Creation: Convert plans into actionable issues in your project issue tracker.
  • Vertical Slices: Utilize vertical slices to ensure comprehensive, end-to-end issue creation.
  • Use Case: When reviewing a feature spec, use this Skill to generate a set of issues that can be tracked and worked on individually.

Quick Start

Use the to-issues skill to create issues from the feature spec document 'feature-spec.md'.

Frequently Asked Questions about to-issues

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

FAQPage Schema
How do I create trackable issues from a feature spec or PRD?▼

Vertical slicing breaks down plans or specs into comprehensive, end-to-end issues that can be grabbed and worked on individually, ensuring each issue delivers independent value across the project workflow.

How do I convert a project plan into vertical slices for issue tracking?▼

Converting a project plan into vertical slices involves analyzing the document and breaking the work into independently actionable, end-to-end issues that are automatically generated and populated in your issue tracker.

Can I automate issue creation directly from a markdown feature spec?▼

Yes, you can automate issue creation directly from a markdown feature spec by processing the document to identify vertical slices and automatically creating corresponding issues in your connected project issue tracker.

Do I need a specific issue tracker to convert plans into issues?▼

You need an existing project issue tracker where issues can be created, but the conversion process itself relies on analyzing your plan, spec, or PRD content and applying vertical slicing to generate the issues.

What is the best way to break down a PRD into independently grabbable issues?▼

The best way to break down a PRD into independently grabbable issues is applying vertical slicing to the source document, which ensures each generated issue represents a comprehensive, end-to-end unit of work.

Related Skills

Explore More Product & Management Skills→
TrebuchetDynamicsTrebuchetDynamics
5

to-issues

Break plans, specs, or PRDs into independently-grabbable vertical-slice issue tickets.

Official
Intermediate
sebc-devsebc-dev

to-issues

Convert project plans and specifications into individual issues for issue trackers.

Community
Intermediate
danilonovaisvdanilonovaisv
1

github-project-management

Coordinate GitHub issues, boards, and sprint planning across repositories.

Community
Advanced
Kushal9889Kushal9889

to-issues

Convert strategic plans into independent, end-to-end issues for an issue tracker.

Community
Advanced