to-issues

To break down a PRD into issues, this skill analyzes your plan's context, explores the codebase, and interacts with you to determine granularity. It then publishes structured issues to your issue tracker in the correct dependency order.

Yes, you can create issues from a project plan automatically. The skill reads your plan file, breaks it into vertical slices using codebase context, and publishes the resulting issues directly to your configured issue tracker.

Yes, you need codebase access to automate issue breakdown. The skill explores the codebase to understand the current project state, ensuring the generated issues accurately reflect actual dependencies and implementation requirements.

Issue dependencies are handled by publishing issues in the correct dependency order. The skill determines the required sequence during the breakdown process and pushes the issues to the tracker so that blocking tasks are created before dependent ones.

The best way to split a project specification is using vertical slices. The skill engages with you to determine the desired issue granularity, analyzes the specification, and creates manageable, structured issues ready for tracking.

Yes, the to-issues skill works with complex project plans. It is ideal for developers or project managers who need to quickly organize and create structured issues from detailed specifications or intricate project plans.