kata-decompose-issue-into-plans

Name: kata-decompose-issue-into-plans
Availability: InStock
Author: Guardia

Decomposes GitHub issues into dependency-aware plan sub-issues with explicit objectives, risks, and validation steps.

Updated Sep 3, 2025

Search Tags:#automation #planning #github #task breakdown #issue decomposition #dependency ordering #workflow guardrails

Ready to run

npx skills add https://github.com/guardiatechnology/design-system --skill kata-decompose-issue-into-plans

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kata-decompose-issue-into-plans
Source: https://github.com/guardiatechnology/design-system/tree/main/.claude/skills/kata-decompose-issue-into-plans
Command: npx skills add https://github.com/guardiatechnology/design-system --skill kata-decompose-issue-into-plans

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents slow, unclear execution by converting a single parent GitHub Issue (story, bug, or task) into multiple smaller, actionable plan sub-issues with explicit dependencies and guardrails.

Core Features & Use Cases

Issue validation before decomposition: Confirms the parent Issue is well-formed, open, and compatible before creating any sub-issues.
Strategy-driven planning: Infers or applies a decomposition strategy (by layers, endpoints, workflow phases, bounded contexts, or dependencies) to produce an effective split.
Dependency-aware plan creation: Generates N plan sub-issues by invoking plan-task for each confirmed Plan draft and records dependencies to enable correct todo→development sequencing.
Safety checks and non-transactional recovery: Avoids decomposition without confirmation, checks for existing sub-issues, and reports partial progress if an invocation fails.

Quick Start

Use the kata-decompose-issue-into-plans skill for issue number 200 in the design-system repository to produce plan sub-issues ready for Athena to execute.

Frequently Asked Questions about kata-decompose-issue-into-plans

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I break down a GitHub issue into smaller actionable sub-tasks?▼

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.

How does issue decomposition handle dependencies between the generated plan tasks?▼

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.

Can I use this issue decomposition workflow for bugs and tech tasks, or only features?▼

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.

What happens if the GitHub issue decomposition process fails halfway through?▼

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.

Do I need to confirm the decomposition strategy before sub-issues are created?▼

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.