kata-plan-task

To create a linked sub-issue for GitHub task planning, use a workflow that validates a parent issue, drafts a canonical plan body, and opens a sub-issue via MCP with native linking. This ensures the child task is correctly attached to the parent issue before development begins.

An Issue to Plan to PR workflow is a hierarchical execution planning process where a parent issue is validated, a plan sub-issue is drafted with specific steps and dependencies, and a pull request is generated. This prevents premature development by enforcing planning gates before coding starts.

You cannot open a GitHub sub-issue if the parent issue is closed. Parent issue validation checks that the issue exists, is open, matches the required template quality with Why/What/How sections, and has compatible issue types and labels before allowing any sub-issue creation.

You enforce planning gates before creating a GitHub task by validating the parent issue template quality and applying the status:todo label only after all canonical plan sections are confirmed. This requires user confirmation before MCP creates the linked sub-issue.

GitHub MCP supports native sub-issue linking for task creation by creating the child issue and verifying the native Issue Type post-creation. This MCP-first approach ensures the parent-child relationship is established correctly before applying status labels.

A canonical GitHub plan body requires Summary, Objective, Steps, Dependencies, Risks, and Open Questions sections. The status:todo label is applied only after all these canonical sections are confirmed present in the drafted sub-issue body.