kata-decompose-issue-into-plans

Decomposing a GitHub issue into sub-tasks involves splitting a parent issue into multiple executable plan sub-issues with clear objectives, steps, dependencies, risks, and open questions. This process enforces validation of issue quality and requires full plan confirmation before creating any sub-issues.

Dependency-aware plan creation records dependencies across generated sub-issues to enable correct todo-to-development sequencing. This ensures that workflow guardrails prevent slow execution by establishing the correct execution order before development begins.

Issue decomposition applies to planning workflows for Feature, Bug, and Tech Task issues. The workflow infers or applies a decomposition strategy by layers, endpoints, workflow phases, bounded contexts, or dependencies to produce an effective split for any compatible issue type.

If an invocation fails during sub-issue creation, the workflow reports partial progress instead of rolling back. It also checks for existing sub-issues before decomposing and avoids creating any sub-issues without explicit confirmation of the full plan set.

Yes, the workflow requires confirmation of the full plan set before creating task sub-issues. It infers or applies a decomposition strategy, generates plan drafts, and checks existing sub-issues before you confirm and it labels the created tasks status: todo.