to-issues

To split project documentation into trackable issues, this skill breaks down project plans, specs, or PRDs into smaller, independently traceable items for issue trackers. It transforms high-level documentation into discrete development tasks.

Vertical slicing in issue creation splits a project into complete end-to-end slices, reducing dependencies and improving traceability. This approach generates issues that represent independently deliverable units of work across the project stack.

You generate issues from user stories to align work with project requirements through user story mapping. This process translates mapped user journeys into discrete, actionable issues that directly reflect the original project requirements.

Yes, you can publish generated issues directly into your project's issue tracker. This skill integrates with issue tracking systems to facilitate streamlined planning, review, and execution workflows without manual data entry.

To create issues from a PRD for software development task tracking, run the skill with your project's plan, specification, or PRD. It automatically splits the documentation into a series of traceable issues for managing development tasks.

Use vertical slice issues when you need to reduce dependencies and improve traceability across complete end-to-end project slices. Horizontal layer issues create cross-dependencies between teams, making independent delivery and progress tracking more difficult.