mp-to-issues

To break a PRD GitHub issue into vertical-slice sub-tasks, use a skill that fetches the issue via gh CLI, asks you to resolve ambiguities, designs 3–15 testable slices mapped to requirements, and links them using the addSubIssue GraphQL mutation.

Yes, you can link sub-issues to a parent PRD issue natively by executing the addSubIssue GraphQL mutation, which establishes correct blocking relationships between the newly created vertical slices and the original requirement.

The best way to handle unresolved decisions before creating GitHub issues is to fetch the issue comments first, identify open questions, and require the user to resolve ambiguities through HITL (Human-in-the-Loop) labeling before generating any sub-tasks.

Generating vertical slice sub-issues from a PRD requires gh CLI to fetch the issue body, comments, and node ID, ensuring dependencies and HITL/AFK labels are applied correctly before using GraphQL to link the sub-issues.

You should create 3 to 15 vertical slices from a single PRD issue, ensuring each slice is independently implementable, maps directly to a PRD requirement, and is labeled correctly as HITL or AFK for governance.

You should not use automated vertical slicing for GitHub issues when prior comments contain decisions or ambiguities that remain unresolved, as the workflow requires user clarification before it can safely design and create testable sub-tasks.